Mirantis / Mirantis/cri-dockerd
should cri-dockerd be responsible for the misconfiguration of cgroup-driver between kubelet and dockerd
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 356
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 3
Description
kubelet works normally with different cgroup-driver configuration with docker container runtime(via cri-dockerd).
and should cri-dockerd checks the cgroupDriver misconfiguration between kubelet and dockerd?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how cri-dockerd, kubelet, and dockerd handle cgroup-driver settings, then establish the expected behavior for a mismatch and define a testable outcome for detection or reporting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100