1. Interface Path Differences Between cgroup v1 and v2 v1 1 2 3 4 /sys/fs/cgroup/cpu/cpu.cfs_quota_us /sys/fs/cgroup/cpu/cpuacct.usage /sys/fs/cgroup/memory/memory.limit_in_bytes /sys/fs/cgroup/memory/memory.usage_in_bytes v2 1 2 3 4 /sys/fs/cgroup/cpu.max /sys/fs/cgroup/cpu.stat /sys/fs/cgroup/memory.max /sys/fs/cgroup/memory.current cgroup v2 is the upgraded version of v1, with advantages such as more unified resource hierarchy management and precise resource isolation. But it also means that when writing code, the paths for reading the relevant interface files are different, so compatibility handling is required.

Elastic scaling mainly has three dimensions: HPA, which automatically scales the number of Pods based on utilization VPA, which automatically sets a Pod’s Request and Limit based on historical data CA, which automatically scales the number of Nodes based on usage This post focuses on the node scaling part. 1. The autoscaler Autoscaling Component autoscaler is a project maintained by the Kubernetes community.

Here a Windows node is used mainly as a Worker, while the Master control plane stays on Linux. 1. System Configuration 1.1 Kubernetes Control Plane Since version 1.14, Kubernetes has added production-grade support for Windows nodes. Because Microsoft’s official documentation mainly covers installing the flannel network plugin, it is recommended here that Kubernetes also use the flannel plugin.