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

switch the default image registry in image builder to registry.k8s.io #845

Closed
neolit123 opened this issue Mar 24, 2022 · 6 comments · Fixed by #956
Closed

switch the default image registry in image builder to registry.k8s.io #845

neolit123 opened this issue Mar 24, 2022 · 6 comments · Fixed by #956
Labels
kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@neolit123
Copy link
Member

this is an item for the k8s 1.25 release cycle.
switch the default image registry in image builder to registry.k8s.io after kubeadm switches to it:
kubernetes/kubeadm#2671

more info:
https://groups.google.com/g/kubernetes-sig-testing/c/U7b_im9vRrM/m/7qywJeUTBQAJ
xref #844
xref kubernetes/k8s.io#1834
@neolit123
Copy link
Member Author

/kind feature deprecation
/priority important-longterm

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Mar 24, 2022
@neolit123 neolit123 mentioned this issue Mar 24, 2022
Closed
@hh hh moved this from Backlog to Breakdown TODO in registry.k8s.io (SIG K8S Infra) Mar 31, 2022
@ameukam ameukam moved this from Breakdown TODO to Backlog in registry.k8s.io (SIG K8S Infra) Apr 27, 2022
@ameukam ameukam moved this from Backlog to Implementation TODO in registry.k8s.io (SIG K8S Infra) Jun 22, 2022
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 22, 2022
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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 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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 22, 2022
@ameukam
Copy link
Member

ameukam commented Aug 4, 2022

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 4, 2022
@AverageMarcus
Copy link
Member

I just hit this issue today trying to build the new v1.25.0 build. It's trying to pull coredns:v1.9.3 from the old registry which doesn't exist.

@AverageMarcus AverageMarcus mentioned this issue Aug 24, 2022
Merged
@neolit123
Copy link
Member Author

likely related to https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/#custom-images
and it depends on the kubeadm version. 1.25 will threat registry.k8s.io as the default and the coredns path differs between default and non default registry.

Repository owner moved this from Implementation TODO to Breakdown Done in registry.k8s.io (SIG K8S Infra) Aug 30, 2022
@riaankleinhans riaankleinhans moved this from Breakdown Done to Validation Done in registry.k8s.io (SIG K8S Infra) Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: updated image registry to new domain giantswarm/image-builder
5 participants
@neolit123 @ameukam @AverageMarcus @k8s-ci-robot @k8s-triage-robot