Mirantis / Mirantis/cri-dockerd
how to pass the CNI plugin's CNI_ARGS via cri-dockerd
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 356
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 3
Description
Hi, there
as the title say, when use the local CNI plugin, like bridge or IPAM, the CNI doc said that we can use the CNI_ARGS to request a specific IP address from a subnet, that means we can fix the IP for the pod in the edge node which the net is isolated.
so, is there any way useing CNI local plugin bridge or IPAM to fix the IP via k8s -> cri-dockerd -> docker?
thx
ref: https://www.cni.dev/plugins/current/ipam/host-local/
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
Begin with the CNI_ARGS behavior described in the linked host-local documentation and compare it with the Kubernetes → cri-dockerd → Docker path described here. Done means establishing whether a fixed pod IP can be passed through that path, and if not, recording the missing capability or a concrete feature scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100