Open BenTheElder opened 1 year ago
Related to:
For the promoter we are covering all the AR regions except the newest (open less than 2 months ago).
For the promoter we are covering all the AR regions except the newest (open less than 2 months ago).
TIL! I could've sworn we had another discussion to add AR regions that we held off, I must be mis-remembering
https://github.com/kubernetes/k8s.io/pull/4949 related, we added two regions here that don't seem to be promoted to yet
I was thinking of this thread https://github.com/kubernetes/release/issues/2947#issuecomment-1458412293
With the registry freeze in effect, promoter improvements, and the redirect settled, I think we can revisit https://github.com/kubernetes/release/issues/2947#issuecomment-1458412293 and add a few regions relatively fine.
Once those are live we can easily spin up additional cloud run regions pointed at them.
/milestone v1.29 /assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/lifecycle stale
We extended registry.k8s.io to:
/milestone v1.30
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
/milestone v1.31
/milestone v1.32
This has been delayed by the lack of time and people to push this forward (one volunteer had to take of some personal issues).
We're in 20 regions*
We should evaluate expanding to remaining regions, further reducing the blast radius for issues like #234 and continuing to benefit at the cost trade-off of storage << bandwidth for any remaining regions where this is true.
IIRC @upodroid already had a PR related to this, but we held off primarily due to #181 and image promoter concerns.
We've had some work on the promoter since then, and I'm not sure if we have any remaining blockers to add a few more regions to further improve isolation and capacity.
cc @puerco @ameukam