Merge pull request #43 from Namanv0509/k8s-workshop

 k8s workshop

Author: leecalcote

content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/kubernetes-workshop/_index.md

@@ -0,0 +1,6 @@
+---
+title: "Kubernetes Workshop"
+description: "This learning path provides an introduction to Kubernetes, focusing on its architecture, components, and how to manage clusters effectively."
+weight: 1
+banner: "/98e16360-a366-4b78-8e0a-031da07fdacb/images/kubernetes-icon.svg"
+---

content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/kubernetes-workshop/concepts/_index.md

@@ -0,0 +1,99 @@
+---
+docType: "Course"
+title: "Concepts"
+description: "Kubernetes Basic Concepts"
+courseTitle: "Concepts"
+weight: 1
+banner: "/98e16360-a366-4b78-8e0a-031da07fdacb/images/kubernetes-icon.svg"
+---
+
+## History
+
+Kubernetes also called *k8s* (a "k" followed by 8 chars and a "s") or simply *kube* means "Helmsman" in Greek. It is a container orchestrator inspired by Google Borg System which were orchestrating billions of containers on Google infrastructure.  
+
+Version *v1.0.0* of Kubernetes was released in July 2015, the last version as of today (October 2024) is *v1.31.1*. The release cycle is quite fast with 3 minor releases per year.
+
+## Main functionalities
+
+Kubernetes is a container orchestrator offering main functionalities, such as:
+
+- Management of applications running in containers
+- Self-healing
+- Service discovery
+- Usage of Secrets and Configurations
+- Long-running process and batch jobs
+- Role Based Access Control (RBAC)
+- Storage Orchestration
+
+## Manages applications in production
+
+![environments]({{< usestatic "k8s-workshop/environments.png" >}})
+## Major project in the open-source ecosystem
+
+Kubernetes is the first graduated project within the [CNCF](https://cncf.io/projects), it was followed by major players like [etcd](https://etcd.io) and [Prometheus](https://prometheus.io/) 
+
+![cncf]({{< usestatic "k8s-workshop/cncf.png" >}})
+## What is a Kubernetes cluster made of ?
+
+A Kubernetes cluster is composed of nodes, where a node is either a virtual machine or a bare metal server. A node can belong to the Control Plane which run processes in charge of managing the cluster and the applications running on it. Or, a node can be a Worker dedicated to run Pods, a group of containers sharing a network stack and storage.
+
+![cluster]({{< usestatic "k8s-workshop/cluster.png" >}})
+
+## How to access a cluster
+
+A cluster usually comes with a kubeconfig file which contains all the information to communicate with the cluster API Server. This file can be used to configure the standard *kubectl* binary to manage the cluster. The kubeconfig file can also be used with tools like [k9s](https://k9scli.io/), [Mirantis Lens](https://k8slens.dev/), ... which give a higher level view of the cluster.
+
+![access]({{< usestatic "k8s-workshop/access.png" >}})
+
+## Various workload resources for different use cases
+
+To run a Pod we often rely on a higher level resource, instead of running it directly. The workload resources are:
+
+- Deployment : web server
+- DaemonSet : one agent per node
+- Job / CronJob : batch
+- StatefulSet : stateful application
+
+![workloads]({{< usestatic "k8s-workshop/workloads.png" >}})
+
+A request that reaches a Service is load-balanced between the exposed Pods
+
+![service]({{< usestatic "k8s-workshop/service.png" >}})
+
+
+A Pod can use several resources
+
+- ConfigMap : contains configuration data
+- Secret : contains sensitive data
+- PersistentVolumeClaim / PersistentVolume : storage management
+
+![pod-resources]({{< usestatic "k8s-workshop/pod-resources.png" >}})
+
+
+## Several types of resources
+
+![summary]({{< usestatic "k8s-workshop/summary.png" >}})
+
+## An application runs in a Namespace
+
+
+![namespace]({{< usestatic "k8s-workshop/namespace.png" >}})
+
+## Resource creation
+
+Each resource is defined in a YAML specification which is sent to the API Server using the kubectl binary.
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+  name: www
+spec:
+  containers:
+  - name: www
+    image: nginx:1.24
+```
+
+```bash
+kubectl apply -f www.yaml
+```

content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/kubernetes-workshop/local/_index.md

@@ -0,0 +1,90 @@
+---
+docType: "Course"
+title: "Creation of a local cluster"
+description: "Create Local kubernetes cluster"
+courseTitle: "Creation of a local cluster"
+weight: 2
+banner: "/98e16360-a366-4b78-8e0a-031da07fdacb/images/kubernetes-icon.svg"
+
+---
+
+Using a local cluster is very handy to get started with Kubernetes, or to test things quickly. In this example, we'll use [K3s](https://k3s.io), a lightweight Kubernetes distribution (5 's' fewer than k8s :) ). K3s is a certified distribution, well-suited for IoT, Edge computing, and which works well with huge servers.
+
+In this section, we'll use [Multipass](https://multipass.run) to create an Ubuntu virtual machine and install k3s on this one. Multipass is a convenient tool to launch Ubuntu VM on Mac/Linux/Windows; it can be installed on your environment following [the documentation](https://canonical.com/multipass/install).
+
+#### info
+We use Multipass as it is handy and lightweight, but feel free to use the tool you're the most comfortable with. If you use another tool, please just make sure to adapt the commands below.
+
+
+We'll only create a single node Kubernetes cluster in this section.
+
+## Pre-requisite
+
+On your local machine, [install kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl). It's the essential tool for communicating with a Kubernetes cluster from the command line.
+
+## Creating an Ubuntu VM
+
+Once you've installed Multipass, create an Ubuntu 24.04 virtual machine named *k3s* with 2G of memory allocated. This process should take a few tens of seconds.
+
+```bash
+multipass launch --name k3s --memory 2G
+```
+
+Then get the IP address of the newly created VM.
+
+```bash
+IP=$(multipass info k3s | grep IP | awk '{print $2}')
+```
+
+## Installing k3s
+
+Run the following command to install k3s the VM. This process should also take a few tens of seconds.
+
+```bash
+multipass exec k3s -- bash -c "curl -sfL https://get.k3s.io | sh -"
+```
+
+#### info
+The command `curl -sfL https://get.k3s.io | sh -`, used to install k3s comes from the official [k3s](https://k3s.io) documentation
+
+
+## Getting the kubeconfig file
+
+Retrieve the configuration file generated during Kubernetes installation on your local machine:
+
+```bash
+multipass exec k3s sudo cat /etc/rancher/k3s/k3s.yaml > k3s.cfg.tmp
+```
+
+In this file, replace the local IP address (127.0.0.1) with the IP address of the VM you created. This IP address should be in the $IP environment variable.
+
+```bash
+cat k3s.cfg.tmp | sed "s/127.0.0.1/$IP/" > k3s.cfg
+```
+
+Then set the *KUBECONFIG* environment variable to point to the previously retrieved configuration file:
+
+```bash
+export KUBECONFIG=$PWD/k3s.cfg
+```
+
+### Info
+This environment variable configures the *kubectl* binary so it can communicate with the cluster.
+
+
+You can now communicate with the cluster's API Server.
+
+List of the cluster's node (only one in this example):
+
+```bash
+kubectl get nodes
+```
+
+List of the Pods running in the cluster:
+
+```bash
+kubectl get pods -A
+```
+
+You'll use this local cluster to do the exercises of the [next section](../resources/).
+

content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/kubernetes-workshop/main-resources/_index.md

@@ -0,0 +1,8 @@
+---
+docType: "Course"
+title: "Resources"
+description: "Learn and Practice Main Resources"
+courseTitle: "Resources"
+weight: 3
+banner: "/98e16360-a366-4b78-8e0a-031da07fdacb/images/kubernetes-icon.svg"
+---

content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/kubernetes-workshop/main-resources/content/configuration/_index.md

@@ -0,0 +1,8 @@
+---
+docType: "Chapter"
+title: "Configuration"
+description: "Manage configuration and sensitive data"
+courseTitle: "Configuration"
+weight: 1
+banner: "/98e16360-a366-4b78-8e0a-031da07fdacb/images/configuration.png"
+---