-
Feature Request
-
Resolution: Done
-
Normal
-
None
-
False
-
False
-
Undefined
-
-
-
-
- Proposed title of this feature request:
- "SDN: Allow expanding ClusterNetworks and ServiceNetworks
- What is the nature and description of the request?
- In OpenShift 3.x, we had a procedure for expanding the ClusterCIDR of an existing cluster without disrupting running workloads. It was, however, manual and error prone. Now that we have the cluster network operator, we should once again allow this operation
- Out of scope:
- Renumbering nodes, especially master nodes
- Changing any of the cidrs except growth.
- Why does the customer need this?
Clusters that grow organically may run out of pod or service IP space. There are safe ways to expand - List any affected packages or components. cluster-network-operator, openshift-sdn, ovn-kubernetes. The openshift-kube-apiserver-operator may also need some minor work.
- is cloned by
-
SDN-1658 Allow Expanding ClusterNetworks
- Closed
- is incorporated by
-
OCPSTRAT-1242 Allow modifying ServiceNetworks post installation
- New
- is related to
-
SDN-3606 [R&D] Allow modifying ServiceNetworks post installation
- New
-
OCPSTRAT-1242 Allow modifying ServiceNetworks post installation
- New
- links to