Login to the Master Node/Server ssh nickm@10.154.2.90 sudo su - cd /root/k3s/k3s-helm-charts/grafana/ If you have not installed Helm 3.11 yet do this: Installing Helm 3.11 on a Linux Server 1. When working with K3S you need to run this command export KUBECONFIG=/etc/rancher/k3s/k3s.yaml 1.1 You can edit the .bashrc file put this on the top nano ~/.bashrc Reboot the server sudo reboot 2. Find the Helm Chart in the Repository You can search for Helm Charts here: https://artifacthub.

Podman PODMAN vs DOCKER - should you switch now you should be using PODMAN I’m Switching to Podman \ Docker registry https://registry.hub.docker.com/ https://hub.docker.com/ Gitlab GitHub Packages https://ghcr.io/ https://ghcr.io/ Introduction to GitHub Packages Publish to Github Packages GitHub Container Registry: BETTER Than Docker Hub? \ Host your own Docker registry Host your own docker registry | Local Docker Registry | Docker Registry How to Build Own Private Docker Hub Registry on Linux \

1. Introducing the Helm Chart Helm is the ultimate Kubernetes package manager Helm Charts are the Kubernetes packages. \ Helm is to Kubernetes what Yum or Apt is to linux.\ Artifacthub is to Helm Charts what Dockerhub is to Docker Images 2. How to use Helm to deploy applications Using existing Helm Charts. Production grade Helm Charts created by the developers of the applications Production grade Helm Charts created by VMware (Bitnami Charts) Making your own Helm Charts

1. Namespaces kubectl create namespace nico kubectl get namespaces kubectl delete namespace nico kubectl get all --namespace nico kubecyl get pods -n nico 2. Creating Resource Objects kubectl create deployment nginx --image=nginx --namespace=nginx kubectl create deployment redis --image=redis kubectl get deployments kubectl describe deployment nginx kubeclt get pods -n nginx 3. Creating Services kubectl create service nodeport nginx --tcp=80:80 --namespace=nginx kubectl get svc --all-namespaces kubectl get service --namespace=nginx 4. Exposing deployments (PODs) as Services Currently we are exposing services inside the Cluster

Deploying Nginx using Kubectl commands Kubernetes Lesson2 Kubectl Demos The Kubectl commands Explaining the Kubernetes Kubectl Commands

The Helm Chart in the Repository You can search for Helm Charts here: https://artifacthub.io/ Searching for a Helm Chart Lets search for wordpress Prefer to use Bitnami Helm Charts these are official Helm Charts maintained by VMware Viewing all the Manifests The TEMPLATES button is used to view all the Manifests You will notice that values are replaced with GO Lang variables: In the ingress.yaml file you will find: {{- if .

Login to the Master Node/Server ssh nickm@10.154.2.90 sudo su - cd /root/k3s/k3s-helm-charts/elasticsearch/ If you have not installed Helm 3.11 yet do this: Installing Helm 3.11 on a Linux Server 1. When working with K3S you need to run this command export KUBECONFIG=/etc/rancher/k3s/k3s.yaml 1.1 You can edit the .bashrc file put this on the top nano ~/.bashrc Reboot the server sudo reboot 2. Find the Helm Chart in the Repository You can search for Helm Charts here: https://artifacthub.

Kubernetes Lesson 2 Demo A. Nginx NodePort example 1. Creating a Namespace kubectl create namespace my-nginx 2. Creating A deployment kubectl create deployment my-nginx --image=nginx --replicas=2 -n=my-nginx kubectl create deployment my-nginx --image=nginx 3. Verifying the deployment kubectl get pods -n=my-nginx kubectl get pods -o wide -n=my-nginx kubectl get all -n=my-nginx kubectl get all -o wide -n=my-nginx 4. Scale the deployment kubectl scale --replicas=2 deployment/my-nginx -n=my-nginx 5. Verifying the deployment kubectl get pods -o wide -n=my-nginx 6.

We are going to learn Kubernetes looking at how Manifests can simplify the deployment of applications in the Kubernetes Cluster 1. What you need to be able to do this at home? You need two Linux Servers Ideally Ubuntu Server VMs If you are not familiar with Hardware Virtualization please watch this video Explaining Hardware Virtualization Now you can use Virtualbox and create Virtual machines but even better use Proxmox

Do this deployment after the Prometheus Deployment Clone Grafana Kubernetes Manifests from Github git clone https://github.com/bibinwilson/kubernetes-grafana.git Create namespace monitoring (if not created for Prometheus Manifest Deployment) kubectl create namespace monitoring Create Manifest : grafana-datasource-config.yaml # nano grafana-datasource-config.yaml kubectl apply -f kubernetes-grafana/grafana-datasource-config.yaml Create a file named deployment.yaml # vi deployment.yaml kubectl apply -f kubernetes-grafana/deployment.yaml Verify Deployment kubectl get all -n monitoring expect kubectl get all -n monitoring NAME READY STATUS RESTARTS AGE pod/grafana-68b7b49968-h6pgx 1/1 Running 0 34s NAME READY UP-TO-DATE AVAILABLE AGE deployment.