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

Migrate from gcr.io to registry.k8s.io #871

Open
tuminoid opened this issue Oct 1, 2024 · 4 comments
Open

Migrate from gcr.io to registry.k8s.io #871

tuminoid opened this issue Oct 1, 2024 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@tuminoid
Copy link
Member

tuminoid commented Oct 1, 2024

We're using gcr.io based Prow images in project-infra. k8s stopped publishing images 2 months ago, hence we're not getting autobumper to bump new images anymore.

Ref: #869 (comment)

@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Oct 1, 2024
@tuminoid
Copy link
Member Author

tuminoid commented Oct 1, 2024

/kind bug
/triage accepted

@metal3-io-bot metal3-io-bot added kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Oct 1, 2024
@tuminoid
Copy link
Member Author

It should be noted that Prow images do not have published production images available yet. Migration to registry.k8s.io is not done yet, and they look for volunteers to help.

@tuminoid
Copy link
Member Author

#908 makes us use the staging registry as intemediate measure, as we haven't had any Prow image updates for 3 months now. There is activity in #prow community to complete the migration, but we can move to that when its done. We need some fixes from Prow sooner than that happens.

@tuminoid
Copy link
Member Author

/lifecycle frozen

Freezing this for now as it is waiting external actions.

@metal3-io-bot metal3-io-bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants