SSH not working when Bring-your-own-VPC is used
ScheererJ opened this issue · comments
What happened:
Connecting to a shoot cluster via ssh with gardenctl failed when the shoot cluster brought its own VPC instead of having it created by gardener.
Still waiting: bastion does not have BastionReady=true condition
An error occurred while waiting: timed out waiting for the bastion to become ready: bastion does not have BastionReady=true condition
What you expected to happen:
I expect gardenctl ssh to work regardless of whether the VPC is created by gardener or not.
How to reproduce it (as minimally and precisely as possible):
Try to ssh into a shoot cluster with spec.provider.infrastructureConfig.networks.vpc.name (for gcp) that is not equal to the shoot name.
Anything else we need to know:
The exact location of the vpc name and the support for bring-your-own-vpc may depend on the infrastructure extension.
Environment:
GCP.
/cc @DockToFuture
@ScheererJ I have transferred this issue to gardener-extension-provider-gcp where the bastion controller for gcp is implemented
cc @tedteng
/assign