kubernetes-sigs
/
kubespray
mirror of https://github.com/kubernetes-sigs/kubespray.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

remove all references to kube_master* variables

pull/11082/head
Payback159 2024-10-07 22:21:44 +02:00
parent fd1ae56def
commit 3a3256c7b8
1 changed files with 1 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/operations/cgroups.md
View File

@ -30,11 +30,6 @@ kube_memory_reserved: 256Mi
kube_cpu_reserved: 100m kube_cpu_reserved: 100m
# kube_ephemeral_storage_reserved: 2Gi # kube_ephemeral_storage_reserved: 2Gi
# kube_pid_reserved: "1000" # kube_pid_reserved: "1000"
# Reservation for master hosts
kube_master_memory_reserved: 512Mi
kube_master_cpu_reserved: 200m
# kube_master_ephemeral_storage_reserved: 2Gi
# kube_master_pid_reserved: "1000"
# Set to true to reserve resources for system daemons # Set to true to reserve resources for system daemons
system_reserved: true system_reserved: true
@ -44,11 +39,6 @@ system_memory_reserved: 512Mi
system_cpu_reserved: 500m system_cpu_reserved: 500m
# system_ephemeral_storage_reserved: 2Gi # system_ephemeral_storage_reserved: 2Gi
# system_pid_reserved: "1000" # system_pid_reserved: "1000"
# Reservation for master hosts
system_master_memory_reserved: 256Mi
system_master_cpu_reserved: 250m
# system_master_ephemeral_storage_reserved: 2Gi
# system_master_pid_reserved: "1000"
``` ```
After the setup, the cgroups hierarchy is as follows: After the setup, the cgroups hierarchy is as follows:
@ -72,7 +62,7 @@ After the setup, the cgroups hierarchy is as follows:
## Automatic Resource Reservation Calculation ## Automatic Resource Reservation Calculation
While manually specifying resource reservations for kube and system daemons works, Kubespray offers a more convenient approach. You can set the `kube_enable_auto_reserved_resources` flag to `true`. This instructs Kubespray to automatically calculate appropriate resource reservations for `kube_[master]_cpu_reserved` and `kube_[master]_memory_reserved` based on your host size. This eliminates the need for manual configuration, simplifying the process. While manually specifying resource reservations for kube and system daemons works, Kubespray offers a more convenient approach. You can set the `kube_enable_auto_reserved_resources` flag to `true`. This instructs Kubespray to automatically calculate appropriate resource reservations for `kube_cpu_reserved` and `kube_memory_reserved` based on your host size. This eliminates the need for manual configuration, simplifying the process.
When `kube_enable_auto_reserved_resources` is set to `true`, Kubespray calculates resource reservations as follows: When `kube_enable_auto_reserved_resources` is set to `true`, Kubespray calculates resource reservations as follows: