You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The subnet CIDR defaults to VPC default which creates a new CIDR block of /18 for each zone. So I cannot install 2 LSF clusters in the same zone Or I if my on-prem network had the same CIDR as LSF default then the overlap would not allow me to connect them together.
ibm_is_subnet module uses VPC default but the module allows specifying a custom CIDR. It wouldn't be difficult to expose or accept a custom CIDR via terraform variables such Schematics can pick up and let customer choose default or a custom CIDR.
The text was updated successfully, but these errors were encountered:
hi @sam-andaluri yes, we acknowledge that the CIDR block overlap issue when trying to establish communication between LSF clusters needs to be addressed. We will look at allowing the user to specify a custom CIDR in a future release. Thanks for taking the time to provide this feedback.
The subnet CIDR defaults to VPC default which creates a new CIDR block of /18 for each zone. So I cannot install 2 LSF clusters in the same zone Or I if my on-prem network had the same CIDR as LSF default then the overlap would not allow me to connect them together.
ibm_is_subnet module uses VPC default but the module allows specifying a custom CIDR. It wouldn't be difficult to expose or accept a custom CIDR via terraform variables such Schematics can pick up and let customer choose default or a custom CIDR.
The text was updated successfully, but these errors were encountered: