View source for Deploy a cluster Kubernetes with CoreOS

<span data-link_translate_en_title="Deploy a cluster Kubernetes with CoreOS"  data-link_translate_en_url="Deploy a cluster Kubernetes with CoreOS"></span>[[:en:Deploy a cluster Kubernetes with CoreOS]][[en:Deploy a cluster Kubernetes with CoreOS]]
<span data-link_translate_he_title="לפרוס את אשכול Kubernetes עם CoreOS"  data-link_translate_he_url="%D7%9C%D7%A4%D7%A8%D7%95%D7%A1+%D7%90%D7%AA+%D7%90%D7%A9%D7%9B%D7%95%D7%9C+Kubernetes+%D7%A2%D7%9D+CoreOS"></span>[[:he:לפרוס את אשכול Kubernetes עם CoreOS]][[he:לפרוס את אשכול Kubernetes עם CoreOS]]
<span data-link_translate_ru_title="Развертывание кластера Kubernetes с CoreOS"  data-link_translate_ru_url="%D0%A0%D0%B0%D0%B7%D0%B2%D0%B5%D1%80%D1%82%D1%8B%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5+%D0%BA%D0%BB%D0%B0%D1%81%D1%82%D0%B5%D1%80%D0%B0+Kubernetes+%D1%81+CoreOS"></span>[[:ru:Развертывание кластера Kubernetes с CoreOS]][[ru:Развертывание кластера Kubernetes с CoreOS]]
<span data-link_translate_ja_title="クラスター コア Os と Kubernetes を展開します。"  data-link_translate_ja_url="%E3%82%AF%E3%83%A9%E3%82%B9%E3%82%BF%E3%83%BC+%E3%82%B3%E3%82%A2+Os+%E3%81%A8+Kubernetes+%E3%82%92%E5%B1%95%E9%96%8B%E3%81%97%E3%81%BE%E3%81%99%E3%80%82"></span>[[:ja:クラスター コア Os と Kubernetes を展開します。]][[ja:クラスター コア Os と Kubernetes を展開します。]]
<span data-link_translate_ar_title="نشر مجموعة كوبيرنيتيس مع CoreOS"  data-link_translate_ar_url="%D9%86%D8%B4%D8%B1+%D9%85%D8%AC%D9%85%D9%88%D8%B9%D8%A9+%D9%83%D9%88%D8%A8%D9%8A%D8%B1%D9%86%D9%8A%D8%AA%D9%8A%D8%B3+%D9%85%D8%B9+CoreOS"></span>[[:ar:نشر مجموعة كوبيرنيتيس مع CoreOS]][[ar:نشر مجموعة كوبيرنيتيس مع CoreOS]]
<span data-link_translate_zh_title="部署群集与 CoreOS Kubernetes"  data-link_translate_zh_url="%E9%83%A8%E7%BD%B2%E7%BE%A4%E9%9B%86%E4%B8%8E+CoreOS+Kubernetes"></span>[[:zh:部署群集与 CoreOS Kubernetes]][[zh:部署群集与 CoreOS Kubernetes]]
<span data-link_translate_ro_title="Implementaţi un cluster Kubernetes cu CoreOS"  data-link_translate_ro_url="Implementa%C5%A3i+un+cluster+Kubernetes+cu+CoreOS"></span>[[:ro:Implementaţi un cluster Kubernetes cu CoreOS]][[ro:Implementaţi un cluster Kubernetes cu CoreOS]]
<span data-link_translate_pl_title="Wdróż klaster Kubernetes z CoreOS"  data-link_translate_pl_url="Wdr%C3%B3%C5%BC+klaster+Kubernetes+z+CoreOS"></span>[[:pl:Wdróż klaster Kubernetes z CoreOS]][[pl:Wdróż klaster Kubernetes z CoreOS]]
<span data-link_translate_de_title="Bereitstellen eines Clusters Kubernetes mit CoreOS"  data-link_translate_de_url="Bereitstellen+eines+Clusters+Kubernetes+mit+CoreOS"></span>[[:de:Bereitstellen eines Clusters Kubernetes mit CoreOS]][[de:Bereitstellen eines Clusters Kubernetes mit CoreOS]]
<span data-link_translate_nl_title="Implementeer een cluster Kubernetes met CoreOS"  data-link_translate_nl_url="Implementeer+een+cluster+Kubernetes+met+CoreOS"></span>[[:nl:Implementeer een cluster Kubernetes met CoreOS]][[nl:Implementeer een cluster Kubernetes met CoreOS]]
<span data-link_translate_it_title="Distribuire un cluster Kubernetes con CoreOS"  data-link_translate_it_url="Distribuire+un+cluster+Kubernetes+con+CoreOS"></span>[[:it:Distribuire un cluster Kubernetes con CoreOS]][[it:Distribuire un cluster Kubernetes con CoreOS]]
<span data-link_translate_pt_title="Implantar um cluster Kubernetes com CoreOS"  data-link_translate_pt_url="Implantar+um+cluster+Kubernetes+com+CoreOS"></span>[[:pt:Implantar um cluster Kubernetes com CoreOS]][[pt:Implantar um cluster Kubernetes com CoreOS]]
<span data-link_translate_es_title="Implementar un clÃºster Kubernetes con CoreOS"  data-link_translate_es_url="Implementar+un+cl%C3%BAster+Kubernetes+con+CoreOS"></span>[[:es:Implementar un clúster Kubernetes con CoreOS]][[es:Implementar un clúster Kubernetes con CoreOS]]
<span data-link_translate_fr_title="Deployer un cluster Kubernetes avec CoreOS"  data-link_translate_fr_url="Deployer_un_cluster_Kubernetes_avec_CoreOS"></span>[[:fr:Deployer un cluster Kubernetes avec CoreOS]][[fr:Deployer un cluster Kubernetes avec CoreOS]]
<br />

{{#seo:
|title=Deploy a cluster Kubernetes with CoreOS
|title_mode=append
|keywords=these,are,your,keywords
|description=Deploy a cluster Kubernetes with CoreOS
|image=Uploaded_file.png
|image_alt=Wiki Logo
}}

This article has been created by an automatic translation software. You can view the article source [[:fr:Deployer un cluster Kubernetes avec CoreOS|here]].<br /><span data-translate="fr"></span>

<!--T:1-->
This procedure describes how to deploy quickly and simply a cluster [http://kubernetes.io/ Kubernetes] multi-nodes with 3 instances CoreOS. [https://www.ikoula.com/en/public-cloud/oneclick/kubernetes Kubernetes] work in client mode - Server, client Kubernetes is named "Kubernetes minion  " and the server "Kubernetes master ". The Kubernetes Master instance is the instance that will orchestrate centrally instances Kubernetes Minion s. In our example, an instance CoreOS will play the role of Master Kubernetes  and the other two instances will play the role of node Kubernetes (minion ).


<!--T:2-->
Kubernetes is a system of open orchestration source created by Google for managing application container with Docker on a cluster of multiple hosts (3 VM CoreOS in our example ). It allows the deployment, maintenance, and scalability of applications. For more information you can go on [https://github.com/GoogleCloudPlatform/kubernetes/ github Kubernetes]


<!--T:3-->
We assume that your 3 CoreOS instances are already deployed, qu ''''they can communicate with each other ''' and that you are logged in ssh with the user core.


<!--T:4-->
If this is not already done, update your CoreOS instances so that they are at least in version CoreOS 653.0.0 and include DCE 2 (see our FAQ  [https://ikoula.wiki/help/Mettre_a_jour_CoreOS_manuellement Update CoreOS manually]). In our case all our bodies are in stable CoreOS 681.2.0.


<!--T:5-->
<syntaxhighlight lang="bash">
$ cat /etc/lsb-release
DISTRIB_ID=CoreOS
DISTRIB_RELEASE=681.2.0
DISTRIB_CODENAME="Red Dog"
DISTRIB_DESCRIPTION="CoreOS 681.2.0"
</syntaxhighlight>


<!--T:6-->
We must also ensure that all our CoreOS instances have an ID of different machine for proper operation context cluster. To simply delete the file /etc/machine-id and restart each of your instances CoreOS  either : 


<!--T:7-->
<syntaxhighlight lang="bash">
$ sudo rm -f /etc/machine-id && sudo reboot
</syntaxhighlight>


== '''Kubernetes Master instance configuration  :''' == <!--T:8-->


<!--T:9-->
Overwrite the file cloud - default config.yml to our Kubernetes Master configuration by performing the following commands ('''only on the instance which will act as the master and in the same order than below ''') :


<!--T:10-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ sudo wget -O /usr/share/oem/cloud-config.yml http://mirror02.ikoula.com/priv/coreos/kubernetes-master.yaml
--2015-06-22 15:55:48--  http://mirror02.ikoula.com/priv/coreos/kubernetes-master.yaml
Resolving mirror02.ikoula.com... 80.93.X.X, 2a00:c70:1:80:93:81:178:1
Connecting to mirror02.ikoula.com|80.93.X.X|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8913 (8.7K) [text/plain]
Saving to: '/usr/share/oem/cloud-config.yml'

<!--T:11-->
/usr/share/oem/cloud-config.yml               100%[===================================================================================================>]   8.70K  --.-KB/s   in 0s

<!--T:12-->
2015-06-22 15:55:48 (148 MB/s) - '/usr/share/oem/cloud-config.yml' saved [8913/8913]
</syntaxhighlight>


<!--T:13-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ export `cat /etc/environment`
</syntaxhighlight>


<!--T:14-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ sudo sed -i 's#PRIVATE_IP#'$COREOS_PRIVATE_IPV4'#g' /usr/share/oem/cloud-config.yml
</syntaxhighlight>


<!--T:15-->
On redémarre notre instance afin que sa configuration either effective :


<!--T:16-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ sudo reboot
</syntaxhighlight>


<!--T:17-->
We check that our body is properly initialized :


<!--T:18-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ sudo fleetctl list-machines
MACHINE         IP              METADATA
aee19a88...     10.1.1.138      role=master
</syntaxhighlight>


<!--T:19-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ sudo etcdctl ls --recursive
/coreos.com
/coreos.com/updateengine
/coreos.com/updateengine/rebootlock
/coreos.com/updateengine/rebootlock/semaphore
/coreos.com/network
/coreos.com/network/config
/coreos.com/network/subnets
/coreos.com/network/subnets/10.244.69.0-24
/registry
/registry/ranges
/registry/ranges/serviceips
/registry/ranges/servicenodeports
/registry/namespaces
/registry/namespaces/default
/registry/services
/registry/services/endpoints
/registry/services/endpoints/default
/registry/services/endpoints/default/kubernetes
/registry/services/endpoints/default/kubernetes-ro
/registry/services/specs
/registry/services/specs/default
/registry/services/specs/default/kubernetes
/registry/services/specs/default/kubernetes-ro
/registry/serviceaccounts
/registry/serviceaccounts/default
/registry/serviceaccounts/default/default
</syntaxhighlight>


<!--T:20-->
You can also see services /listen ports (There are server components /Master Kubernetes ):


<!--T:21-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ sudo netstat -taupen | grep LISTEN
tcp        0      0 10.1.1.138:7001         0.0.0.0:*               LISTEN      232        16319      634/etcd2
tcp        0      0 10.1.1.138:7080         0.0.0.0:*               LISTEN      0          19392      1047/kube-apiserver
tcp        0      0 0.0.0.0:5000            0.0.0.0:*               LISTEN      0          19142      973/python
tcp        0      0 127.0.0.1:10251         0.0.0.0:*               LISTEN      0          20047      1075/kube-scheduler
tcp        0      0 10.1.1.138:6443         0.0.0.0:*               LISTEN      0          19406      1047/kube-apiserver
tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      245        14794      502/systemd-resolve
tcp        0      0 127.0.0.1:10252         0.0.0.0:*               LISTEN      0          19653      1058/kube-controlle
tcp        0      0 10.1.1.138:2380         0.0.0.0:*               LISTEN      232        16313      634/etcd2
tcp6       0      0 :::8080                 :::*                    LISTEN      0          19390      1047/kube-apiserver
tcp6       0      0 :::22                   :::*                    LISTEN      0          13647      1/systemd
tcp6       0      0 :::4001                 :::*                    LISTEN      232        16321      634/etcd2
tcp6       0      0 :::2379                 :::*                    LISTEN      232        16320      634/etcd2
tcp6       0      0 :::5355                 :::*                    LISTEN      245        14796      502/systemd-resolve
</syntaxhighlight>


== '''Configuration of instances Kubernetes Minion s :''' == <!--T:22-->


<!--T:23-->
Overwrite the file cloud - default config.yml to our Kubernetes Minion  configuration by performing the following commands on all of your instance that will play the role of Kubernetes Minion  ('''only on instances that will play the role node /minion  et dans le même ordre d'exécution que celui ci-dessous''') :


<!--T:24-->
<syntaxhighlight lang="bash">
core@Kube-MINION1 ~ $ sudo wget -O /usr/share/oem/cloud-config.yml http://mirror02.ikoula.com/priv/coreos/kubernetes-minion.yaml
--2015-06-22 16:39:26--  http://mirror02.ikoula.com/priv/coreos/kubernetes-minion.yaml
Resolving mirror02.ikoula.com... 80.93.X.X, 2a00:c70:1:80:93:81:178:1
Connecting to mirror02.ikoula.com|80.93.X.X|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5210 (5.1K) [text/plain]
Saving to: '/usr/share/oem/cloud-config.yml'

<!--T:25-->
/usr/share/oem/cloud-config.yml               100%[===================================================================================================>]   5.09K  --.-KB/s   in 0s

<!--T:26-->
2015-06-22 16:39:26 (428 MB/s) - '/usr/share/oem/cloud-config.yml' saved [5210/5210]
</syntaxhighlight>


<!--T:27-->
<syntaxhighlight lang="bash">
core@Kube-MINION1 ~ $ export `cat /etc/environment`
</syntaxhighlight>


<!--T:28-->
Caution it is necessary to adapt the private ip address of your kubernetes master instance in the command below ('''replace 10.1.1.138 by the ip private of your kubernetes master instance ''') the command below :


<!--T:29-->
<syntaxhighlight lang="bash">
core@Kube-MINION1 ~ $ sudo sed -i 's#MASTER_PRIVATE_IP#10.1.1.138#g' /usr/share/oem/cloud-config.yml
</syntaxhighlight>


<!--T:30-->
Finally once you have perform these commands identically on each of your instances /nodes kubernetes minion , redémarrez celles-ci afin que leur configuration soient effectives et quelles joignent le cluster.


<!--T:31-->
<syntaxhighlight lang="bash">
core@Kube-MINION1 ~ $ sudo reboot
</syntaxhighlight>


<!--T:32-->
We verify that our 2 instances kubernetes minion  ont bien rejoint notre cluster (the command below peut être exécuté sur n'importe laquelle de vos instances membre de votre cluster) :


<!--T:33-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ sudo fleetctl list-machines
MACHINE         IP              METADATA
5097f972...     10.1.1.215      role=node
aee19a88...     10.1.1.138      role=master
fe86214c...     10.1.1.83       role=node
</syntaxhighlight>


<!--T:34-->
<syntaxhighlight lang="bash">
core@Kube-MINION1 ~ $ sudo etcdctl ls --recursive
/coreos.com
/coreos.com/updateengine
/coreos.com/updateengine/rebootlock
/coreos.com/updateengine/rebootlock/semaphore
/coreos.com/network
/coreos.com/network/config
/coreos.com/network/subnets
/coreos.com/network/subnets/10.244.69.0-24
/coreos.com/network/subnets/10.244.38.0-24
/coreos.com/network/subnets/10.244.23.0-24
/registry
/registry/ranges
/registry/ranges/serviceips
/registry/ranges/servicenodeports
/registry/namespaces
/registry/namespaces/default
/registry/services
/registry/services/specs
/registry/services/specs/default
/registry/services/specs/default/kubernetes
/registry/services/specs/default/kubernetes-ro
/registry/services/endpoints
/registry/services/endpoints/default
/registry/services/endpoints/default/kubernetes
/registry/services/endpoints/default/kubernetes-ro
/registry/serviceaccounts
/registry/serviceaccounts/default
/registry/serviceaccounts/default/default
/registry/events
/registry/events/default
/registry/events/default/10.1.1.215.13ea16c9c70924f4
/registry/events/default/10.1.1.83.13ea16f74bd4de1c
/registry/events/default/10.1.1.83.13ea16f77a4e7ab2
/registry/events/default/10.1.1.215.13ea16c991a4ee57
/registry/minions
/registry/minions/10.1.1.215
/registry/minions/10.1.1.83
</syntaxhighlight>


<!--T:35-->
<syntaxhighlight lang="bash">
core@Kube-MINION2 ~ $ sudo etcdctl ls --recursive
/coreos.com
/coreos.com/updateengine
/coreos.com/updateengine/rebootlock
/coreos.com/updateengine/rebootlock/semaphore
/coreos.com/network
/coreos.com/network/config
/coreos.com/network/subnets
/coreos.com/network/subnets/10.244.69.0-24
/coreos.com/network/subnets/10.244.38.0-24
/coreos.com/network/subnets/10.244.23.0-24
/registry
/registry/ranges
/registry/ranges/serviceips
/registry/ranges/servicenodeports
/registry/namespaces
/registry/namespaces/default
/registry/services
/registry/services/specs
/registry/services/specs/default
/registry/services/specs/default/kubernetes
/registry/services/specs/default/kubernetes-ro
/registry/services/endpoints
/registry/services/endpoints/default
/registry/services/endpoints/default/kubernetes
/registry/services/endpoints/default/kubernetes-ro
/registry/serviceaccounts
/registry/serviceaccounts/default
/registry/serviceaccounts/default/default
/registry/events
/registry/events/default
/registry/events/default/10.1.1.83.13ea16f77a4e7ab2
/registry/events/default/10.1.1.215.13ea16c991a4ee57
/registry/events/default/10.1.1.215.13ea16c9c70924f4
/registry/events/default/10.1.1.83.13ea16f74bd4de1c
/registry/minions
/registry/minions/10.1.1.215
/registry/minions/10.1.1.83
</syntaxhighlight>


<!--T:36-->
On our instances Kubernetes Minion  here services /listen ports (including the Kubelet service by which the exchange of information is done with the master Kubernetes  ) :


<!--T:37-->
<syntaxhighlight lang="bash">
core@Kube-MINION1 ~ $ sudo netstat -taupen | grep LISTEN
tcp        0      0 127.0.0.1:10249         0.0.0.0:*               LISTEN      0          18280      849/kube-proxy
tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      245        14843      500/systemd-resolve
tcp6       0      0 :::49005                :::*                    LISTEN      0          18284      849/kube-proxy
tcp6       0      0 :::10255                :::*                    LISTEN      0          19213      1025/kubelet
tcp6       0      0 :::47666                :::*                    LISTEN      0          18309      849/kube-proxy
tcp6       0      0 :::22                   :::*                    LISTEN      0          13669      1/systemd
tcp6       0      0 :::4001                 :::*                    LISTEN      232        16106      617/etcd2
tcp6       0      0 :::4194                 :::*                    LISTEN      0          19096      1025/kubelet
tcp6       0      0 :::10248                :::*                    LISTEN      0          19210      1025/kubelet
tcp6       0      0 :::10250                :::*                    LISTEN      0          19305      1025/kubelet
tcp6       0      0 :::2379                 :::*                    LISTEN      232        16105      617/etcd2
tcp6       0      0 :::5355                 :::*                    LISTEN      245        14845      500/systemd-resolve
</syntaxhighlight>


== '''Verification of communication with the Master Kubernetes API  :''' == <!--T:38-->


<!--T:39-->
'''The UI Kubernetes :'''

<!--T:40-->
To access the dashboard Kubernetes, you need to allow connections to port 8080 (Kubernetes master  API server) and carried out a port if required forwarding (forward area ) port 8080 de votre instance Kubernetes master . Ensuite, il vous suffit d'accéder à l'url http://''adresse_ip_publique_instance_kubernetes_master'':8080/static/app/#/dashboard/ in your browser :


<!--T:41-->
[[File:Kubernetes-UI.png]]


<!--T:42-->
Since this dashboard, you are among other possible to display information on your nodes (Kubernetes Minion ). For this, you can click on "Views  " :


<!--T:43-->
[[File:Kubernetes-UI-2.png]]


<!--T:44-->
Click on "Nodes " :


<!--T:45-->
[[File:Kubernetes-UI-3.png]]


<!--T:46-->
La liste de vos nodes Kubernetes minion   apparait :


<!--T:47-->
[[File:Kubernetes-UI-4.png]]


<!--T:48-->
Click on l'un d'eux pour afficher les informations relatives à ce node (version of Docker, system, KubeProxy, and Kubelet, etc. |) :


<!--T:49-->
[[File:Kubernetes-UI-5.png]]


<!--T:50-->
'''Kubernetes CLI :'''


<!--T:51-->
You can also use the tools [https://cloud.google.com/container-engine/docs/kubectl/ Kubectl] deThen votre instance Kubernetes master . Pour se faire, vous devez installer cette utilitaire comme suit :


<!--T:52-->
Une fois connecté en ssh sur votre instance Kubernetes master  saisissez les commandes suivantes :


<!--T:53-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ sudo wget -O /opt/bin/kubectl https://storage.googleapis.com/kubernetes-release/release/v0.17.0/bin/linux/amd64/kubectl
--2015-06-23 11:39:09--  https://storage.googleapis.com/kubernetes-release/release/v0.17.0/bin/linux/amd64/kubectl
Resolving storage.googleapis.com... 64.233.166.128, 2a00:1450:400c:c09::80
Connecting to storage.googleapis.com|64.233.166.128|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 20077224 (19M) [application/octet-stream]
Saving to: '/opt/bin/kubectl'

<!--T:54-->
/opt/bin/kubectl                              100%[===================================================================================================>]  19.15M  1.18MB/s   in 16s

<!--T:55-->
2015-06-23 11:39:26 (1.18 MB/s) - '/opt/bin/kubectl' saved [20077224/20077224]
</syntaxhighlight>


<!--T:56-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ sudo chmod 755 /opt/bin/kubectl
</syntaxhighlight>


<!--T:57-->
Test of good communication with your API Kubernetes :


<!--T:58-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ kubectl get node
NAME         LABELS                              STATUS
10.1.1.215   kubernetes.io/hostname=10.1.1.215   Ready
10.1.1.83    kubernetes.io/hostname=10.1.1.83    Ready
</syntaxhighlight>


<!--T:59-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ kubectl cluster-info
Kubernetes master is running at http://localhost:8080
</syntaxhighlight>


<!--T:60-->
We can thus deploy a first container Nginx in our cluster :


<!--T:61-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ kubectl run-container nginx --image=nginx
CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR              REPLICAS
nginx        nginx          nginx      run-container=nginx   1
</syntaxhighlight>



<!--T:62-->
Then we can or even on which our hosts this container is deployed, the name of the pod and the ip which was was affected :


<!--T:63-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ kubectl get pods
POD           IP            CONTAINER(S)   IMAGE(S)   HOST                    LABELS                STATUS    CREATED     MESSAGE
nginx-zia71   10.244.38.2                             10.1.1.215/10.1.1.215   run-container=nginx   Running   3 minutes
                            nginx          nginx                                                    Running   1 minutes
</syntaxhighlight>


<!--T:64-->
We find this same information via the Kubernete UI dashboard by going in "Views  " Then "Pods " :


<!--T:65-->
[[File:Kubernetes-UI-6.png]]


<!--T:66-->
We can see the ip of the host on which this container deployed, with the name of the Pod and its ip address : 


<!--T:67-->
[[File:Kubernetes-UI-7.png]]


<!--T:68-->
Clicking on it gets more details on our Pod :


<!--T:69-->
[[File:Kubernetes-UI-8.png]]


<!--T:70-->
We can stop our container simply :


<!--T:71-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ kubectl stop rc nginx
replicationcontrollers/nginx
</syntaxhighlight>


<!--T:72-->
We can also deploy our container with 2 replicas :


<!--T:73-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ kubectl run-container nginx --image=nginx --replicas=2
CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR              REPLICAS
nginx        nginx          nginx      run-container=nginx   2
</syntaxhighlight>


<!--T:74-->
<syntaxhighlight lang="bash">
core@Kube-MASTER ~ $ kubectl get pods
POD           IP            CONTAINER(S)   IMAGE(S)   HOST                    LABELS                STATUS    CREATED          MESSAGE
nginx-7gen5   10.244.38.3                             10.1.1.215/10.1.1.215   run-container=nginx   Running   About a minute
                            nginx          nginx                                                    Running   39 seconds
nginx-w4xue   10.244.23.3                             10.1.1.83/10.1.1.83     run-container=nginx   Running   About a minute
                            nginx          nginx                                                    Running   About a minute
</syntaxhighlight>


<!--T:75-->
[[File:Kubernetes-UI-9.png]]



<!--T:76-->
For more information, on the architecture, components and operation of a cluster Kubernetes we invite you to read the official documentation [https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/design/architecture.md "Kubernetes architecture"] :


<!--T:77-->
[[Category:cloudstack]]
[[Category:public_cloud]]
[[Category:private_cloud]]
<br />
<comments />