k8s

Create your own CRD CRD (Custom Resource Definition) This defines how we want our custom Kubernetes objects to look and behave. The name of the CRD must follow this format: . Example: albertocrds.crds.albertogalvez.com To list existing CRDs: 1 kubectl get crds In the custom resource manifest, you must specify: 1 2 3 apiVersion: crds.albertogalvez.com/v1 kind: Albertocrds ... Controller Now we create our controller, which is simply an application running continuously in Kubernetes, listening for changes to our custom resources....

Kubectl kubectl taint Taints are used to prevent pods from being scheduled on certain nodes unless those pods have the appropriate tolerations. 1 kubectl taint nodes node1 node2 node3 node-role.kubernetes.io/control-plane:NoSchedule- node-role.kubernetes.io/control-plane:NoSchedule is a taint typically applied to control plane nodes to prevent regular pods from being scheduled on them. The - at the end removes the taint from the nodes. If you want to add the taint instead of removing it, just remove the - at the end:...

K9scli Shortcuts 1 2 3 4 5 6 7 Ctrl-d: delete. Ctrl-k: kill (no confirmation). Ctrl-w: toggle wide columns. (Equivalent to kubectl … -o wide) Ctrl-z: toggle error state Ctrl-e: hide header. Ctrl-s: save output (e.g. the YAML) to disk. Ctrl-l: rollback. Sort by Column If you want to sort any view (Pod/Services) based on some exact column - you can just press Shift + Column Initial e.g. If you want to sort items by column Age - Just press Shift + A...

Pod disruption budget PDBs define the minimum number of replicas that must remain running during disruptions. This prevents critical workloads from being evicted but can hinder node scaling. A PodDisruptionBudget (PDB) is a Kubernetes object that specifies the number of pods that can be unavailable in deployment, maintenance, or at any given time. This helps to ensure that your applications remain available even if some of their pods are terminated or evicted....

kustomize lets you customize raw, template-free YAML files for multiple purposes, leaving the original YAML untouched and usable as is.

Installing talos on a Turing Piv2 board with cm4 modules.

Automated cluster scaling is a critical aspect of Kubernetes management, enabling your applications to dynamically adjust resources to meet changing demands. This involves two main mechanisms: Horizontal Pod Autoscaling (HPA) and Vertical Pod Autoscaling (VPA). Understanding these mechanisms and implementing them effectively can significantly enhance the scalability, reliability, and cost-efficiency of your Kubernetes environments. What is Automated Cluster Scaling? Automated cluster scaling refers to the process of dynamically adjusting the number of running pods (HPA) or their resource allocations (VPA) based on real-time metrics....

Kubernetes microservices

Kubernetes monitoring

Kubernetes networking