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.

Sign up for GitHub

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

Jump to bottom

Migrate away from GCR to AR #12400

Open
ameukam opened this issue Nov 21, 2024 · 6 comments
Open

Migrate away from GCR to AR #12400

ameukam opened this issue Nov 21, 2024 · 6 comments
Assignees
@Gacko
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@ameukam
Copy link
Member

ameukam commented Nov 21, 2024 •
edited
Loading

What do you want to happen?

Publish images to a new AR container repository. GCR is depecrated and will be removed on March 2025:
https://cloud.google.com/artifact-registry/docs/transition/prepare-gcr-shutdown#what-happens-after-shutdown

Is there currently another issue associated with this?
@ameukam ameukam added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 21, 2024
@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Nov 21, 2024
@ameukam
Copy link
Member Author

ameukam commented Nov 21, 2024

/priority important-soon
/triage accepted

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 21, 2024
@ameukam
Copy link
Member Author

ameukam commented Nov 21, 2024

FYI @kubernetes/ingress-nginx-maintainers

@Gacko Gacko self-assigned this Nov 21, 2024
@longwuyuan
Copy link
Contributor

Can you help improve the description and make it more elaborate and descriptive.

Where is the connection to gcr

% k -n ingress-nginx describe po ingress-nginx-controller-699896b45d-vz42s| grep -i image
    Image:           registry.k8s.io/ingress-nginx/controller:v1.11.3@sha256:d56f135b6462cfc476447cfe564b83a45e8bb7da2774963b00d12161112270b7
    Image ID:        registry.k8s.io/ingress-nginx/controller@sha256:d56f135b6462cfc476447cfe564b83a45e8bb7da2774963b00d12161112270b7
  Normal   Pulled          26m                kubelet                   Container image "registry.k8s.io/ingress-nginx/controller:v1.11.3@sha256:d56f135b6462cfc476447cfe564b83a45e8bb7da2774963b00d12161112270b7" already present on machine

@longwuyuan
Copy link
Contributor

/remove-priority important-soon
/remove-triage accepted

can reapply labels after detailing the description of the issue

@k8s-ci-robot k8s-ci-robot added needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Nov 21, 2024
@Gacko
Copy link
Member

Gacko commented Nov 21, 2024

We are currently pushing images to GCR. As far as I can tell registry.k8s.io is just another name for that. Before promotion images definitely get pushed to GCR.

@longwuyuan
Copy link
Contributor

So these 23 locations for gcr.io will change to something like pkg.dev https://github.com/search?q=repo%3Akubernetes%2Fingress-nginx%20%20gcr.io&type=code

And similarly all code instance for registry.k8s.io will also change to registry-k8s.pkg.dev

/triage accepted
/priority important-soon

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Gacko Gacko

Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
[SIG Network] Ingress NGINX
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Gacko @ameukam @longwuyuan @k8s-ci-robot