/kind feature
/area provider/ibmcloud
Describe the solution you'd like
A customer is asking for the ability for an OpenShift cluster to be disaster resistant. If a data center goes down then the cluster can still function.
An example of this is to create single master nodes over different zones. For example:
dal10, dal12, and dal13.
We could also spread the worker nodes over the different zones.
The PowerEdgeRouter has the ability to link the VPC along with multiple Service Instances. The only extra thing which would need to happen is to add some more routing to the CoreOS OS. (NOTE: I don't expect IBM CAPI to do this one part)
The IBMPowerVSMachineSpec structure already uses IBMPowerVSResourceReference as the ServiceInstance. I would think that the IBMPowerVSClusterSpec structure should be changed to support an array of IBMPowerVSResourceReference.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
/kind feature
/area provider/ibmcloud
Describe the solution you'd like
A customer is asking for the ability for an OpenShift cluster to be disaster resistant. If a data center goes down then the cluster can still function.
An example of this is to create single master nodes over different zones. For example:
dal10,dal12, anddal13.We could also spread the worker nodes over the different zones.
The PowerEdgeRouter has the ability to link the VPC along with multiple Service Instances. The only extra thing which would need to happen is to add some more routing to the CoreOS OS. (NOTE: I don't expect IBM CAPI to do this one part)
The
IBMPowerVSMachineSpecstructure already usesIBMPowerVSResourceReferenceas theServiceInstance. I would think that theIBMPowerVSClusterSpecstructure should be changed to support an array ofIBMPowerVSResourceReference.Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]