docs:virtualizacion:docker:kops_cluster_mamagement

Diferencias

Muestra las diferencias entre dos versiones de la página.

Enlace a la vista de comparación

Ambos lados, revisión anterior Revisión previa
Próxima revisión		 Revisión previa
docs:virtualizacion:docker:kops_cluster_mamagement [2018/08/25 23:04] – rodolfodocs:virtualizacion:docker:kops_cluster_mamagement [2020/04/08 21:59] (actual) – borrado rodolfo
Línea 1: Línea 1:
-====== kops cluster management ====== 
- 
-===== Create cluster ===== 
- 
-  export NAME=myfirstcluster.k8s.local 
-  export KOPS_STATE_STORE=s3://kubernetesaws-example-com-state-store 
- 
-  $ ssh-keygen -t rsa -f /home/vagrant/.ssh/id_rsa -q -P "" 
- 
-Create cluster config (S3 store) 
- 
-  $ kops create cluster --zones us-west-2a ${NAME} 
- 
-  $ kops create secret --name myfirstcluster.k8s.local sshpublickey admin -i ~/.ssh/id_rsa.pub 
- 
-Build: 
- 
-  $ kops update cluster ${NAME} --yes 
-   
-  Cluster is starting.  It should be ready in a few minutes. 
-   
-  Suggestions: 
-   * validate cluster: kops validate cluster 
-   * list nodes: kubectl get nodes --show-labels 
-   * ssh to the master: ssh -i ~/.ssh/id_rsa admin@api.myfirstcluster.k8s.local 
-   * the admin user is specific to Debian. If not using Debian please use the appropriate user based on your OS. 
-   * read about installing addons at: https://github.com/kubernetes/kops/blob/master/docs/addons.md. 
- 
- 
-  $ kops validate cluster 
-  Using cluster from kubectl context: myfirstcluster.k8s.local 
-   
-  Validating cluster myfirstcluster.k8s.local 
-   
-  INSTANCE GROUPS 
-  NAME ROLE MACHINETYPE MIN MAX SUBNETS 
-  master-us-west-2a Master m3.medium 1 1 us-west-2a 
-  nodes Node t2.medium 2 2 us-west-2a 
-   
-  NODE STATUS 
-  NAME ROLE READY 
-  ip-172-20-32-120.us-west-2.compute.internal master True 
-  ip-172-20-51-89.us-west-2.compute.internal node True 
-  ip-172-20-58-56.us-west-2.compute.internal node True 
-   
-  Your cluster myfirstcluster.k8s.local is ready 
- 
-  $ kubectl get nodes 
-  NAME                                          STATUS    ROLES     AGE       VERSION 
-  ip-172-20-32-120.us-west-2.compute.internal   Ready     master    23m       v1.10.3 
-  ip-172-20-51-89.us-west-2.compute.internal    Ready     node      22m       v1.10.3 
-  ip-172-20-58-56.us-west-2.compute.internal    Ready     node      21m       v1.10.3 
- 
-  $ kubectl cluster-info 
-  Kubernetes master is running at https://api-myfirstcluster-k8s-lo-hqulii-1192082441.us-west-2.elb.amazonaws.com 
-  KubeDNS is running at https://api-myfirstcluster-k8s-lo-hqulii-1192082441.us-west-2.elb.amazonaws.com/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy 
-   
-  To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. 
- 
- 
-===== Delete cluster ===== 
- 
-Preview: 
- 
-  $ kops delete cluster --name ${NAME} 
- 
-Apply changes: 
- 
-  $ kops delete cluster --name ${NAME} --yes 
- 
-===== Referencias ===== 
- 
-  * [[https://medium.com/containermind/how-to-create-a-kubernetes-cluster-on-aws-in-few-minutes-89dda10354f4|How to Create a Kubernetes Cluster on AWS in Few Minutes]] 
-  * [[https://github.com/kubernetes/kops/blob/master/docs/aws.md#create-cluster-configuration|Kubernetes AWS Getting Started]] 
- 
  
  • docs/virtualizacion/docker/kops_cluster_mamagement.1535238254.txt.gz
  • Última modificación: 2018/08/25 23:04
  • por rodolfo