-
Notifications
You must be signed in to change notification settings - Fork 2
MEP-16 Firewall Support for Cluster API Provider #255
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
Conversation
Thanks for contributing a pull request to the metal-stack docs! A rendered preview of your changes will be available at: https://docs.metal-stack.io/previews/PR255/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well written.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super-nice to read this MEP. Thank you for incrementally improving Cluster API support!
We redesigned this evolution proposal and changed the approach of it to maximize compatibility between Gardener and Cluster API. Now there is more explanation on the existing concept and on Cluster API. While there are configuration examples for the Gardener and the CAPMS cases, the API isn't final and we did not create new charts. This is still in progress. |
Co-Authored-By: @Gerrit91
f4163ee
to
66c2f48
Compare
Updated to reflect the latest discussed changes. |
Description
Opens up the discussion around integrating firewalls to the scope of capms
References: