Skip to content

Commit b82ef7a

Browse files
committed
Add extra comment into feature rollback
Signed-off-by: Ricardo Pchevuzinske Katz <ricardo.katz@gmail.com>
1 parent 894e58e commit b82ef7a

File tree

1 file changed

+7
-3
lines changed
  • keps/sig-network/2079-network-policy-port-range

1 file changed

+7
-3
lines changed

keps/sig-network/2079-network-policy-port-range/README.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -232,9 +232,13 @@ _This section must be completed when targeting alpha to a release._
232232

233233
* **Can the feature be disabled once it has been enabled (i.e. can we roll back
234234
the enablement)?**
235-
Yes, fields created before feature gate being disabled will not be dropped unless the user removes it from the object.
236-
If the user removes the field from the object it will be dropped and the
237-
field can only be re-inserted if feature gate is enabled again.
235+
236+
Yes. One caveat here is that NetworkPolicies created with EndPort field set
237+
when the feature was enabled will continue to have that field set when the
238+
feature is disabled unless user removes it from the object.
239+
240+
If the value is dropped with the FeatureGate disabled, the field can only
241+
be re-inserted if feature gate is enabled again.
238242

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

0 commit comments

Comments
 (0)