确保对GKE的效果，该效果从升级到GKE的v1.23的云代表器
我有一些云作曲家。
升级到 GKE v1.23 对 Cloud Composer 有影响吗？ https://cloud.google.com/kubernetes-engine/docs/deprecations/ webhookcompatibility
虽然我检查了后端服务是否有可能受到影响，但我认为不存在。
I have some cloud composer.
Is upgrading to v1.23 of GKE effect to cloud composer?
https://cloud.google.com/kubernetes-engine/docs/deprecations/webhookcompatibility
Although I inspected backend service which has possibility to be impact, I thought no exist.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
请勿将 Cloud Composer 环境中的 GKE 集群升级到更新版本，除非 Cloud Composer 发行说明 或已知问题页 。使用创建环境时预配置的 GKE 版本，并利用 GKE 服务的自动升级。
所有现有 Cloud Composer 的 GKE 集群都将自动升级到较新的 GKE 版本，并修复 CVE-2021-25741。新的 GKE 版本定期发布，但未选择版本立即自动升级。当 GKE 版本获得足够的集群使用量以证明随着时间的推移的稳定性时，Google 会选择它作为运行旧版本子集的集群的自动升级目标。新的自动升级目标已在发行说明中公布。
建议的最佳实践是利用 GKE 服务提供的自动升级，这样集群版本和 Composer 版本将保持同步，从而避免 不兼容性问题。
Do not upgrade GKE clusters in your Cloud Composer environment to a newer version unless specifically stated in the Cloud Composer Release Notes or the Known Issues page . Use the GKE version that was preconfigured when you created the environment and take advantage of the automatic upgrade of the GKE Service.
All existing Cloud Composer's GKE clusters will be auto-upgraded to newer GKE versions with a fix for the issues described in CVE-2021-25741. New GKE versions are released regularly, but a version is not selected for auto-upgrade right away. When a GKE version has acquired enough cluster usage to prove stability over time, Google selects it as an auto-upgrade target for clusters running a subset of older versions.New auto-upgrade targets are announced in the release notes.
The recommended best practice that is suggested would be to take advantage of the automatic upgrade provided by GKE Service, so the cluster version and composer version will be in sync which avoids incompatibility issues.