Mirantis / Mirantis/cri-dockerd
set ipv6-dual-stack true as default?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 356
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 3
Description
when i plan to setup dual stack k8s cluster, i use calico as network plugin, the pod's annotation get calico ipv4 and ipv6, but {status.podIPs} can't find any ipv6 address,After my troubleshooting, it was found that cri-dockerd did not set the ipv6-dual-stack flag to true.Is there a way to find that this cluster is a dual-stack cluster and then automatically set it up?
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
Start by tracing how cri-dockerd handles the ipv6-dual-stack flag and reproduce the reported behavior in a dual-stack Kubernetes cluster using Calico. Determine how cluster dual-stack status could be identified and define completion as IPv6 addresses appearing in pod status without manual flag configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100