From 13697e14c90acded2175414f2a969f46c913a229 Mon Sep 17 00:00:00 2001 From: sourav kumar Date: Sun, 19 Jun 2022 16:01:40 +0530 Subject: [PATCH 1/4] added correct the file location --- Days/day53.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Days/day53.md b/Days/day53.md index 19cc98f..529cc70 100644 --- a/Days/day53.md +++ b/Days/day53.md @@ -63,7 +63,7 @@ Another thing to mention is that if you did need to get access to any cluster be ### Create a new cluster -Over the past two sessions we have created a minikube cluster locally and we have used Vagrant with VirtualBox to create a 3 node Kubernetes cluster, with Rancher we can also create clusters. In the [Rancher Folder](Days/Kubernetes/Rancher) you will find additional vagrant files that will build out the same 3 nodes but without the steps for creating our Kubernetes cluster (we want Rancher to do this for us) +Over the past two sessions we have created a minikube cluster locally and we have used Vagrant with VirtualBox to create a 3 node Kubernetes cluster, with Rancher we can also create clusters. In the [Rancher Folder](Kubernetes/Rancher) you will find additional vagrant files that will build out the same 3 nodes but without the steps for creating our Kubernetes cluster (we want Rancher to do this for us) We do however want docker installed and for the OS to be updated so you will still see the `common.sh` script being ran on each of our nodes. This will also install Kubeadm, Kubectl etc. But it will not run the Kubeadm commands to create and join our nodes into a cluster. From a8caefdca6337fe7411512ab150c59c486852693 Mon Sep 17 00:00:00 2001 From: sourav kumar Date: Sun, 19 Jun 2022 16:09:04 +0530 Subject: [PATCH 2/4] added correct the file location --- Days/day52.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Days/day52.md b/Days/day52.md index 2927b86..f63293b 100644 --- a/Days/day52.md +++ b/Days/day52.md @@ -23,7 +23,7 @@ I am going to be using a baseline this [blog and repository](https://devopscube. ### Kubernetes Lab environment -I have uploaded in [Kubernetes folder](days/kubernetes) the vagrantfile that we will be using to build out our environment. Grab this and navigate to this directory in your terminal. I am again using Windows so I will be using PowerShell to perform my workstation commands with vagrant. If you do not have vagrant then you can use arkade, we covered this yesterday when installing minikube and other tools. A simple command `arkade get vagrant` should see you download and install the latest version of vagrant. +I have uploaded in [Kubernetes folder](kubernetes) the vagrantfile that we will be using to build out our environment. Grab this and navigate to this directory in your terminal. I am again using Windows so I will be using PowerShell to perform my workstation commands with vagrant. If you do not have vagrant then you can use arkade, we covered this yesterday when installing minikube and other tools. A simple command `arkade get vagrant` should see you download and install the latest version of vagrant. When you are in your directory then you can simply run `vagrant up` and if all is configured correctly then you should see the following kick off in your terminal. @@ -33,7 +33,7 @@ When you are in your directory then you can simply run `vagrant up` and if all i ![](Images/Day52_Kubernetes2.png) -From the above you can see that we are going to build out 3 virtual machines, we will have a control plane node and then two worker nodes. If you head back to [Day 49](Days/day49.md) You will see some more description on these areas we see in the image. +From the above you can see that we are going to build out 3 virtual machines, we will have a control plane node and then two worker nodes. If you head back to [Day 49](day49.md) You will see some more description on these areas we see in the image. Also in the image we indicate that our kubectl access will come from outside of the cluster and hit that kube apiserver when in fact as part of the vagrant provisioning we are deploying kubectl on each of these nodes so that we can access the cluster from within each of our nodes. From 4dbc7ec2413ba2e26cf95fc60e96650909f8eb22 Mon Sep 17 00:00:00 2001 From: sourav kumar Date: Sun, 19 Jun 2022 16:12:58 +0530 Subject: [PATCH 3/4] added correct the file location --- Days/day52.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Days/day52.md b/Days/day52.md index f63293b..4212743 100644 --- a/Days/day52.md +++ b/Days/day52.md @@ -23,7 +23,7 @@ I am going to be using a baseline this [blog and repository](https://devopscube. ### Kubernetes Lab environment -I have uploaded in [Kubernetes folder](kubernetes) the vagrantfile that we will be using to build out our environment. Grab this and navigate to this directory in your terminal. I am again using Windows so I will be using PowerShell to perform my workstation commands with vagrant. If you do not have vagrant then you can use arkade, we covered this yesterday when installing minikube and other tools. A simple command `arkade get vagrant` should see you download and install the latest version of vagrant. +I have uploaded in [Kubernetes folder](Days/kubernetes) the vagrantfile that we will be using to build out our environment. Grab this and navigate to this directory in your terminal. I am again using Windows so I will be using PowerShell to perform my workstation commands with vagrant. If you do not have vagrant then you can use arkade, we covered this yesterday when installing minikube and other tools. A simple command `arkade get vagrant` should see you download and install the latest version of vagrant. When you are in your directory then you can simply run `vagrant up` and if all is configured correctly then you should see the following kick off in your terminal. From 0f6ce1dc98043d4f5adff79c31ebb9997eb08e39 Mon Sep 17 00:00:00 2001 From: sourav kumar Date: Sun, 19 Jun 2022 16:19:12 +0530 Subject: [PATCH 4/4] added correct the file location --- Days/day52.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Days/day52.md b/Days/day52.md index 4212743..26dc78a 100644 --- a/Days/day52.md +++ b/Days/day52.md @@ -23,7 +23,7 @@ I am going to be using a baseline this [blog and repository](https://devopscube. ### Kubernetes Lab environment -I have uploaded in [Kubernetes folder](Days/kubernetes) the vagrantfile that we will be using to build out our environment. Grab this and navigate to this directory in your terminal. I am again using Windows so I will be using PowerShell to perform my workstation commands with vagrant. If you do not have vagrant then you can use arkade, we covered this yesterday when installing minikube and other tools. A simple command `arkade get vagrant` should see you download and install the latest version of vagrant. +I have uploaded in [Kubernetes folder](Kubernetes) the vagrantfile that we will be using to build out our environment. Grab this and navigate to this directory in your terminal. I am again using Windows so I will be using PowerShell to perform my workstation commands with vagrant. If you do not have vagrant then you can use arkade, we covered this yesterday when installing minikube and other tools. A simple command `arkade get vagrant` should see you download and install the latest version of vagrant. When you are in your directory then you can simply run `vagrant up` and if all is configured correctly then you should see the following kick off in your terminal.