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

fix: always update firewall rules (kubespan) #8538

Merged
merged 1 commit into from
Apr 3, 2024

Conversation

smira
Copy link
Member

@smira smira commented Apr 3, 2024

Fixes #8498

Before KubeSpan was reimplemented to use resources for firewall rules, the update was happening always, but it got moved to a wrong section of the controller which gets executed on resource updates, but ignores updates of the peer statuses.

@smira smira added this to the v1.7 milestone Apr 3, 2024
Copy link
Member

@utkuozdemir utkuozdemir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🆒

Fixes siderolabs#8498

Before KubeSpan was reimplemented to use resources for firewall rules,
the update was happening always, but it got moved to a wrong section of
the controller which gets executed on resource updates, but ignores
updates of the peer statuses.

Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
@smira
Copy link
Member Author

smira commented Apr 3, 2024

/m

@talos-bot talos-bot merged commit e7d8041 into siderolabs:main Apr 3, 2024
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Proposed
Development

Successfully merging this pull request may close these issues.

NfTables chain does not get updated with latest KubeSpan peer when allowDownPeerBypass: true
4 participants