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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: