From 13697e14c90acded2175414f2a969f46c913a229 Mon Sep 17 00:00:00 2001 From: sourav kumar Date: Sun, 19 Jun 2022 16:01:40 +0530 Subject: [PATCH] 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.