-
Notifications
You must be signed in to change notification settings - Fork 155
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
Spotlight: SIG K8s Infra #522
Comments
/assign |
Another specific focus for this: budget. Talk with Mario & K8s Infra about how to represent this in the post. |
We've decided to do a separate additional blog about budget in SIG K8s Infra |
Here's my questions doc; could I please have some reviews/ suggestions If its good, I can then send in the SIG Infra channel. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Old blog for reference: https://kubernetes.io/blog/2020/05/27/an-introduction-to-the-k8s-infrastructure-working-group/
Registry change
To pick back up after KubeCon NA 2023.
Specific topic, suggested by Mario: Migration of single-cloud GCP to multi-cloud using credits from other providers. Azure, AWS, Digital Ocean, etc.
August 2: Aakansha to take this on
The text was updated successfully, but these errors were encountered: