Upstream Kubernetes includes feature gates, which enable or disable features with flags and track the maturity of a feature using feature stages. Here in the Kubernetes Ingress Controller (KIC), we use the same definitions of
feature gates and
feature stages from upstream Kubernetes to define our own list of features.
Using feature gates enables contributors to add and manage new (and potentially experimental) functionality to the KIC in a controlled manner. The features will be “hidden” until generally available (GA) and the progress and maturity of features on their path to GA will be documented. Feature gates also create a clear path for deprecating features.
See below for current features and their statuses, and follow the links to the relevant feature documentation:
Feature gates for alpha and beta features
Features that reach GA and become stable are removed from this table, but they can be found in the main KIC CRD documentation and guides. This table is an overview of features at various maturity levels:
Feature gates details
- The since and until rows in the table refer to KIC Releases.
- Most features will be planned using Kubernetes Enhancement Proposals (KEP). If you’re interested in developing features, familiarize yourself with our KEPs.
- Features that are currently in alpha or beta states may become deprecated at any time. Deprecated features are removed during the next minor release.
- Until a feature becomes GA, there are no guarantees that it’s going to continue being available. For more information, see the changelog.
Important: To avoid disruption to your services consider not using features until they have reached GA status.
You can find feature preview documentation for alpha maturity features in the kubernetes-ingress-controller repository..