Expand AR and Cloud Run Regions

[BenTheElder]

We're in 20 regions*

• 19 fully deployed at the moment following 🚨 registry.k8s.io affected by GCP europe-west9 outage 🚨  #234

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

[ameukam]

Related to:

• Add more S3 regions #172

For the promoter we are covering all the AR regions except the newest (open less than 2 months ago).

[BenTheElder]

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

[BenTheElder]

kubernetes/k8s.io#4949 related, we added two regions here that don't seem to be promoted to yet

[BenTheElder]

I was thinking of this thread kubernetes/release#2947 (comment)

[BenTheElder]

With the registry freeze in effect, promoter improvements, and the redirect settled, I think we can revisit kubernetes/release#2947 (comment) and add a few regions relatively fine.

Once those are live we can easily spin up additional cloud run regions pointed at them.

[ameukam]

/milestone v1.29
/assign

[k8s-triage-robot]

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

[ameukam]

/lifecycle stale

[ameukam]

We extended registry.k8s.io to:

• europe-west10
• europe-west3

[ameukam]

/milestone v1.30

[k8s-triage-robot]

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

[ameukam]

/remove-lifecycle stale

[ameukam]

/milestone v1.31

[ameukam]

/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).

[k8s-triage-robot]

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

[BenTheElder]

I'm not sure the promoter can handle this and we seem to be doing well for the moment with the current set.