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

change the image registry for container images from k8s.gcr.io to registry.k8s.io #636

Closed
tejarora opened this issue Mar 26, 2023 · 2 comments · Fixed by #651
Closed

change the image registry for container images from k8s.gcr.io to registry.k8s.io #636

tejarora opened this issue Mar 26, 2023 · 2 comments · Fixed by #651
Labels
bug Something isn't working

Comments

@tejarora
Copy link

Describe the bug
k8s.gcr.io registry is being retired. Your manifests use this registry.
See this announcement https://kubernetes.io/blog/2023/02/06/k8s-gcr-io-freeze-announcement/

Also provide steps in your documentation for those who have used your manifests on how to update their clusters.

Steps To Reproduce

Expected behavior
A clear and concise description of what you expected to happen.

Environment

  • Kubernetes version
  • Using EKS (yes/no), if so version?
  • Kubeflow version
  • AWS build number
  • AWS service targeted (S3, RDS, etc.)

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

@tejarora tejarora added the bug Something isn't working label Mar 26, 2023
@surajkota
Copy link
Contributor

surajkota commented Mar 31, 2023

Hi, thanks for opening the issue. We have identified that we have one component using this registry - secrets-store-csi-driver. Existing deployments wont be affected as of now but the guidance is to start using the new registry as soon as possible, all the old images are available in the new registry.

We will be providing guidance on how to update existing deployment deployments. Thank you for your patience in the meantime.

@ryansteakley
Copy link
Contributor

ryansteakley commented Apr 7, 2023

On February 6th, the Kubernetes project announced changes to the existing community-owned image registry called k8s.gcr.io to host its container images. On the 3rd of April 2023, the old registry k8s.gcr.io will be frozen and no further images for Kubernetes and related subprojects will be pushed to the old registry. The Kubernetes community recommends to start using the new registry.k8s.io as soon as possible. For more information read the community blog.

This only effects Secrets Store CSI Driver for those who have installed either RDS-S3/Cognito-RDS-S3 before v1.6.1-aws-b1.0.2. To update your pulled image source run the following kubectl commands

kubectl set image daemonset/csi-secrets-store node-driver-registrar=registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.3.0 -n kube-system
kubectl set image daemonset/csi-secrets-store secrets-store=registry.k8s.io/csi-secrets-store/driver:v1.0.0-rc.1 -n kube-system
kubectl set image daemonset/csi-secrets-store liveness-probe=registry.k8s.io/sig-storage/livenessprobe:v2.4.0 -n kube-system

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants