2016-09-16 92 views
3

運行的創建一個2節點Kubernetes集羣:SSH成Kubernetes羣集上亞馬遜

KUBERNETES_PROVIDER=aws NUM_NODES=2 kube-up.sh 

這顯示了輸出爲:

Found 2 node(s). 
NAME           STATUS AGE 
ip-172-20-0-226.us-west-2.compute.internal Ready  57s 
ip-172-20-0-227.us-west-2.compute.internal Ready  55s 
Validate output: 
NAME     STATUS MESSAGE    ERROR 
controller-manager Healthy ok     
scheduler   Healthy ok     
etcd-0    Healthy {"health": "true"} 
etcd-1    Healthy {"health": "true"} 
Cluster validation succeeded 
Done, listing cluster services: 

Kubernetes master is running at https://52.33.9.1 
Elasticsearch is running at https://52.33.9.1/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging 
Heapster is running at https://52.33.9.1/api/v1/proxy/namespaces/kube-system/services/heapster 
Kibana is running at https://52.33.9.1/api/v1/proxy/namespaces/kube-system/services/kibana-logging 
KubeDNS is running at https://52.33.9.1/api/v1/proxy/namespaces/kube-system/services/kube-dns 
kubernetes-dashboard is running at https://52.33.9.1/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard 
Grafana is running at https://52.33.9.1/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana 
InfluxDB is running at https://52.33.9.1/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb 

我可以看到在EC2控制檯實例。我如何進入主節點?

回答

0

「創建一個名爲kubernetes的AWS SSH密鑰。這裏的指紋是OpenSSH密鑰指紋,因此多個用戶可以使用不同的密鑰運行腳本,並且密鑰不會相互碰撞(幾乎可以肯定)。現有的密鑰,如果一個在AWS_SSH_KEY發現,否則會造成一個有(隨着Ubuntu默認的圖像,如果你有SSH方式:用戶是Ubuntu和用戶可以須藤」

https://github.com/kubernetes/kubernetes/blob/master/docs/design/aws_under_the_hood.md

你應在ssh config本地查看ssh密鑰指紋或設置ENV並重新創建。

5

這裏是爲我工作的準確命令:

ssh -i ~/.ssh/kube_aws_rsa [email protected]<masterip> 

kube_aws_rsa是生成的默認密鑰,AWS_SSH_KEY環境變量,否則控制。對於AWS,它在文件cluster/aws/config-default.sh中指定。

有關羣集的更多詳細信息可以使用kubectl.sh config view找到。