Skip to content

Commit

Permalink
Add extra comment into feature rollback
Browse files Browse the repository at this point in the history
Signed-off-by: Ricardo Pchevuzinske Katz <[email protected]>
  • Loading branch information
rikatz committed Jan 26, 2021
1 parent 894e58e commit b82ef7a
Showing 1 changed file with 7 additions and 3 deletions.
10 changes: 7 additions & 3 deletions keps/sig-network/2079-network-policy-port-range/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -232,9 +232,13 @@ _This section must be completed when targeting alpha to a release._

* **Can the feature be disabled once it has been enabled (i.e. can we roll back
the enablement)?**
Yes, fields created before feature gate being disabled will not be dropped unless the user removes it from the object.
If the user removes the field from the object it will be dropped and the
field can only be re-inserted if feature gate is enabled again.

Yes. One caveat here is that NetworkPolicies created with EndPort field set
when the feature was enabled will continue to have that field set when the
feature is disabled unless user removes it from the object.

If the value is dropped with the FeatureGate disabled, the field can only
be re-inserted if feature gate is enabled again.

Rolling back the Kubernetes API Server that does not have this field
will make the field not be returned anymore on GET operations,
Expand Down

0 comments on commit b82ef7a

Please sign in to comment.