Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Prochaine révision
Révision précédente
elearning:workbooks:kubernetes_en:k8s03 [2024/12/30 05:41] – created adminelearning:workbooks:kubernetes_en:k8s03 [2025/01/17 16:39] (Version actuelle) admin
Ligne 1: Ligne 1:
 ~~PDF:LANDSCAPE~~ ~~PDF:LANDSCAPE~~
  
-Version - **2024.01**+Version - **2025.01**
  
 Last update : ~~LASTMOD~~ Last update : ~~LASTMOD~~
  
-======DOF304 - Working with Pods and Containers======+======DOE304 - Working with Pods and Containers======
  
 =====Module content===== =====Module content=====
  
-  * **DOF304 - Working with Pods and Containers**+  * **DOE304 - Working with Pods and Containers**
     * Curriculum     * Curriculum
     * LAB #1 - Application Configuration     * LAB #1 - Application Configuration
Ligne 18: Ligne 18:
         * Using Environment variables         * Using Environment variables
         * Using Configuration Volumes         * Using Configuration Volumes
-    * LAB #2 - Managing container resources+    * LAB #2 - Container Resource Management
       * 2.1 - Overview       * 2.1 - Overview
       * 2.2 - Resource Requests       * 2.2 - Resource Requests
Ligne 34: Ligne 34:
       * 4.3 - OnFailure       * 4.3 - OnFailure
       * 4.4 - Never       * 4.4 - Never
-    * LAB #5 - Multi-container Pod creation+    * LAB #5 - Creating Multi-container Pods
       * 5.1 - Overview       * 5.1 - Overview
       * 5.2 - Implementation       * 5.2 - Implementation
Ligne 52: Ligne 52:
 =====LAB #1 - Application Configuration===== =====LAB #1 - Application Configuration=====
  
-====.1 - Overview====+====1.1 - Overview====
  
 Application Configuration is the process of passing dynamic values to applications at runtime. Application Configuration is the process of passing dynamic values to applications at runtime.
Ligne 328: Ligne 328:
 Two important aspects of container resource management are : Two important aspects of container resource management are :
  
-  **Resource Requests**,+  **Resource Requests**,
     * A Resource Request is used to define resources such as CPU and memory at the time of **scheduling**. In other words, if the Resource Request is for 5GB, the pod scheduler will look for a node with 5GB of available RAM. A Resource Request is not a limit, as the pod can use more or less memory.     * A Resource Request is used to define resources such as CPU and memory at the time of **scheduling**. In other words, if the Resource Request is for 5GB, the pod scheduler will look for a node with 5GB of available RAM. A Resource Request is not a limit, as the pod can use more or less memory.
-  **Resource Limits**,+  **Resource Limits**,
     * A Resource Limit allows you to set limits on resources such as CPU and memory. Different Container Runtimes react in different ways to a Resource Limit. For example, some will stop the container process if the limit is exceeded. In the case of Docker, if the CPU limit is exceeded, Docker will limit CPU usage. On the other hand, if the memory limit is exceeded, Docker will kill the container process.     * A Resource Limit allows you to set limits on resources such as CPU and memory. Different Container Runtimes react in different ways to a Resource Limit. For example, some will stop the container process if the limit is exceeded. In the case of Docker, if the CPU limit is exceeded, Docker will limit CPU usage. On the other hand, if the memory limit is exceeded, Docker will kill the container process.
  
Ligne 446: Ligne 446:
   * **Startup Probes**,   * **Startup Probes**,
     * Similar to Liveness Probes, Startup Probes only intervene at container startup and stop when the application has started.     * Similar to Liveness Probes, Startup Probes only intervene at container startup and stop when the application has started.
-  * Readiness Probes**,+  * **Readiness Probes**,
     * Similar to Startup Probes in that they only intervene at pod startup, Readiness Probes are responsible for blocking traffic to pods until all containers in the pod have passed met the Readiness Probes criteria.     * Similar to Startup Probes in that they only intervene at pod startup, Readiness Probes are responsible for blocking traffic to pods until all containers in the pod have passed met the Readiness Probes criteria.
  
Ligne 1405: Ligne 1405:
 ----- -----
  
-Copyright © 2024 Hugh Norris+Copyright © 2025 Hugh Norris
Menu