kubelet: specify --containerd
flag to specify containerd socket path
#868
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number:
Partially addresses #867
Description of changes:
We changed the containerd socket path to be
/run/dockershim.sock
in #796. cAdvisor assumes the containerd socket to be located at/run/containerd/containerd.sock
.Pass
--containerd
to kubelet to specify containerd socket path so cAdvisor can make calls to containerd for gathering metric metadata information.Testing done:
Built bottlerocket image, ran in an EKS 1.15 cluster. Kubelet starts up fine, mark-successful-boot.service is OK. Node registers with the cluster successfully, pods run fine.
Most metrics now have metadata information, whereas before none of the metrics had any metadata information.
Note that some metrics are still missing metadata information, e.g. most filesystem related metrics have missing metadata information.
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.