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
Anything else do we need to know:
This bug is introduced from changes made in #4291.
If you don't deploy with a bastion (number_of_bastions = 0 in your terraform variables file) the security group is never created and no other rules exist for allowing SSH from outside your cluster.
The text was updated successfully, but these errors were encountered:
I've reproduced this as well. Even is number_of_bastion = 0, the bastion security group is used for SSH access. Therefore there is no situation where the bastion security group is not needed.
@Miouge1 I just had a similar issue. I've set number_of_bastions = 0 and wanted to test connectivity using ansible -vvv -i inventory/$CLUSTER/hosts -m ping all. I'm unable to connect to the master using ssh.
My master node (spray1st-k8s-master-1) is NOT using the security group spray1st-bastion but only spray1st-k8s-master and spray1st-k8s. Once I add spray1st-bastion to the master manually, everything works.
Cloud provider or hardware configuration: OpenStack
/kind bug
Environment:
printf "$(uname -srm)\n$(cat /etc/os-release)\n"
):ansible --version
):Kubespray version (commit) (
git rev-parse --short HEAD
):e865c50
Output of ansible run:
Anything else do we need to know:
This bug is introduced from changes made in #4291.
If you don't deploy with a bastion (
number_of_bastions = 0
in your terraform variables file) the security group is never created and no other rules exist for allowing SSH from outside your cluster.The text was updated successfully, but these errors were encountered: