英文:
How to migrate Ingress Nginx Controller from k8s.gcr.io to registry.k8s.io?
问题
我已阅读到称为 k8s.gcr.io 的容器注册表即将被删除。
从该存储库中拉取的任何容器必须迁移到替代者：registry.k8s.io。
对于已经使用传统方式的现有工作负载，我该如何在GCP GKE中进行更改？
这会对Ingress IP地址、SSL证书、任何停机时间等造成问题吗？
英文:
I read that the Container Registry called k8s.gcr.io is about to be removed soon.
Any container pulls from this repository must migrate to the replacer: registry.k8s.io.
How can I change this in GCP GKE for existing workloads that already use the legacy?
Will it cause issues on Ingress IP address, SSL certs, any downtime etc?
答案1
得分: 2
根据这份官方文档，k8s.gcr.io将会被重定向到registry.k8s.io，按照社区的公告。这个变化将会逐渐进行，以减少中断，并且应该对大多数GKE集群是透明的。
> 对于运行在受限环境中的受影响用户，最佳选择是将所需的镜像复制到私有注册表，或在其注册表中配置拉取缓存。
>
> 有几种工具可以在注册表之间复制镜像；crane是其中之一，可以使用crane copy SRC DST将镜像复制到私有注册表。还有一些特定于供应商的工具，如Google的gcrane，执行类似的功能但针对其平台进行了优化。您还可以参考文档中列出的选项进行进一步的故障排除。
>
> 如果您认为遇到了新注册表或重定向的错误，请在https://github.com/kubernetes/registry.k8s.io/issues中提出问题。
英文:
As per this official doc , k8s.gcr.io will be redirected to registry.k8s.io, following the community announcement. This change will happen gradually to reduce disruption, and should be transparent to the majority of GKE clusters.
> For impacted users that run in a restricted environment, the best
> option is to copy over the required images to a private registry or
> configure a pull-through cache in their registry.
>
> There are several tools to copy images between registries; crane is
> one of those tools, and images can be copied to a private registry by
> using crane copy SRC DST. There are also vendor-specific tools, like
> e.g. Google’s gcrane, that perform a similar function but are
> streamlined for their platform. You can also refer to the options
> listed in the doc and troubleshoot further.
>
> If you believe you have encountered a bug with the new registry or the
> redirect, please open an issue in the
> https://github.com/kubernetes/registry.k8s.io/issues.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论