<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Articles :: Kubernetes training</title><link>https://k8s-school.fr/labs/k8s/en/articles/index.html</link><description>You will find technical articles about Kubernetes here.</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2025 Fabrice Jammes - Licensed under CC BY-SA 4.0</copyright><lastBuildDate>Sun, 21 Sep 2025 14:15:26 +1000</lastBuildDate><atom:link href="https://k8s-school.fr/labs/k8s/en/articles/index.xml" rel="self" type="application/rss+xml"/><item><title>Essential kubectl Commands</title><link>https://k8s-school.fr/labs/k8s/en/articles/kubectl-essential/index.html</link><pubDate>Tue, 11 Jun 2024 14:15:26 +1000</pubDate><guid>https://k8s-school.fr/labs/k8s/en/articles/kubectl-essential/index.html</guid><description>Duration: 5 min read
Official documentation for kubectl kubectl quick reference
List a Resource from the API Server To retrieve details of a specific resource in Kubernetes, use the following command:
kubectl get &lt;resource-name&gt; &lt;obj-name&gt; [-o yaml/json] Describe a Resource from the API Server To get a detailed description of a specific resource, use:</description></item><item><title>Alternatives for deprecated 'kubectl run' commands</title><link>https://k8s-school.fr/labs/k8s/en/articles/kubectl-run-deprecated/index.html</link><pubDate>Mon, 30 Sep 2019 00:00:00 +0000</pubDate><guid>https://k8s-school.fr/labs/k8s/en/articles/kubectl-run-deprecated/index.html</guid><description>Written by: Karim AMMOUS (LinkedIn). Date: Sept 30, 2019 · 5 min read
kubectl run command is a convenient and useful way to quickly create kubernetes resources without dealing with yaml files. Since kubernetes v1.12, creation acknowledgment (“object created”) is preceded by a message noting that this creation command is deprecated and will no longer be available in future kubectl releases.
Indeed, we can create some “runnable” resources like Pods and Deployments (the complete list) using kubectl run command by setting the --generator flag with the appropriate value. However, those generators have been deprecated since v1.12 except ‘run-pod/v1’ generator.</description></item><item><title>Taints</title><link>https://k8s-school.fr/labs/k8s/en/articles/taints_and_tolerations/01-taints/index.html</link><pubDate>Sat, 07 Mar 2020 17:15:52 +0000</pubDate><guid>https://k8s-school.fr/labs/k8s/en/articles/taints_and_tolerations/01-taints/index.html</guid><description>Add Taints to nodes To make it simple, adding a taint to a node is like adding a bad smell to this node. Only pods that tolerate that bad smell can be scheduled on the node.
Just like labels, one or more taints can be applied to a node; this marks that the node should not accept any pods that do not tolerate the taints.</description></item><item><title>Tolerations</title><link>https://k8s-school.fr/labs/k8s/en/articles/taints_and_tolerations/02-tolerations/index.html</link><pubDate>Sat, 07 Mar 2020 17:15:52 +0000</pubDate><guid>https://k8s-school.fr/labs/k8s/en/articles/taints_and_tolerations/02-tolerations/index.html</guid><description>Add Tolerations to pods Tolerations can be added to pods, or pod templates (for Daemonset, Replicaset, Deployment and Statefulset). Based on the taints on a node, the Kubernetes scheduler will allow to run the Pod on this node if it has the corresponding tolerations.
Toleration syntax in Pod spec.
spec: tolerations: - key: node-role.kubernetes.io/master effect: NoSchedule</description></item><item><title> Kustomize - Kubernetes Native Configuration Management</title><link>https://k8s-school.fr/labs/k8s/en/articles/kustomize-overview/index.html</link><pubDate>Sun, 21 Sep 2025 14:15:26 +1000</pubDate><guid>https://k8s-school.fr/labs/k8s/en/articles/kustomize-overview/index.html</guid><description>What is Kustomize? Native Kubernetes tool for customizing application configurations Template-free: Works with plain YAML manifests Declarative approach: Define variations as patches and overlays Built into kubectl since v1.14 (kubectl apply -k) Key Principles Base + Overlays: Keep common resources in base, environment-specific changes in overlays No templating: Pure YAML manipulation DRY (Don’t Repeat Yourself): Reuse base configurations across environments Core Concepts Directory Structure ├── base/ │ ├── kustomization.yaml │ ├── deployment.yaml │ └── service.yaml └── overlays/ ├── dev/ │ └── kustomization.yaml ├── staging/ │ └── kustomization.yaml └── production/ ├── kustomization.yaml └── patches/ └── resources-patch.yaml kustomization.yaml The main configuration file that defines:</description></item><item><title>Kubernetes official icons</title><link>https://k8s-school.fr/labs/k8s/en/articles/k8s-official-icons/index.html</link><pubDate>Tue, 22 Oct 2019 15:15:26 +1000</pubDate><guid>https://k8s-school.fr/labs/k8s/en/articles/k8s-official-icons/index.html</guid><description>Written by: Fabrice JAMMES (LinkedIn). Date: Oct 22, 2019 · 5 min read
Tim Hockin, Principal Software Engineer at Google for Kubernetes, shared with us these lovely Kubernetes icons, under Creative Commons Attribution 4.0 International License CC-BY. K8s-school now shares them with you, feel free to use it in your talks and slides!
Kubernetes icons by Google Cloud</description></item></channel></rss>