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
{{ message }}
This repository has been archived by the owner on Oct 31, 2019. It is now read-only.
Currently, each cluster creates a brand new VCN, subnets, reoute tables, etc. for each cluster. It would be nice if we supported the ability to provision subsequent clusters into an an existing VCN.
The text was updated successfully, but these errors were encountered:
Replace "oci_core_virtual_network.CompleteVCN.id" with "var.vz_vcn_id" and "oci_core_virtual_network.CompleteVCN.default_dhcp_options_id" with "var.vz_vcn_dhcpoptions_id" in securitylists.tf, subnets.tf, vcn.tf
Currently, each cluster creates a brand new VCN, subnets, reoute tables, etc. for each cluster. It would be nice if we supported the ability to provision subsequent clusters into an an existing VCN.
The text was updated successfully, but these errors were encountered: