search

Azure / ACS

Azure Container Service - Bug Tracker + Announcements
65 stars 27 forks source link

Kubernetes deployed using ACS-Engine and Cluster Definition but kubectlcluster is not running inside the master. #48

Open rakeshkulkarni6 opened 7 years ago

rakeshkulkarni6 commented 7 years ago

Is this a request for help?:

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm) Kubernetes

What happened: I have Deployed kubernetes container service using ACS-Engine After Deploying i am facing following issues.

  1. After Deployment not able to connect to cluster using ssh key but able to connect to cluster using password.
  2. After connecting to cluster able to login machine master 01 but docker service is not running and kubectl is not installed in master server.
  3. I have tried to connect to cluster using kuectl cli from remote machine but not able to connect to cluster.Can any one guide me how to connect to cluster using cli

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know:

JackQuincy commented 7 years ago

Can you move this incident to acs-engine? That repo gets a lot more activity than this one and this isn't our service causing the issues. Also my first step would be to verify your service principal is properly setup. Look at the trouble shooting steps in this readme. https://github.com/Azure/acs-engine/blob/master/docs/kubernetes.md

rakeshkulkarni6 commented 7 years ago

thanks for reply. I have verified Service principal its fine. Kubectl cluster-info is listing cluster running but getting below error when i run kubectl get nodes

Unable to connect to the server: dial tcp IP:8080: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.