-
Notifications
You must be signed in to change notification settings - Fork 791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Take inventory of Google-owned cluster-based k8s-infra #240
Comments
/assign |
I noticed |
Is there an estimate on when services will be ready to migrate? I need to decide whether to stand up a new cluster for the oncall-issue-filer or do something else. Thanks! |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/lifecycle frozen |
The new cluster is up and is viable for migrations. A small number of things, including k8s.io, have moved. @philips do you have docs or info on your thing? |
@thockin I just decommissioned my thing on Tuesday because it has been replaced by HackerOne 😂 |
To close this out I'd like to create or link a corresponding issue for each piece of cluster infra #240 (comment) |
As perfdash is currently running at the |
/close Next is non-cluster infra, such as BigQuery, App Engine, etc. which can lead to turn down of GCP projects, not just clusters. That's #241 |
@spiffxp: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Google has a number of clusters floating around running different pieces of infra for the project. What's running on them
The text was updated successfully, but these errors were encountered: