From b71f7ce347e20b397162ecb3e192102275ebe3c0 Mon Sep 17 00:00:00 2001 From: sourav kumar Date: Mon, 20 Jun 2022 12:35:07 +0530 Subject: [PATCH 1/5] change the file location --- Days/day54.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Days/day54.md b/Days/day54.md index 10b78ae..d57e82c 100644 --- a/Days/day54.md +++ b/Days/day54.md @@ -29,7 +29,7 @@ In this first step we are simply going to create a stateless application within In the first demo we want to define everything we do with YAML, we could have a whole section on YAML but I am going to skim over this and leave some resources at the end that will cover YAML in more detail. -We could create the following as one YAML file or we could break this down for each aspect of our application, i.e this could be separate files for namespace, deployment and service creation but in this file below we separate these by using `---` in one file. You can find this file located [here](Days\Kubernetes\nginx-stateless-demo.yaml) +We could create the following as one YAML file or we could break this down for each aspect of our application, i.e this could be separate files for namespace, deployment and service creation but in this file below we separate these by using `---` in one file. You can find this file located [here](Kubernetes) (File name:- nginx-stateless-demo.yaml) ``` apiVersion: v1 From 886ee82ad12648751622e56ec4d963162f10f739 Mon Sep 17 00:00:00 2001 From: sourav kumar Date: Mon, 20 Jun 2022 12:42:45 +0530 Subject: [PATCH 2/5] change the file location --- Days/day55.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Days/day55.md b/Days/day55.md index 55dde32..cfdf7d0 100644 --- a/Days/day55.md +++ b/Days/day55.md @@ -108,7 +108,7 @@ The build out of the application looks like the below: ![](Images/Day55_Kubernetes1.png) -You can find the YAML configuration file for this application here[pacman-stateful-demo.yaml](Days/Kubernetes/pacman-stateful-demo.yaml) +You can find the YAML configuration file for this application here [pacman-stateful-demo.yaml](Kubernetes) ### StorageClass Configuration @@ -199,7 +199,7 @@ If we check our namespaces now you will see that we have a new ingress-nginx nam ![](Images/Day55_Kubernetes14.png) -Now we must create our ingress YAML configuration to hit our Pacman service I have added this file to the repository [pacman-ingress.yaml](Days/Kubernetes/pacman-ingress.yaml) +Now we must create our ingress YAML configuration to hit our Pacman service I have added this file to the repository [pacman-ingress.yaml](Kubernetes) We can then create this in our ingress namespace with `kubectl create -f pacman-ingress.yaml` From 8bf9fbcf9b746b095278613ab7129f91e1453b10 Mon Sep 17 00:00:00 2001 From: sourav kumar Date: Tue, 21 Jun 2022 19:05:07 +0530 Subject: [PATCH 3/5] change file location --- Days/day58.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Days/day58.md b/Days/day58.md index cdb9b6e..4ba3af8 100644 --- a/Days/day58.md +++ b/Days/day58.md @@ -9,7 +9,7 @@ id: 1048741 --- ## HashiCorp Configuration Language (HCL) -Before we start making stuff with Terraform we have to dive a little into HashiCorp Configuration Language (HCL). So far during our challenge we have looked at a few different scripting and programming languages and here is another one. We touched on the [Go programming language](Days/day07.md) then [bash scripts](Days/day19.md) we even touched on a little python when it came to [network automation](Days/day27.md) +Before we start making stuff with Terraform we have to dive a little into HashiCorp Configuration Language (HCL). So far during our challenge we have looked at a few different scripting and programming languages and here is another one. We touched on the [Go programming language](day07.md) then [bash scripts](day19.md) we even touched on a little python when it came to [network automation](day27.md) Now we must cover HashiCorp Configuration Language (HCL) if this is the first time you are seeing the language it might look a little daunting but its quite simple and very powerful. From 295ba4c512ec18d94202ddcf3862d8501526a6b2 Mon Sep 17 00:00:00 2001 From: sourav kumar Date: Sat, 25 Jun 2022 16:51:33 +0530 Subject: [PATCH 4/5] change file name --- Days/day70.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Days/day70.md b/Days/day70.md index cac954a..43ea508 100644 --- a/Days/day70.md +++ b/Days/day70.md @@ -30,7 +30,7 @@ The ability for developers to make small impactful changes regular means we get ### Ok, so what does this mean? -On [Day 5](day5.md) we covered a lot of the theory behind DevOps and as already mentioned here already that the CI/CD Pipeline is the backbone of the modern DevOps environment. +On [Day 5](day05.md) we covered a lot of the theory behind DevOps and as already mentioned here already that the CI/CD Pipeline is the backbone of the modern DevOps environment. ![DevOps](Images/Day5_DevOps8.png) From 16a0855599bea0345a868406071a7c8e2610ae53 Mon Sep 17 00:00:00 2001 From: sourav kumar Date: Sat, 25 Jun 2022 17:53:33 +0530 Subject: [PATCH 5/5] change file name --- Days/day72.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Days/day72.md b/Days/day72.md index f3195c8..f63838c 100644 --- a/Days/day72.md +++ b/Days/day72.md @@ -37,7 +37,7 @@ The first step is to get our minikube cluster up and running, we can simply do t ![](Images/Day72_CICD1.png) -I have added a folder with all the YAML configuration and values that can be found [here](days/CICD/Jenkins) Now that we have our cluster we can run the following to create our jenkins namespace. `kubectl create -f jenkins-namespace.yml` +I have added a folder with all the YAML configuration and values that can be found [here](CICD/Jenkins) Now that we have our cluster we can run the following to create our jenkins namespace. `kubectl create -f jenkins-namespace.yml` ![](Images/Day72_CICD2.png)