大网数据广告活动
服务器运维问答

Kubernetes - Why Ingress resource is still marked as "beta"?

· 52CE 我爱测

Kubernetes 1.9 is now available. However, Ingress resource is still marked as "beta" in the Kubernetes documentation (see https://kubernetes.io/docs/concepts/services-networking/ingress/ : "The Ingress is a beta resource, not ava…

问题原文

原帖链接 · Sylmarch · CC BY-SA 3.0

Kubernetes 1.9 is now available.

However, Ingress resource is still marked as "beta" in the Kubernetes documentation (see https://kubernetes.io/docs/concepts/services-networking/ingress/ : "The Ingress is a beta resource, not available in any Kubernetes release prior to 1.1").

My questions are:

  • Why is the Ingress resource marked as beta? Because some features are missing or because the API may change?
  • Is it safe to use Ingress resources in a production Kubernetes cluster (on-premise cluster), especially with the official Nginx IngressControler (https://github.com/kubernetes/ingress-nginx)?

已采纳解答

原帖链接 · webwurst · CC BY-SA 3.0

It usually fine to use Kubernetes components that are marked as beta. The same is true for API resources:

  • Code is well tested. Enabling the feature is considered safe. Enabled by default.
  • Support for the overall feature will not be dropped, though details may change.

There is still a warning for incompatible changes in later releases:

  • Recommended for only non-business-critical uses because of potential for incompatible changes in subsequent releases. If you have multiple clusters which can be upgraded independently, you may be able to relax this restriction.

Regarding NGINX Ingress Controller: That is out of beta since early December.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2018-01-22)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。