Merge pull request #3054 from kevindelgado/2885-update-feature-gate-name

2885 - Update feature gate name

keps/sig-api-machinery/2885-server-side-unknown-field-validation/README.md

@@ -646,7 +646,7 @@ This section must be completed when targeting alpha to a release.
 Pick one of these and delete the rest.
 -->
 - [x] Feature gate (also fill in values in `kep.yaml`)
-  - Feature gate name: UnknownFieldValidation
+  - Feature gate name: ServerSideFieldValidation
   - Components depending on the feature gate: kube-apiserver
 - [x] Other
   - Describe the mechanism: query parameter
@@ -662,7 +662,7 @@ No, strict validation is false by default.
 ###### Can the feature be disabled once it has been enabled (i.e. can we roll back the enablement)?
 
 Yes. From the cluster operator's side, they can restart the kube-apiserver without
-the UnknownFieldValidation flag set and this will disable the feature
+the ServerSideFieldValidation flag set and this will disable the feature
 cluster-wide.
 
 For end-users that no longer wish to perform server-side strict validation,

keps/sig-api-machinery/2885-server-side-unknown-field-validation/kep.yaml

@@ -40,7 +40,7 @@ milestone:
 # The following PRR answers are required at alpha release
 # List the feature gate name and the components for which it must be enabled
 feature-gates:
-  - name: UnknownFieldValidation
+  - name: ServerSideFieldValidation
     components:
       - kube-apiserver
 disable-supported: true