k8s.io icon indicating copy to clipboard operation
k8s.io copied to clipboard

[Umbrella issue] Migrate from k8s.gcr.io to registry.k8s.io

Open ameukam opened this issue 3 years ago • 9 comments

Part of:

  • https://github.com/kubernetes/k8s.io/issues/1834

Design doc: https://docs.google.com/document/d/1yNQ7DaDE5LbDJf9ku82YtlKZK0tcg5Wpk9L72-x2S2k.

This issue focus on the implementation of oci-proxy as a proxy/redirect endpoint for k8s.gcr.io:

Sandbox environment

  • [ ] Setup a sandox environment for development: registry-sandbox.k8s.io.
    • https://github.com/kubernetes/k8s.io/issues/3317
    • https://github.com/kubernetes-sigs/oci-proxy/issues/16
  • [ ] Migrate test workloads to registry-sandbox.k8s.io:
    • https://github.com/kubernetes/test-infra/pull/25466
    • https://github.com/kubernetes/test-infra/pull/25458
    • https://github.com/kubernetes/test-infra/pull/25608
    • https://github.com/kubernetes/test-infra/pull/25607

Production environment:

(taken from https://github.com/kubernetes/k8s.io/issues/1834#issuecomment-949916308)

  • [ ] Continuous deployment
  • [ ] Monitoring: Cloud Run provides native metrics based on GCP Monitoring: https://cloud.google.com/run/docs/monitoring
  • [ ] Logging
  • [ ] PII Management
  • [ ] Recovery
  • [ ] Scalability
  • [ ] Incident Management

/milestone v1.24 /priority important-soon

cc @BenTheElder @dims @eddiezane

ameukam avatar Feb 16 '22 23:02 ameukam

/milestone v1.25

ameukam avatar May 12 '22 02:05 ameukam

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Aug 10 '22 03:08 k8s-triage-robot

/remove-lifecycle stale

ameukam avatar Aug 10 '22 14:08 ameukam

/milestone v.126

ameukam avatar Aug 19 '22 22:08 ameukam

@ameukam: The provided milestone is not valid for this repository. Milestones in this repository: [v1.24, v1.25, v1.26]

Use /milestone clear to clear the milestone.

In response to this:

/milestone v.126

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.

k8s-ci-robot avatar Aug 19 '22 22:08 k8s-ci-robot

/milestone v1.26

ameukam avatar Aug 19 '22 22:08 ameukam

@ameukam can we ditch already the endpoint config here? https://github.com/BenTheElder/kind/blob/main/images/base/files/etc/containerd/config.toml#L46-L47

matthyx avatar Oct 03 '22 12:10 matthyx

@ameukam can we ditch already the endpoint config here? BenTheElder/kind@main/images/base/files/etc/containerd/config.toml#L46-L47

@matthyx We are still in the early days registry.k8s.io in production. I would not advise to remove this endpoint at the moment until we are sure we stop use k8s.gcr.io.

ameukam avatar Oct 03 '22 19:10 ameukam

@ameukam can we ditch already the endpoint config here? BenTheElder/kind@main/images/base/files/etc/containerd/config.toml#L46-L47

@matthyx We are still in the early days registry.k8s.io in production. I would not advise to remove this endpoint at the moment until we are sure we stop use k8s.gcr.io.

Alright, so I will migrate kind's config to mirror my PR https://github.com/kubernetes/kubernetes/pull/110350 (as a benefit it will test the principles).

matthyx avatar Oct 04 '22 06:10 matthyx

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Jan 02 '23 06:01 k8s-triage-robot

/remove-lifecycle stale

riaankleinhans avatar Jan 02 '23 18:01 riaankleinhans

/milestone v1.27

ameukam avatar Jan 19 '23 14:01 ameukam

Waiting until k8s.gcr.io has no egress traffic.

/lifecycle frozen

ameukam avatar Mar 03 '23 10:03 ameukam

/milestone clear

ameukam avatar Mar 03 '23 10:03 ameukam

registry.k8s.io is GA: https://kubernetes.io/blog/2022/11/28/registry-k8s-io-faster-cheaper-ga/

Any new issue should go to https://github.com/kubernetes/registry.k8s.io/issues

/close

ameukam avatar Mar 03 '24 14:03 ameukam

@ameukam: Closing this issue.

In response to this:

registry.k8s.io is GA: https://kubernetes.io/blog/2022/11/28/registry-k8s-io-faster-cheaper-ga/

Any new issue should go to https://github.com/kubernetes/registry.k8s.io/issues

/close

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.

k8s-ci-robot avatar Mar 03 '24 14:03 k8s-ci-robot