Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore allowing the use of an existing VCN and/or Bastion service instance #44

Open
michael-cico opened this issue Sep 28, 2021 · 3 comments

Comments

@michael-cico
Copy link

When support is added for using the OCI bastion service for SSH and port-forwarding for private cluster endpoints, it would be useful if the module could accept an existing VCN/Subnet and OCI bastion configuration instead of creating its own.

We have a use case for test clusters where we wish to use a single VCN and a single bastion instance to support multiple OKE test clusters. So, ideally we could provide the VCN/Subnet/Bastion OCIDs and the module would simply make use of those.

@arruko
Copy link

arruko commented Oct 3, 2021

Hi, I have a similar use case where I need to address specific requirements on the VCN and subnets architecture, so for the bastion host I need to specify the subnet ID instead of creating a new one.

@michael-cico
Copy link
Author

Actually another factor is that Bastions are typically a scarce resource (5 by default per tenancy). So the ability to reuse them is important.

@shb-mll
Copy link

shb-mll commented Apr 11, 2023

Hi, I have a similar requirement where I need the bastion module to take an existing subnet ID instead of creating a new one.
any traction on this ?

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

No branches or pull requests

3 participants