Changes between Version 7 and Version 8 of minikubedeployment2023

Timestamp:

Dec 4, 2023, 5:08:08 AM (12 months ago)

Author:

deepthi

Comment:

--

minikubedeployment2023

@@ -1 @@
-You may continue to install Kubernetes on the vm you already installed docker. If you are installing this on a different machine make sure docker is already installed.
-
+'''You may continue to install Kubernetes on the vm you already installed docker. If you are installing this on a different machine make sure docker is already installed.
+'''
 ==== Part 1 ====
 
-Installing kubeadm, kubelet, and kubectl:
+'''Installing kubeadm, kubelet, and kubectl:'''
 
 1. Update the apt package index:
@@ -39 +39 @@
 `kubeadm version`
  
-Disable Swap Space
+'''Disable Swap Space'''
 
 8. Disable all swaps from /proc/swaps.
@@ -51 +51 @@
 `free -h`
  
-Install Container runtime
+'''Install Container runtime'''
 
 10. Configure persistent loading of modules 
@@ -69 +69 @@
 
 12. Ensure sysctl params are set
-{{{
-
+
+{{{
 sudo tee /etc/sysctl.d/kubernetes.conf<<EOF
-
 net.bridge.bridge-nf-call-ip6tables = 1
-
 net.bridge.bridge-nf-call-iptables = 1
-
 net.ipv4.ip_forward = 1
-
 EOF
 }}}
@@ -96 +92 @@
 
 16. Configuring a cgroup driver
+
 Both the container runtime and the kubelet have a property called "cgroup driver", which is essential for the management of cgroups on Linux machines.
 
@@ -108 +105 @@
 `systemctl status containerd`
 
-Initialize control plane
+'''Initialize control plane'''
+
 18. Make sure that the br_netfilter module is loaded:
 
@@ -114 +112 @@
 
 Output should similar to:
+
 {{{
 br_netfilter           22256  0 
@@ -133 +132 @@
 You will see Your Kubernetes control-plane has initialized successfully!
 
+You need to save the kubeadm join token string on a text document for future use.
+
 22. To start the cluster, you need to run the following as a regular user (For this scenario we will only use a single host):
  
@@ -157 +158 @@
 
 `kubectl get nodes -o wide`
+
 27. On a master/ control node to query the nodes you can use:
 
 `kubectl get nodes`
 
-Scheduling Pods on Kubernetes Master Node
-28. By default, Kubernetes Cluster will not schedule pods on the master/control-plane node for security reasons. It is recommended you keep it this way, but for test environments you need to schedule Pods on 
-control-plane node to maximize resource usage.
-
-`kubectl taint nodes --all  node-role.kubernetes.io/control-plane-`
+28. Connecting Worker nodes:
+
+28.1. Install docker on both worker nodes as per the guidelines here.(LINK)
+
+28.2. Install Kubernetes on each worker nodes. Follow steps 1 to 20.
+
+28.3 Use previously saved kubeadm join token string to connect the workers. Run it with sudo.
+
+If you forgot the token, run the following on your master to create a new token:
+
+`kubeadm token create --print-join-command`
+
+But remember, this will create a new token.
+
+28.4 After all workers are connected, check status of the cluster: Here after all commands should be run on the master.
+
+kubectl get nodes -o wide
 
 ==== Part 2 ====
 Create a file simple-pod.yaml
+
 {{{
 apiVersion: v1
@@ -186 +201 @@
 `kubectl apply -f simple-pod.yaml`
 
+Check pod
+
+`kubectl get pods`
+
+Kill the Pod.
+
+`kubectl delete pod nginx`
+
 Pods are generally not created directly and are created using workload resources. See Working with Pods 
-Links to an external site. for more information on how Pods are used with workload resources
+[https://kubernetes.io/docs/concepts/workloads/pods/#working-with-pods Links to an external site]. for more information on how Pods are used with workload resources
 
 ==== Part 3 ====
 
-Deploying a Simple Web Application on Kubernetes
+'''Deploying a Simple Web Application on Kubernetes'''
+
 1. Create a Deployment Manifest:
+
 A Deployment ensures that a specified number of pod replicas are running at any given time. Let's create a simple Deployment for a web application using the nginx image.
 Save the following YAML to a file named webapp-deployment.yaml:
@@ -221 +246 @@
 
 2. Create a Service Manifest:
+
 A Service is an abstraction that defines a logical set of Pods and enables external traffic exposure, load balancing, and service discovery. For our web application, we'll use a NodePort service.
+
 Save the following YAML to a file named webapp-service.yaml:
 
@@ -266 +293 @@
 
 You should see the default nginx welcome page, indicating that your web application is running.
+
+Delete all the deployments, run below command:
+
+`kubectl delete deployment <deployment name>`
+
+Delete all the Services, run below command:
+
+`kubectl delete service <service name>`
  
 Part 4
-Deploying WordPress and MySQL on Kubernetes
+
+'''Deploying WordPress and MySQL on Kubernetes'''
 
 Installing dependancies:
+
 Download rancher.io/local-path storage class:
 
@@ -433 +470 @@
  
 Part 5
+
 Convert your Docker deployment into a Kubernetes deployment, you may compose your own service, deployment manifests as needed. Use the docker images you used previously when creating the pods/deployments. 
  
-Additional ref: https://kubebyexample.com/
+Additional ref:[ https://kubebyexample.com/]