I'm a bit curious about what happens to non-ephemeral things that normally live in /var/lib/kubelet. Kubelet has -root-dir and -log-dir, after digging through the code seems like root-dir maps to the desired cadvisor FsStats: (and similar) Your node can have as many other filesystems, not used for Kubernetes, as you like. The first filesystem does not hold any image layers or writeable layers. The kubelet to place container image layers and writeable layers is on this second filesystem. In this configuration, the directory where you tell You also use a separate filesystem, backed by a different logical storage device. The kubelet also writes node-level container logs into the first filesystem, and treats these similarly to ephemeral local storage. You can use this filesystem for other data (for example: system logs not related to Kubernetes) it can even be the root filesystem. You have a filesystem on the node that you're using for ephemeral data that comes from running Pods: logs, and emptyDir volumes. This bit from the k8s docs explains the implications of splitting the two (emphasis mine): So we end up with /var/lib/kubelet + /var/log. ![]() ![]() Size of cluster (how many worker nodes are in the cluster?) 13ĪKS seems to currently uses the first configuration, where root dir contains both "ephemeral storage" and other files.Kubernetes version (use kubectl version): 1.12.6.I'm not certain how where the ephemeral storage is mounted on a node or how much is allocated to it, but presumably just deploy an AKS cluster with a temp disk larger than 32 GiB How to reproduce it (as minimally and precisely as possible): Since this class of VM has 128GiB of temp disk, I would expect the ephemeral storage to be mounted on that scratch disk and have roughly that much capacity
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |