-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.19.z, 4.20.0, 4.21.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
Proposed
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Summary
Update the BGP enable/disable modules to use the current Network.operator API and valid oc patch invocations.
What changed
Use the fully qualified resource form and merge patch:
oc patch Network.operator.openshift.io/cluster --type=merge ...
Switch .spec.additionalRoutingCapabilities to the object form with providers:
Enable: {"spec":{"additionalRoutingCapabilities":{"providers":["FRR"]}}}
Disable: {"spec":{"additionalRoutingCapabilities":null}}
Why
The latest API defines additionalRoutingCapabilities as an object with a required providers array; "FRR" is the valid value. The old array-of-strings form is no longer correct.
The resource path Network.operator.openshift.io/cluster and --type=merge are consistent with current usage in docs and kubernetes examples.
Version-Release number of selected component (if applicable):
4.19+
Actual results:
Does not work
Expected results:
Commands run successfully
Additional info:
modules/nw-bgp-routing-enable.adoc modules/nw-bgp-routing-disable.adoc
