From 7d07d4f8fa62ed41c07d66ad954c4bb92b53913a Mon Sep 17 00:00:00 2001 From: William Graef Date: Tue, 1 Oct 2024 20:08:21 -0400 Subject: [PATCH] update taint ocne post --- content/posts/ocne/post-22/index.md | 2 +- content/posts/ocne/post-24/index.md | 35 +++++++++++++---------------- 2 files changed, 16 insertions(+), 21 deletions(-) diff --git a/content/posts/ocne/post-22/index.md b/content/posts/ocne/post-22/index.md index c83d9756..1334e434 100644 --- a/content/posts/ocne/post-22/index.md +++ b/content/posts/ocne/post-22/index.md @@ -26,4 +26,4 @@ In this tutorial, you'll learn how to: ### Prerequisites - Installation of Oracle Cloud Native Environment - - a single control and worker node + - a single control and worker node diff --git a/content/posts/ocne/post-24/index.md b/content/posts/ocne/post-24/index.md index 9bb91890..7469f9eb 100644 --- a/content/posts/ocne/post-24/index.md +++ b/content/posts/ocne/post-24/index.md @@ -1,9 +1,9 @@ --- title: "Use Taints and Tolerations" -date: 2024-03-07 +date: 2024-10-2 draft: false -summary: "This tutorial shows how to use Taints and Tolerations with Oracle Cloud Native Environment." -tags: ["ocne", "lab", "tutorial", "ocne-k8s"] +summary: "Learn to use taints and tolerations with Oracle Cloud Native Environment." +tags: ["ocne", "ocne2", "lab", "tutorial", "ocne-k8s"] showDate: true --- @@ -15,29 +15,24 @@ showDate: true ## Details -Taints allow the Kubernetes administrator to prevent unwanted Pods from executing on a predefined set of nodes. Tolerations allow any Pods to deploy onto a node with a matching Taint. Together these allow the administrator to fine-tune how Pods schedule to Nodes. +The ability to influence the way Pods are [scheduled](https://kubernetes.io/docs/concepts/scheduling-eviction/) to provide the best performance, reduce running costs, and make Kubernetes cluster management easier is an essential skill for an administrator to master. Taints and tolerations work with [Node Affinity](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity) to attract Pods to a set of nodes. [Taints and tolerations](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) have the opposite effect by allowing nodes to repel Pods. Frequent use cases for taints and tolerations include: -However, it is important to note that taints and tolerations cannot ensure that a pod schedules to a specific node. The Kubernetes scheduler can deploy a pod onto any node without a taint that repels it. Instead, use Node affinity when control over where Pods schedule is required. +- Identifying nodes with special hardware. +- The ability to dedicate nodes to specific application Pods. +- The ability to define custom conditions to evict a Pod from a node. -This tutorial shows how to create and use Taints and Tolerations with Oracle Cloud Native Environment. +*Taints* allow the Kubernetes administrator to prevent unwanted Pods from executing on a predefined set of nodes. *Tolerations* allow any Pods to deploy onto a node with a matching taint. Together, these allow the administrator to fine-tune how Pods schedule to nodes. + +**Important:** Taints and tolerations **cannot ensure that a Pod schedules to a specific node**. The Kubernetes scheduler can deploy a Pod onto any node without a taint that repels it. Instead, use node affinity when controlling where Pod scheduling is required. ### Objectives -You will learn: +In this tutorial, you will learn: -- The difference between a Taint and a Toleration -- How to use Taints and Tolerations to influence application deployment on Oracle Cloud Native Environment. +- The difference between a taint and a toleration +- How to use taints and tolerations to influence application deployment on Oracle Cloud Native Environment ### Prerequisites -- 4 Oracle Linux systems to use as: - - Operator node (ocne-operator-01) - - Kubernetes control plane node (ocne-control-01) - - Kubernetes worker nodes (ocne-worker-01 & ocne-worker-02) - -- Each system should have the latest Oracle Linux 8 (x86_64) installed - -- This environment is pre-configured with: - - An Oracle user account (used during the installation) with sudo access - - Key-based SSH, also known as password-less SSH, between the hosts - - Installation of Oracle Cloud Native Environment +- Installation of Oracle Cloud Native Environment + - a single control node and two worker nodes