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

Use new Kubernetes registry for Kubernetes >= v1.22 #7472

Closed
sbueringer opened this issue Oct 31, 2022 · 5 comments · Fixed by #7471
Closed

Use new Kubernetes registry for Kubernetes >= v1.22 #7472

sbueringer opened this issue Oct 31, 2022 · 5 comments · Fixed by #7471
Labels
kind/feature Categorizes issue or PR as related to a new feature. kind/release-blocking Issues or PRs that need to be closed before the next CAPI release triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone
v1.2

Comments

@sbueringer
Copy link
Member

sbueringer commented Oct 31, 2022 •
edited

Given:

  • that the new registry is cheaper for the project and
  • there's an upstream effort (kubeadm) to backport the registry change back until v1.22

let's align and already use the new registry for Kubernetes >= v1.22

xrefs:

/kind feature
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 31, 2022
@sbueringer sbueringer mentioned this issue Oct 31, 2022
Merged
@sbueringer
Copy link
Member Author

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 31, 2022
@sbueringer sbueringer changed the title Use new Kubernetes registry with Kubernetes >= v1.22 Use new Kubernetes registry for Kubernetes >= v1.22 Oct 31, 2022
@sbueringer sbueringer added this to the v1.3 milestone Nov 3, 2022
@sbueringer
Copy link
Member Author

/reopen
until the cherry-pick is merged as well: #7505

@k8s-ci-robot k8s-ci-robot reopened this Nov 7, 2022
@k8s-ci-robot
Copy link
Contributor

@sbueringer: Reopened this issue.

In response to this:

/reopen
until the cherry-pick is merged as well: #7505

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.

@sbueringer sbueringer modified the milestones: v1.3, v1.2 Nov 30, 2022
@sbueringer
Copy link
Member Author

/close
cherry-pick is merged

@k8s-ci-robot
Copy link
Contributor

@sbueringer: Closing this issue.

In response to this:

/close
cherry-pick is merged

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.

@sbueringer sbueringer added kind/release-blocking Issues or PRs that need to be closed before the next CAPI release and removed release-blocking labels Feb 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. kind/release-blocking Issues or PRs that need to be closed before the next CAPI release triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
v1.2
Development

Successfully merging a pull request may close this issue.

🌱 KCP: use new registry for Kubernetes >= v1.22 sbueringer/cluster-api
2 participants
@sbueringer @k8s-ci-robot