Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

not absolutely compatible with calico #38

Closed
luckymrwang opened this issue May 31, 2022 · 1 comment · Fixed by #52
Closed

not absolutely compatible with calico #38

luckymrwang opened this issue May 31, 2022 · 1 comment · Fixed by #52
Labels
bug Something isn't working enhancement New feature or request

Comments

@luckymrwang
Copy link
Member

luckymrwang commented May 31, 2022

On cluster deployed with calico as the network plugin, the podCIDR is assigned by ippool as blockCIDR. Every node is bound to blockaffinity whose CIDR is different from node.spec.podCIDR. So IPsec's policy added by node.spec.podCIDR is not right.

@luckymrwang luckymrwang changed the title not absolutely compatible with calico not absolutely compatible with calico CNI May 31, 2022
@luckymrwang luckymrwang changed the title not absolutely compatible with calico CNI not absolutely compatible with calico May 31, 2022
@njucjc njucjc added the bug Something isn't working label Jun 1, 2022
@njucjc
Copy link
Member

njucjc commented Jun 1, 2022

you are right, node.spec.pocCIDR is different from calico's blockCIDR since calico v3.6.
refer to #2592 #637
@BSWANG @DrmagicE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants