Merge pull request #34809 from jboxman/bz-1939314

BZ#1939314: The FeatureGate API is not namespaced

Author: jboxman

modules/nodes-cluster-enabling-features-about.adoc

@@ -5,7 +5,7 @@
 [id="nodes-cluster-enabling-features-about_{context}"]
 = Understanding feature gates
 
-You can use the `FeatureGate` custom resource (CR) to enable specific feature sets in your cluster. A feature set is a collection of {product-title} features that are not enabled by default. 
+You can use the `FeatureGate` custom resource (CR) to enable specific feature sets in your cluster. A feature set is a collection of {product-title} features that are not enabled by default.
 
 For example, the `TechPreviewNoUpgrade` feature set allows you to enable a subset of the current Technology Preview features on test clusters, where you can fully test them, while leaving the features disabled on production clusters.
 

modules/nodes-cluster-enabling-features-cli.adoc

@@ -15,11 +15,11 @@ You can use the OpenShift CLI (`oc`) to enable feature sets for all of the nodes
 
 To enable feature sets:
 
-. Edit the `FeatureGate` CR, named `cluster`, in the `openshift-config` project:
+. Edit the `FeatureGate` CR named `cluster`:
 +
 [source,terminal]
 ----
-$ oc edit featuregate cluster -n openshift-config
+$ oc edit featuregate cluster
 ----
 +
 .Sample FeatureGate custom resource
@@ -29,7 +29,6 @@ apiVersion: config.openshift.io/v1
 kind: FeatureGate
 metadata:
   name: cluster <1>
-...
 spec:
   featureSet: TechPreviewNoUpgrade <2>
 ----