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

cleangateway not works for multiple NIC #2640

Closed
Icarus9913 opened this issue Nov 22, 2023 · 0 comments · Fixed by #2618
Closed

cleangateway not works for multiple NIC #2640

Icarus9913 opened this issue Nov 22, 2023 · 0 comments · Fixed by #2618
Assignees
Labels

Comments

@Icarus9913
Copy link
Collaborator

Spiderpool Version

0.8.0

Bug Type

IPAM

Main CNI

/

What happened?

Once you use annotation "ipam.spidernet.io/ippools" to specify IPPools for multiple NICs, you can use the "cleangateway" property to specify whether this NIC allocation need default route with the IPPool's gateway.

But this field just works for the first NIC and it does not works for the second or latter NIC. For example, this following annotation not works

ipam.spidernet.io/ippools: |-
  [{
      "interface": "eth0",
      "ipv4": ["demo-v4-ippool1"],
      "ipv6": ["demo-v6-ippool1"],
      "cleangateway": false
   },{
      "interface": "net1",
      "ipv4": ["demo-v4-ippool2"],
      "ipv6": ["demo-v6-ippool2"],
      "cleangateway": true
  }]

What did you expect to happen?

cleangateway property works well

How to reproduce it (as minimally and precisely as possible)

/

Additional Context

No response

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

Successfully merging a pull request may close this issue.

2 participants