-
Notifications
You must be signed in to change notification settings - Fork 21
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
Flag backing registries? #96
Labels
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Comments
+1 @BenTheElder let's talk more in sig-k8s-infra? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Jun 24, 2024
/remove-lifecycle stale |
k8s-ci-robot
removed
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Jul 11, 2024
/priority backlog |
k8s-ci-robot
added
the
priority/backlog
Higher priority than priority/awaiting-more-evidence.
label
Jul 11, 2024
/unassign |
k8s-ci-robot
added
the
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
label
Jul 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
We should also consider flagging usage of backing hosts from k8s.gcr.io and the ARs behind registry.k8s.io
WDYT @dims?
These were never supported, but I bet lots of clusters use them, and they should switch to registry.k8s.io or their mirror instead.
The text was updated successfully, but these errors were encountered: