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

Can flannel set forceAddress parameters? #1850

Open
tanberBro opened this issue Dec 25, 2023 · 4 comments
Open

Can flannel set forceAddress parameters? #1850

tanberBro opened this issue Dec 25, 2023 · 4 comments

Comments

@tanberBro
Copy link

Expected Behavior

I want to add a forceAddress parameter to the parameter passed to bridge cni so that he can perform the following logic:
image

Current Behavior

My current configuration does not have forceAddress parameters. In some cases, the pod reported an error:
企业微信截图_06982571-b90e-4e0d-bbbc-e755fe21c8a8

Possible Solution

Set forceAddress parameters in flannel config.

Context

The reason why the pod reports an error is:
This node was originally a node in cluster 1, but now it has become a node in cluster 2, causing the subnet to change.

Your Environment

  • Flannel version: v0.20.2
  • Backend used (e.g. vxlan or udp): vxlan
  • Kubernetes version (if used): v1.24.10
  • Operating System and version: centos7
@tanberBro
Copy link
Author

@rbrtbnfgl

@rbrtbnfgl
Copy link
Contributor

do you cleaned the node when it joined the second cluster?

@tanberBro
Copy link
Author

tanberBro commented Jan 2, 2024

flannel configuration and bridge not cleaned up,

Need a separate cleaning?

@rbrtbnfgl

@rbrtbnfgl
Copy link
Contributor

yes Flannel is not cleaning older configuration like routes and bridge interface.

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

No branches or pull requests

2 participants