Skip to content
This repository was archived by the owner on Mar 9, 2022. It is now read-only.

Support new CNI capabilities. #1243

Closed
Random-Liu opened this issue Aug 21, 2019 · 1 comment · Fixed by #1244
Closed

Support new CNI capabilities. #1243

Random-Liu opened this issue Aug 21, 2019 · 1 comment · Fixed by #1244
Milestone

Comments

@Random-Liu
Copy link
Member

There are several useful new capabilities we should support https://github.com/containernetworking/cni/blob/d19c2358a56d66cff6694e4f00f7c38c16d8182e/CONVENTIONS.md#well-known-capabilities:

  • ipRanges: We should pass the pod cidr down there;
  • dns: This is especially important for windows support.
@Random-Liu
Copy link
Member Author

ipRanges requires the cni plugin to provide pod cidr when creating pods.

However, kubelet only pass down the pod cidr once during node startup, after containerd restarts we'll lose the pod cidr.

The only solution is to checkpoint the cidr somewhere, which I prefer not to do unless necessary.

Dockershim doesn't have this problem, because it has the same lifecycle with kubelet. And after kubelet restarts it will send pod cidr to the container runtime again. kubernetes/kubernetes@5d9ec20

In conclusion, I prefer not supporting ipRanges which requires an extra checkpoint until we have to.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant