Skip to content

Commit f243597

Browse files
Namanv0509Namanv0509
authored
Merge pull request #29 from vr-varad/update/intro-k8
Update Intro Kubernetes Learning Path
2 parents 5224da3 + 536bea9 commit f243597

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

60 files changed

+532
-2
lines changed

‎content/learning-paths/090e7114-509a-4046-81f1-9c5fb8daf724/intro-kubernetes/_index.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
title: "INTRO Kubernetes"
3+
description: "New to container and container orchestration? This INTRO Kubernetes - Learning Path covers the foundational topics for a non-technical audience and conveys the benefits of containers and container orchestration for modern IT scenarios. It will help you learn the basics of terminology associated, understand the essential components' functions, and understand why these new technologies are so important."
4+
themeColor: "#3C494F"
5+
cardImage: "/images/learning-path/kubernetes-icon.svg"
6+
courses: 6
7+
weight: 1
8+
---

‎content/learning-paths/090e7114-509a-4046-81f1-9c5fb8daf724/intro-kubernetes/kubernetes-building-blocks/_index.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
title: "Kubernetes Building Blocks"
3+
description: "This section covers the fundamental components of Kubernetes, including Pods, Services, Deployments, and more. Understanding these building blocks is essential for effectively deploying and managing applications in a Kubernetes environment."
4+
themeColor: "#3C494F"
5+
cardImage: "/images/learning-path/kubernetes-icon.svg"
6+
weight: 4
7+
---

‎content/learning-paths/090e7114-509a-4046-81f1-9c5fb8daf724/intro-kubernetes/kubernetes-building-blocks/content/cronjob.md‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
docType: "Chapter"
3+
id: "CRONJOBs"
4+
chapterTitle: "CRONJOBs"
5+
description: ""
6+
title: "CRONJOBs"
7+
weight: 7
8+
---
9+
10+
### **CRONJOBs**
11+
12+
Use familiar cron syntax to schedule tasks. CronJobs are part of the Batch API for creating short-lived non-server tools. CronJobs provide a method for scheduling the execution of Pods. They are excellent for running periodic tasks like backups, reports, and automated tests.
13+
14+
![image]({{< usestatic "intro-k8/cronjob.png" >}})

‎content/learning-paths/090e7114-509a-4046-81f1-9c5fb8daf724/intro-kubernetes/kubernetes-building-blocks/content/deamonset.md‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
docType: "Chapter"
3+
id: "DEAMONSETs"
4+
chapterTitle: "DEAMONSETs"
5+
description: ""
6+
title: "DEAMONSETs"
7+
weight: 5
8+
---
9+
10+
### **DEAMONSETs**
11+
12+
DaemonSets have many use cases – one frequent pattern is to use DaemonSets to install or configure each host node. DaemonSets provide a way to ensure that a Pod copy is running on every node in the cluster. As a cluster grows and shrinks, the DaemonSet spreads these specially labelled Pods across all nodes.
13+
14+
![image]({{< usestatic "intro-k8/deamonset.png" >}})

‎content/learning-paths/090e7114-509a-4046-81f1-9c5fb8daf724/intro-kubernetes/kubernetes-building-blocks/content/deployments.md‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
docType: "Chapter"
3+
id: "DEPLOYMENTs"
4+
chapterTitle: "DEPLOYMENTs"
5+
description: ""
6+
title: "DEPLOYMENTs"
7+
weight: 4
8+
---
9+
10+
### **DEPLOYMENTs**
11+
12+
A Deployment is a higher-order abstraction that controls deploying and maintaining a set of Pods. Behind the scenes, it uses a ReplicaSet to keep the Pods running, but it offers sophisticated logic for deploying, updating, and scaling a set of Pods within a cluster. Deployments support rollbacks and rolling updates. Rollouts can be paused if needed.
13+
14+
![image]({{< usestatic "intro-k8/deployment.gif" >}})

‎content/learning-paths/090e7114-509a-4046-81f1-9c5fb8daf724/intro-kubernetes/kubernetes-building-blocks/content/imp-building-blocks.md‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
docType: "Chapter"
3+
id: "Important Building Blocks"
4+
chapterTitle: "Important Building Blocks"
5+
description: ""
6+
title: "Important Building Blocks"
7+
weight: 1
8+
---
9+
10+
### **Important Building Blocks**
11+
12+
An application running on Kubernetes is a workload. Whether your workload is a single component or several that work together, on Kubernetes, you run it inside a set of Pods. In Kubernetes, a Pod represents a set of running containers on your cluster.
13+
14+
A critical fault on the node where your Pod runs means that all the Pods on that node fail. Kubernetes treats that level of failure as final: you would need to create a new Pod to recover, even if the node later becomes healthy. However, to make life easier, you don't need to manage each Pod directly.
15+
16+
Instead, you can use workload resources that address a set of Pods on your behalf. These resources configure controllers that ensure the correct number and right kind of Pods are running to match the state you specified. Kubernetes provides several built-in workload resources: Pods, ReplicaSet, Deployment, DaemonSet, Ingress, and CronJob, to name a few of those building blocks.
17+
18+
![image]({{< usestatic "intro-k8/kubernetes5.png" >}})

‎content/learning-paths/090e7114-509a-4046-81f1-9c5fb8daf724/intro-kubernetes/kubernetes-building-blocks/content/ingress.md‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
docType: "Chapter"
3+
id: "INGRESS"
4+
chapterTitle: "INGRESS"
5+
description: ""
6+
title: "INGRESS"
7+
weight: 6
8+
---
9+
10+
### **INGRESS**
11+
12+
Route traffic to and from the cluster. Provide a single SSL endpoint for multiple applications. Many implementations of an ingress allow you to customize your platform. Ingresses provide a way to declare that they should channel traffic from the outside of the cluster into destination points within the cluster. One single external Ingress point can accept traffic destined to many internal services.
13+
14+
![image]({{< usestatic "intro-k8/ingress2.png" >}})

‎content/learning-paths/090e7114-509a-4046-81f1-9c5fb8daf724/intro-kubernetes/kubernetes-building-blocks/content/pod.md‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
docType: "Chapter"
3+
id: "PODs"
4+
chapterTitle: "PODs"
5+
description: ""
6+
title: "PODs"
7+
weight: 2
8+
---
9+
10+
### **PODs**
11+
12+
Pods are the basic building blocks to run containers inside of Kubernetes. Every Pod holds at least one container and controls the execution of that container. If all containers terminate, the Pod terminates too. Mounting storage, setting environment variables, and feed information into the container are all functions provided by the Pod.
13+
14+
![image]({{< usestatic "intro-k8/pod.png" >}})
15+
16+
Pods are the smallest deployable units of computing that you can create and manage in Kubernetes. Pods in a Kubernetes cluster are used in two main ways:
17+
18+
- **Pods that run a single container**
19+
20+
The "one-container-per-Pod" model is the most common Kubernetes use case; in this case, you can think of a Pod as a wrapper around a single container; Kubernetes manages Pods rather than managing the containers directly.
21+
22+
- **Pods that run multiple containers that need to work together**
23+
24+
A Pod can encapsulate an application composed of multiple co-located containers tightly coupled and need to share resources. These co-located containers form a single cohesive unit of service—for example, one container serving data stored in a shared volume to the public. In contrast, a separate sidecar container refreshes or updates those files. The Pod wraps these containers, storage resources, and an ephemeral network identity together as a single unit.

‎content/learning-paths/090e7114-509a-4046-81f1-9c5fb8daf724/intro-kubernetes/kubernetes-building-blocks/content/replicaet.md‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
docType: "Chapter"
3+
id: "REPLICASETs"
4+
chapterTitle: "REPLICASETs"
5+
description: ""
6+
title: "REPLICASETs"
7+
weight: 3
8+
---
9+
10+
### **REPLICASETs**
11+
12+
A ReplicaSet's purpose is to maintain a stable set of replica Pods running at any given time to guarantee the availability of a specified number of identical Pods. However, a Deployment is a higher-level concept that manages ReplicaSets and provides declarative updates to Pods and other useful features. Therefore, Deployments are recommended instead of directly using ReplicaSets.
13+
14+
![image]({{< usestatic "intro-k8/replicaset.gif" >}})

‎content/learning-paths/090e7114-509a-4046-81f1-9c5fb8daf724/intro-kubernetes/kubernetes-details/_index.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
title: "Kubernetes Details"
3+
description: "Explore the intricate details of Kubernetes, its architecture, components, and how it orchestrates containerized applications effectively."
4+
themeColor: "#3C494F"
5+
cardImage: "/images/learning-path/kubernetes-icon.svg"
6+
weight: 3
7+
---

0 commit comments

Comments
 (0)