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 i use your repo to start a cluster, everything works great, but i have one issue.
When the cert signing for the master node has to happen, the request gets created, but it keeps in a pending state, the script continue and completes.
When i log into the cluster all the nodes are there but the master, the one where the cert signing is pending.
I reset the cluster and started the playbook again, this time keeping an eye for when the cert signing request gets done, and then I approved the request by hand, and that fixed the issue, and i could see all nodes on the cluster.
What could cause the cert signing to be stuck in pending, and i have to do it by hand??
Thank you for he awesome work so far, and any help will be greatly appreciated.
Cheers
The text was updated successfully, but these errors were encountered:
are you behind your corporate firewall? Have they put in some ssl security policy to protect from man in the middle attack? You can verify it by using a host which directly connects to the internet without proxies or firewalls or VPNs
Hi
When i use your repo to start a cluster, everything works great, but i have one issue.
When the cert signing for the master node has to happen, the request gets created, but it keeps in a pending state, the script continue and completes.
When i log into the cluster all the nodes are there but the master, the one where the cert signing is pending.
I reset the cluster and started the playbook again, this time keeping an eye for when the cert signing request gets done, and then I approved the request by hand, and that fixed the issue, and i could see all nodes on the cluster.
What could cause the cert signing to be stuck in pending, and i have to do it by hand??
Thank you for he awesome work so far, and any help will be greatly appreciated.
Cheers
The text was updated successfully, but these errors were encountered: