How to install Kubernetes - Revision history

Admin: /* Conclusion */

2021-04-29T01:58:46Z

Conclusion

2021-04-29T01:49:55Z

Service yaml

2021-04-29T01:47:17Z

Scale

2021-04-29T00:38:35Z

On the master node

2021-04-29T00:34:36Z

Prerequisites

2021-04-29T00:29:10Z

2020-05-02T18:08:08Z

Access Dashboard

2020-05-02T17:30:37Z

Access Dashboard

2020-05-02T17:22:30Z

Dashboard Configuration

2020-05-02T17:13:37Z

Dashboard Configuration

← Older revision		Revision as of 01:58, 29 April 2021
Line 730:		Line 730:

	=Conclusion=		=Conclusion=
−	In this tutorial, we setup a 3 nodes cluster with one master and 2 nodes. We also setup the dashboard which is very helpful to use when you are new on working with K8s. The tutorial was written to help those that wants to start to learn the basic of K8 with simple examples.	+	In this tutorial, we setup a 3 nodes cluster with one master and 2 nodes. We also setup the dashboard which is very helpful to use when you are new on working with K8s. The tutorial was written to help those that wants to start to learn the basic of K8s with simple examples.

@@ Line 549: / Line 549: @@
 ==Service yaml==
-The service below opens a specific port on all the Nodes(k8s2002 and k8s2003) and any traffic that is sent to this port is forwarded to the service. In this case, the service can me accessible from any node in the cluster bu using any give node IP address follow by the open port.
+The service below opens a specific port on all the Nodes(k8s2002 and k8s2003) and any traffic that is sent to this port is forwarded to the service. In this case, the service can me accessible from any node in the cluster by using any give node IP address follow by the open port.
   ---

@@ Line 458: / Line 458: @@
 Depending on your needs, you can decide to scale your deployment. You have 2 options to scale, scale up which will add mode pod(s) to your deployment and scale down which will remove pod(s) from your deployment.
-We have seen that when the replicas = 5 K8s and we have 2 node in our cluster, K8s distribute the load equally between the nodes ( 3 for k8s2002 and 2 for k8s2003) if the replicas was equal to let see 4, then k82002 will get 2 and k8s2003 as well.
+We have seen that when the replicas = 5  and we have 2 nodes in our cluster, K8s distribute the load equally between the nodes ( 3 for k8s2002 and 2 for k8s2003) if the replicas was equal to let see 4, then k82002 will get 2 and k8s2003 as well.
 In example 1, we have 3 pods running on k8s2002 and 2 on k8s2003.
@@ Line 471: / Line 471: @@
 if we decide to scale up by adding 1 more pod, this pod will automatically be added to k8s2003.
-We do ahve 3 options for scaling up
+We do have 3 options for scaling up
 * Use the dashboard: the easy way
 * Edit the deployment yaml file
@@ Line 499: / Line 499: @@
   hello-world-78f6dc68cf-ttkwh    1/1     Running   0          110m   192.168.3.6    k8s2002   <none>
   hello-world-78f6dc68cf-xv75k    1/1     Running   0          38m    192.168.2.13   k8s2003   <none>
 =Understand K8s yaml file=
 In this section we are going to break down the most important parts of the deployment and service yaml files to create a basic app

@@ Line 85: / Line 85: @@
   kubectl get nodes
   ppaul@k8s2001:~$ kubectl get node
   NAME      STATUS   ROLES    AGE   VERSION
   k8s1001   NotReady master   36h   v1.18.2
@@ Line 98: / Line 92: @@
 We can see that the status of the master is NotReady. The reason being that the cluster doesn't have a Container Networking Interface or CNI.
-Issue the 2 commands below to deploy a Calico CNI and coreDNS.
+ kubectl apply -f https://docs.projectcalico.org/v3.9/manifests/calico.yaml
-Output
+Now issue again the command kubectl get nodes
-on version 1.18
+  ppaul@k8s2001:~$ kubectl get nodes
   NAME      STATUS   ROLES    AGE   VERSION
   k8s1001   Ready    master   36h   v1.18.2
@@ Line 145: / Line 107: @@
   kubectl get pods --all-namespaces
   ppaul@k8s2001:~$ kubectl get pods --all-namespaces
   NAMESPACE              NAME                                         READY   STATUS    RESTARTS   AGE
   kube-system            calico-kube-controllers-6fcbbfb6fb-68nv4     1/1     Running   0          36h

@@ Line 4: / Line 4: @@
 =Prerequisites=
-To complete this tutorial, we will need 3 nodes running Debian Stretch. This tutorial will work too on nodes running Ubuntu Xenial.
+To complete this tutorial, we will need 3 nodes running Debian Stretch/Buster. This tutorial will work too on nodes running Ubuntu Xenial.
 ==Node informations==
@@ Line 23: / Line 23: @@
   ff02::2 ip6-allrouters
-make also sure if you are using swap to disable swap
+make also sure if you are using swap to disable swap on all nodes
 /etc/fstab

@@ Line 1: / Line 1: @@
-<span style="color: red">ATTENTION!!! THIS TUTORIAL WAS FOR VERSION 1.12. I UPDATE THE TUTORIAL SIDE BY SIDE WITH THE INSTALLLATION AND CONFIGURATION OF VERSION 1.18 and Docker version 19.03.8</span>
+<span style="color: red">ATTENTION!!! CONFIGURATION OF VERSION 1.18 and Docker version 19.03.8</span>
 In this tutorial, we will be installing Kubernetes (k8s) cluster. The cluster will have 1 master and 2 nodes.
@@ Line 22: / Line 22: @@
   ff02::1 ip6-allnodes
   ff02::2 ip6-allrouters
 =K8s Installation=

@@ Line 280: / Line 280: @@
 Copy and paste the token you obtained for the ppadmin service account
- Now that we have the master ready, it is time to join the first node.
+Now that we have the master ready, it is time to join the first node. Everything from here below is the same as for version 1.12 and version 1.18
 =Join node to cluster=

@@ Line 250: / Line 250: @@
 ==Access Dashboard==
 To be able to access the dashboard, we need to enable proxy on the master bu issuing the command below
@@ Line 264: / Line 265: @@
 [[file:k8sdashboard.png|800px]]
-Now that we have the master ready, it is time to join the first node.
+On version 1.18
 =Join node to cluster=

@@ Line 246: / Line 246: @@
   serviceaccount/ppadmin created
   clusterrolebinding.rbac.authorization.k8s.io/ppadmin created
 ==Access Dashboard==

@@ Line 192: / Line 192: @@
 ==Dashboard Configuration==
 Let us configure our Dashboard so we can have full admin permission. First we need to create a yaml file and use the yaml file to setup admin permission on the dashboard. Create a file named dashboard.yaml. and paste the content below into the file, save, close the file and make it executable.
@@ Line 214: / Line 215: @@
   ppaul@k8s2001:~$ kubectl create -f dashboard.yaml
   clusterrolebinding.rbac.authorization.k8s.io/kubernetes-dashboard created
 ==Access Dashboard==