Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1328986

Summary: [RFE] Automated way to configure or grow clusterNetworkCIDR without having down time.
Product: OpenShift Container Platform Reporter: Ryan Howe <rhowe>
Component: RFEAssignee: Ben Bennett <bbennett>
Status: CLOSED DEFERRED QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: aos-bugs, cstark, eparis, erich, jokerman, mbarrett, mcurry, mmccomas, pdwyer, rhowe, sreber
Target Milestone: ---Flags: mcurry: needinfo-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-12 13:54:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ryan Howe 2016-04-20 19:50:50 UTC 
Description of problem:

Supported and easy way to update both the clusterNetworkCIDR and serviceNetworkCIDR networks post installation. 

With IP space limited starting with a small OSE environment /16 is overkill.  Ability to change both Networks post installation would be great.

Additional info:

https://trello.com/c/bCmIOTeJ/17-13-spike-sdn-out-of-box-configuration-and-scale-sdn

Procedure today:
    Shut down the nodes
    Delete all entries in the hostsubnet table (oc delete hostsubnet --all)
    Edit the master-config.yaml to have the right clusterNetworkCIDR
    Restart the master
    Restart the nodes
Comment 1 Ben Bennett 2016-04-21 13:55:46 UTC 
Trello card:
  https://trello.com/c/cvxx3Q34/202-reconfigure-cluster-and-service-network-cidr-without-downtime
Comment 5 Eric Rich 2018-03-12 13:54:36 UTC 
This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.