Mirantis / Mirantis/cri-dockerd
[Question] Support for new functionality after dockershim
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 356
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 3
Description
In K8S 1.25 cgroupv2 ( https://github.com/kubernetes/enhancements/issues/2254 ) is enabled, in containerD 1.7 ( https://github.com/containerd/containerd/blob/main/docs/NRI.md ) there is support for Node Resource Interface, and k8s 1.27 adds support for memory QoS ( https://github.com/kubernetes/enhancements/issues/2570 ) . Using cri-dockerd will it be possible to use these functionalities?
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
Review cri-dockerd's compatibility with Kubernetes 1.25 cgroupv2, containerd 1.7's Node Resource Interface, and Kubernetes 1.27 memory QoS using the linked enhancement and NRI documents. Determine whether these capabilities can be supported through cri-dockerd; done requires a concrete compatibility decision and defined implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100