7 minute read
Feature Gates in Gardener
This page contains an overview of the various feature gates an administrator can specify on different Gardener components.
Feature gates are a set of key=value pairs that describe Gardener features. You can turn these features on or off using the a component configuration file for a specific component.
Each Gardener component lets you enable or disable a set of feature gates that are relevant to that component. For example this is the configuration of the gardenlet component.
The following tables are a summary of the feature gates that you can set on different Gardener components.
- The “Since” column contains the Gardener release when a feature is introduced or its release stage is changed.
- The “Until” column, if not empty, contains the last Gardener release in which you can still use a feature gate.
- If a feature is in the Alpha or Beta state, you can find the feature listed in the Alpha/Beta feature gate table.
- If a feature is stable you can find all stages for that feature listed in the Graduated/Deprecated feature gate table.
- The Graduated/Deprecated feature gate table also lists deprecated and withdrawn features.
Feature gates for Alpha or Beta features
Feature gates for graduated or deprecated features
Using a feature
A feature can be in Alpha, Beta or GA stage. An Alpha feature means:
- Disabled by default.
- Might be buggy. Enabling the feature may expose bugs.
- Support for feature may be dropped at any time without notice.
- The API may change in incompatible ways in a later software release without notice.
- Recommended for use only in short-lived testing clusters, due to increased risk of bugs and lack of long-term support.
A Beta feature means:
- Enabled by default.
- The feature is well tested. Enabling the feature is considered safe.
- Support for the overall feature will not be dropped, though details may change.
- The schema and/or semantics of objects may change in incompatible ways in a subsequent beta or stable release. When this happens, we will provide instructions for migrating to the next version. This may require deleting, editing, and re-creating API objects. The editing process may require some thought. This may require downtime for applications that rely on the feature.
- Recommended for only non-critical uses because of potential for incompatible changes in subsequent releases.
Please do try Beta features and give feedback on them! After they exit beta, it may not be practical for us to make more changes.
A General Availability (GA) feature is also referred to as a stable feature. It means:
- The feature is always enabled; you cannot disable it.
- The corresponding feature gate is no longer needed.
- Stable versions of features will appear in released software for many subsequent versions.
List of Feature Gates
|HVPA||Enables simultaneous horizontal and vertical scaling in Seed Clusters.|
|HVPAForShootedSeed||Enables simultaneous horizontal and vertical scaling in managed seed (aka “shooted seed”) clusters.|
|ManagedIstio||Enables a Gardener-tailored Istio in each Seed cluster. Disable this feature if Istio is already installed in the cluster. Istio is not automatically removed if this feature is disabled. See the detailed documentation for more information.|
|APIServerSNI||Enables only one LoadBalancer to be used for every Shoot cluster API server in a Seed. Enable this feature when |
|CachedRuntimeClients||Enables a cache in the controller-runtime clients, that Gardener components use. The feature gate can be specified for gardenlet and gardener-controller-manager (and gardener-scheduler for the versions |
|SeedChange||Enables updating the |
|SeedKubeScheduler||Adds custom |
|ReversedVPN||Reverses the connection setup of the vpn tunnel between the Seed and the Shoot cluster(s). It allows Seed and Shoot clusters to be in different networks with only direct access in one direction (Shoot -> Seed). In addition to that, it reduces the amount of load balancers required, i.e. no load balancers are required for the vpn tunnel anymore. It requires |
|AdminKubeconfigRequest||Enables the |
|UseDNSRecords||Enables using |
|RotateSSHKeypairOnMaintenance||Enables SSH keypair rotation in the maintenance controller of the gardener-controller-manager. Details can be found in GEP-15.|
|DenyInvalidExtensionResources||Causes the |
|WorkerPoolKubernetesVersion||Allows to overwrite the Kubernetes version used for shoot clusters per worker pool (see this document)|
|CopyEtcdBackupsDuringControlPlaneMigration||Enables the copy of etcd backups from the object store of the source seed to the object store of the destination seed during control plane migration.|
|SecretBindingProviderValidation||Enables validations on Gardener API server that:|
- requires the provider type of a SecretBinding to be set (on SecretBinding creation)
- requires the SecretBinding provider type to match the Shoot provider type (on Shoot creation)
- enforces immutability on the provider type of a SecretBinding
|ForceRestore||Enables forcing the shoot’s restoration to the destination seed during control plane migration if the preparation for migration in the source seed is not finished after a certain grace period and is considered unlikely to succeed (falling back to the control plane migration “bad case” scenario). If you enable this feature gate, make sure to also enable |
|DisableDNSProviderManagement||Disables management of |
|ShootCARotation||Enables the feature to trigger automated CA rotation for shoot clusters.|
|ShootMaxTokenExpirationOverwrite||Makes the Gardener API server overwriting values in the |
- be at least 720h (30d) when the current value is lower
- be at most 2160h (90d) when the current value is higher
before persisting the object to etcd.
|ShootMaxTokenExpirationValidation||Enables validations on Gardener API server that enforce that the value of the |
- is at least 720h (30d).
- is at most 2160h (90d).
Only enable this after
Was this page helpful?