Skip to content
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

Open
kaslin opened this issue Aug 2, 2024 · 6 comments
Open

Spotlight: SIG K8s Infra #522

kaslin opened this issue Aug 2, 2024 · 6 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@kaslin
Copy link
Contributor

kaslin commented Aug 2, 2024

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

@kaslin kaslin converted this from a draft issue Aug 2, 2024
@priyaaakansha
Copy link

/assign

@kaslin
Copy link
Contributor Author

kaslin commented Aug 2, 2024

Another specific focus for this: budget. Talk with Mario & K8s Infra about how to represent this in the post.

@kaslin
Copy link
Contributor Author

kaslin commented Aug 9, 2024

We've decided to do a separate additional blog about budget in SIG K8s Infra

@priyaaakansha
Copy link

Here's my questions doc; could I please have some reviews/ suggestions
https://docs.google.com/document/d/1qO3G1m5t-sQXBkoY6IrxgVew73R8oHYyl9SGPr-SC3s/edit?usp=sharing

If its good, I can then send in the SIG Infra channel.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 14, 2024
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
Status: Blocked/Waiting
Development

No branches or pull requests

4 participants