2016-09-16 116 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找到。