|
| 1 | +--- |
| 2 | +layout: blog |
| 3 | +title: '更新 NGINX-Ingress 以使用稳定的 Ingress API' |
| 4 | +date: 2021-07-26 |
| 5 | +slug: update-with-ingress-nginx |
| 6 | +--- |
| 7 | +<!-- |
| 8 | +layout: blog |
| 9 | +title: 'Updating NGINX-Ingress to use the stable Ingress API' |
| 10 | +date: 2021-07-26 |
| 11 | +slug: update-with-ingress-nginx |
| 12 | +--> |
| 13 | + |
| 14 | +<!-- |
| 15 | +**Authors:** James Strong, Ricardo Katz |
| 16 | +--> |
| 17 | +**作者:** James Strong, Ricardo Katz |
| 18 | + |
| 19 | +<!-- |
| 20 | +With all Kubernetes APIs, there is a process to creating, maintaining, and |
| 21 | +ultimately deprecating them once they become GA. The networking.k8s.io API group is no |
| 22 | +different. The upcoming Kubernetes 1.22 release will remove several deprecated APIs |
| 23 | +that are relevant to networking: |
| 24 | +--> |
| 25 | +对于所有 Kubernetes API,一旦它们被正式发布(GA),就有一个创建、维护和最终弃用它们的过程。 |
| 26 | +networking.k8s.io API 组也不例外。 |
| 27 | +即将发布的 Kubernetes 1.22 版本将移除几个与网络相关的已弃用 API: |
| 28 | + |
| 29 | +<!-- |
| 30 | +- the `networking.k8s.io/v1beta1` API version of [IngressClass](/docs/concepts/services-networking/ingress/#ingress-class) |
| 31 | +- all beta versions of [Ingress](/docs/concepts/services-networking/ingress/): `extensions/v1beta1` and `networking.k8s.io/v1beta1` |
| 32 | +--> |
| 33 | +- [IngressClass](/zh-cn/docs/concepts/services-networking/ingress/#ingress-class) 的 `networking.k8s.io/v1beta1` API 版本 |
| 34 | +- [Ingress](/zh-cn/docs/concepts/services-networking/ingress/) 的所有 Beta 版本: `extensions/v1beta1` 和 `networking.k8s.io/v1beta1` |
| 35 | + |
| 36 | +<!-- |
| 37 | +On a v1.22 Kubernetes cluster, you'll be able to access Ingress and IngressClass |
| 38 | +objects through the stable (v1) APIs, but access via their beta APIs won't be possible. |
| 39 | +--> |
| 40 | +在 v1.22 Kubernetes 集群上,你能够通过稳定版本(v1)的 API 访问 Ingress 和 IngressClass 对象, |
| 41 | +但无法通过其 Beta API 访问。 |
| 42 | +<!-- |
| 43 | +This change has been in |
| 44 | +in discussion since |
| 45 | +[2017](https://github.com/kubernetes/kubernetes/issues/43214), |
| 46 | +[2019](https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/) with |
| 47 | +1.16 Kubernetes API deprecations, and most recently in |
| 48 | +KEP-1453: |
| 49 | +[Graduate Ingress API to GA](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1453-ingress-api#122). |
| 50 | +--> |
| 51 | +自 [2017](https://github.com/kubernetes/kubernetes/issues/43214)、 |
| 52 | +[2019](https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/) |
| 53 | +以来一直讨论关于 Kubernetes 1.16 弃用 API 的更改, |
| 54 | +最近的讨论是在 KEP-1453:[Ingress API 毕业到 GA](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1453-ingress-api#122)。 |
| 55 | + |
| 56 | +<!-- |
| 57 | +During community meetings, the networking Special Interest Group has decided to continue |
| 58 | +supporting Kubernetes versions older than 1.22 with Ingress-NGINX version 0.47.0. |
| 59 | +Support for Ingress-NGINX will continue for six months after Kubernetes 1.22 |
| 60 | +is released. Any additional bug fixes and CVEs for Ingress-NGINX will be |
| 61 | +addressed on a need-by-need basis. |
| 62 | +--> |
| 63 | +在社区会议中,网络特别兴趣小组决定继续支持带有 0.47.0 版本 Ingress-NGINX 的早于 1.22 版本的 Kubernetes。 |
| 64 | +在 Kubernetes 1.22 发布后,对 Ingress-NGINX 的支持将持续六个月。 |
| 65 | +团队会根据需要解决 Ingress-NGINX 的额外错误修复和 CVE 问题。 |
| 66 | + |
| 67 | +<!-- |
| 68 | +Ingress-NGINX will have separate branches and releases of Ingress-NGINX to |
| 69 | +support this model, mirroring the Kubernetes project process. Future |
| 70 | +releases of the Ingress-NGINX project will track and support the latest |
| 71 | +versions of Kubernetes. |
| 72 | +--> |
| 73 | +Ingress-NGINX 将拥有独立的分支和发布版本来支持这个模型,与 Kubernetes 项目流程相一致。 |
| 74 | +Ingress-NGINX 项目的未来版本将跟踪和支持最新版本的 Kubernetes。 |
| 75 | + |
| 76 | +<!-- |
| 77 | +{{< table caption="Ingress NGINX supported version with Kubernetes Versions" >}} |
| 78 | +Kubernetes 版本 | Ingress-NGINX version | Notes |
| 79 | +:-------------------|:----------------------|:------------ |
| 80 | +v1.22 | v1.0.0-alpha.2 | New features, plus bug fixes. |
| 81 | +v1.21 | v0.47.x | Bugfixes only, and just for security issues or crashes. No end-of-support date announced. |
| 82 | +v1.20 | v0.47.x | Bugfixes only, and just for security issues or crashes. No end-of-support date announced. |
| 83 | +v1.19 | v0.47.x | Bugfixes only, and just for security issues or crashes. Fixes only provided until 6 months after Kubernetes v1.22.0 is released. |
| 84 | +{{< /table >}} |
| 85 | +--> |
| 86 | +{{< table caption="Kubernetes 各版本支持的 Ingress NGINX 版本" >}} |
| 87 | +Kubernetes 版本 | Ingress-NGINX 版本 | 公告 |
| 88 | +:-------------------|:----------------------|:------------ |
| 89 | +v1.22 | v1.0.0-alpha.2 | 新特性,以及错误修复。 |
| 90 | +v1.21 | v0.47.x | 仅修复安全问题或系统崩溃的错误。没有宣布终止支持日期。 |
| 91 | +v1.20 | v0.47.x | 仅修复安全问题或系统崩溃的错误。没有宣布终止支持日期。 |
| 92 | +v1.19 | v0.47.x | 仅修复安全问题或系统崩溃的错误。仅在 Kubernetes v1.22.0 发布后的 6 个月内提供修复支持。 |
| 93 | +{{< /table >}} |
| 94 | + |
| 95 | +<!-- |
| 96 | +Because of the updates in Kubernetes 1.22, **v0.47.0** will not work with |
| 97 | +Kubernetes 1.22. |
| 98 | +--> |
| 99 | +由于 Kubernetes 1.22 中的更新,**v0.47.0** 将无法与 Kubernetes 1.22 一起使用。 |
| 100 | + |
| 101 | +<!-- |
| 102 | +# What you need to do |
| 103 | +--> |
| 104 | +## 你需要做什么 |
| 105 | + |
| 106 | +<!-- |
| 107 | +The team is currently in the process of upgrading ingress-nginx to support |
| 108 | +the v1 migration, you can track the progress |
| 109 | +[here](https://github.com/kubernetes/ingress-nginx/pull/7156). |
| 110 | +We're not making feature improvements to `ingress-nginx` until after the support for |
| 111 | +Ingress v1 is complete. |
| 112 | +--> |
| 113 | +团队目前正在升级 Ingress-NGINX 以支持向 v1 的迁移, |
| 114 | +你可以在[此处](https://github.com/kubernetes/ingress-nginx/pull/7156)跟踪进度。 |
| 115 | +在对 Ingress v1 的支持完成之前, |
| 116 | +我们不会对功能进行改进。 |
| 117 | + |
| 118 | +<!-- |
| 119 | +In the meantime to ensure no compatibility issues: |
| 120 | +--> |
| 121 | +同时,团队会确保没有兼容性问题: |
| 122 | + |
| 123 | +<!-- |
| 124 | +* Update to the latest version of Ingress-NGINX; currently |
| 125 | + [v0.47.0](https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v0.47.0) |
| 126 | +--> |
| 127 | +* 更新到最新的 Ingress-NGINX 版本, |
| 128 | + 目前是 [v0.47.0](https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v0.47.0)。 |
| 129 | +<!-- |
| 130 | +* After Kubernetes 1.22 is released, ensure you are using the latest version of |
| 131 | + Ingress-NGINX that supports the stable APIs for Ingress and IngressClass. |
| 132 | +--> |
| 133 | +* Kubernetes 1.22 发布后,请确保使用的是支持 Ingress 和 IngressClass 稳定 API 的最新版本的 Ingress-NGINX。 |
| 134 | +<!-- |
| 135 | +* Test Ingress-NGINX version v1.0.0-alpha.2 with Cluster versions >= 1.19 |
| 136 | + and report any issues to the projects Github page. |
| 137 | +--> |
| 138 | +* 使用集群版本 >= 1.19 测试 Ingress-NGINX 版本 v1.0.0-alpha.2,并将任何问题报告给项目 GitHub 页面。 |
| 139 | + |
| 140 | +<!-- |
| 141 | +The community’s feedback and support in this effort is welcome. The |
| 142 | +Ingress-NGINX Sub-project regularly holds community meetings where we discuss |
| 143 | +this and other issues facing the project. For more information on the sub-project, |
| 144 | +please see [SIG Network](https://github.com/kubernetes/community/tree/master/sig-network). |
| 145 | +--> |
| 146 | +欢迎社区对此工作的反馈和支持。 |
| 147 | +Ingress-NGINX 子项目定期举行社区会议, |
| 148 | +我们会讨论这个问题以及项目面临的其他问题。 |
| 149 | +有关子项目的更多信息,请参阅 [SIG Network](https://github.com/kubernetes/community/tree/master/sig-network)。 |
0 commit comments