ravening commented on issue #4146: URL: https://github.com/apache/cloudstack/issues/4146#issuecomment-712675075
> @ravening MS will need SSH access on master node VMs while starting cluster and scaling it. When upgrading cluster it will need SSH access on all VMs. This must be the problem. Deployment would have failed after the time set in `cloud.kubernetes.cluster.start.timeout` global setting (Default 3600secs or 1hr) > It needs to connect to the k8s deployment using kubectl on master vm > > Yes, ideally the same version which you have used for k8s. I've not played with different version myself @shwstppr usually in our production environments, mgt server doesnt have ssh access to any of the VM's. So how do I fix the issue in that case? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
