Skip to content
This repository has been archived by the owner on Oct 31, 2019. It is now read-only.

Add support for provisioning a cluster in an existing VCN (i.e. shared VCN) #72

Open
jlamillan opened this issue Dec 15, 2017 · 4 comments
Assignees

Comments

@jlamillan
Copy link
Contributor

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.

@jlamillan
Copy link
Contributor Author

See also #77

@garthy
Copy link
Member

garthy commented Mar 20, 2018

This is also needed #168

@garthy garthy self-assigned this Mar 20, 2018
@beide
Copy link

beide commented Apr 20, 2018

I want to use existing VCN features. is the enhancement ready for me to use? Thanks

@AdityaVishwekar
Copy link

Workaround -
Inside 'network/vcn' folder :

  1. Comment out resource "oci_core_virtual_network"
  2. 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
  3. Define variables in variables.tf -
    `variable "vz_vcn_id" {
    default = "Put vcn ocid"
    }

variable "vz_vcn_dhcpoptions_id" {
default = "Put dhcpoption ocid"
} `

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants