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
By default we are using the public IP to SSH into the cluster. This covers the case where we assume someone is running this automation from a remote source, outside PowerVS. Eventually someone will have a full deployment only within PowerVS using private IPs, without using any route outside this environment.
I would be a good feature if we can select via TF which IP we want to use: bastion_public_ip or bastion_private_ip.
The text was updated successfully, but these errors were encountered:
By default we are using the public IP to SSH into the cluster. This covers the case where we assume someone is running this automation from a remote source, outside PowerVS. Eventually someone will have a full deployment only within PowerVS using private IPs, without using any route outside this environment.
I would be a good feature if we can select via TF which IP we want to use: bastion_public_ip or bastion_private_ip.
The text was updated successfully, but these errors were encountered: