Skip to content

Commit

Permalink
move original files cilum.md and cgroups.md into new docs-folders str…
Browse files Browse the repository at this point in the history
…ucture
  • Loading branch information
Payback159 committed May 6, 2024
1 parent a6e47ba commit 87ee177
Show file tree
Hide file tree
Showing 3 changed files with 0 additions and 333 deletions.
72 changes: 0 additions & 72 deletions docs/cgroups.md

This file was deleted.

248 changes: 0 additions & 248 deletions docs/cilium.md

This file was deleted.

13 changes: 0 additions & 13 deletions docs/operations/cgroups.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,17 +69,4 @@ After the setup, the cgroups hierarchy is as follows:
└── ...
```

## 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.

When `kube_enable_auto_reserved_resources` is set to `true`, Kubespray calculates resource reservations as follows:

CPU: 1% of the total CPU cores on the host machine + 80 millicores
Memory: 5% of the total available system memory + 330 Megabytes

This approach ensures that kubelet has sufficient resources to function properly while leaving the majority of resources available for your workloads.

After the setup, the cgroups hierarchy remains the same as before.

You can learn more in the [official kubernetes documentation](https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/).

0 comments on commit 87ee177

Please sign in to comment.