apiVersion: config.openshift.io/v1
kind: FeatureGate
metadata:
name: cluster (1)
....
spec:
featureSet: TechPreviewNoUpgrade (2)
As an administrator, you can use feature gates to enable features that are not part of the default set of features.
You can use the FeatureGate
custom resource (CR) to enable specific feature sets in your cluster. A feature set is a collection of OpenShift Container Platform features that are not enabled by default.
You can activate any of the following feature sets by using the FeatureGate
CR:
TechPreviewNoUpgrade
. This feature set is a subset of the current Technology Preview features. This feature set allows you to enable these tech preview features on test clusters, where you can fully test them, while leaving the features disabled on production clusters. Enabling this feature set cannot be undone and prevents minor version updates. This feature set is not recommended on production clusters.
Enabling the |
The following Technology Preview features are enabled by this feature set:
Azure Disk CSI Driver Operator. Enables the provisioning of persistent volumes (PVs) by using the Container Storage Interface (CSI) driver for Microsoft Azure Disk Storage.
VMware vSphere CSI Driver Operator. Enables the provisioning of persistent volumes (PVs) by using the Container Storage Interface (CSI) VMware vSphere driver for Virtual Machine Disk (VMDK) volumes.
CSI automatic migration. Enables the automatic migration of supported in-tree volume plugins to their equivalent Container Storage Interface (CSI) drivers. Available as a Technology Preview for:
Amazon Web Services (AWS) Elastic Block Storage (EBS)
OpenStack Cinder
For more information about the features activated by the TechPreviewNoUpgrade
feature gate, see the following topics:
You can use the OpenShift Container Platform web console to enable feature sets for all of the nodes in a cluster by editing the FeatureGate
custom resource (CR).
To enable feature sets:
In the OpenShift Container Platform web console, switch to the Administration → Custom Resource Definitions page.
On the Custom Resource Definitions page, click FeatureGate.
On the Custom Resource Definition Details page, click the Instances tab.
Click the cluster feature gate, then click the YAML tab.
Edit the cluster instance to add specific feature sets:
Enabling the |
apiVersion: config.openshift.io/v1
kind: FeatureGate
metadata:
name: cluster (1)
....
spec:
featureSet: TechPreviewNoUpgrade (2)
1 | The name of the FeatureGate CR must be cluster . |
2 | Add the feature set that you want to enable:
|
After you save the changes, new machine configs are created, the machine config pools are updated, and scheduling on each node is disabled while the change is being applied.
You can verify that the feature gates are enabled by looking at the kubelet.conf
file on a node after the nodes return to the ready state.
From the Administrator perspective in the web console, navigate to Compute → Nodes.
Select a node.
In the Node details page, click Terminal.
In the terminal window, change your root directory to /host
:
sh-4.2# chroot /host
View the kubelet.conf
file:
sh-4.2# cat /etc/kubernetes/kubelet.conf
...
featureGates:
InsightsOperatorPullingSCA: true,
LegacyNodeRoleBehavior: false
...
The features that are listed as true
are enabled on your cluster.
The features listed vary depending upon the OpenShift Container Platform version. |
You can use the OpenShift CLI (oc
) to enable feature sets for all of the nodes in a cluster by editing the FeatureGate
custom resource (CR).
You have installed the OpenShift CLI (oc
).
To enable feature sets:
Edit the FeatureGate
CR named cluster
:
$ oc edit featuregate cluster
Enabling the |
apiVersion: config.openshift.io/v1
kind: FeatureGate
metadata:
name: cluster (1)
spec:
featureSet: TechPreviewNoUpgrade (2)
1 | The name of the FeatureGate CR must be cluster . |
2 | Add the feature set that you want to enable:
|
After you save the changes, new machine configs are created, the machine config pools are updated, and scheduling on each node is disabled while the change is being applied.
You can verify that the feature gates are enabled by looking at the kubelet.conf
file on a node after the nodes return to the ready state.
From the Administrator perspective in the web console, navigate to Compute → Nodes.
Select a node.
In the Node details page, click Terminal.
In the terminal window, change your root directory to /host
:
sh-4.2# chroot /host
View the kubelet.conf
file:
sh-4.2# cat /etc/kubernetes/kubelet.conf
...
featureGates:
InsightsOperatorPullingSCA: true,
LegacyNodeRoleBehavior: false
...
The features that are listed as true
are enabled on your cluster.
The features listed vary depending upon the OpenShift Container Platform version. |