-
Notifications
You must be signed in to change notification settings - Fork 0
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
Giant Swarm OS Defaults within Cluster API #426
Comments
@puja108 do we need this issue still? |
Yes, we are still using Ubuntu and need to move our existing OS hardening once we have moved to Flatcar with the CAPI providers. |
just adding an aka and/or pre-req for this issue: Flatcar support in all providers. cc @stone-z had some relevant comments on Slack about the priority of this, as all our hardening is done for Flatcar and Ubuntu as base OS for CAPI is creating a lot of overwork like in giantswarm/node-exporter-app#172 |
checking for CAPVCD in: https://github.com/giantswarm/giantswarm/issues/25295 |
Flatcar support for CAPZ was merged this week, so it's also supported. |
Separate epic for the work that needs to be done for CAPA. |
I removed CAPG from the list. |
The harmonisation of OS Images over all providers will be done in the scope of #2544 |
User Story: As a customer, I want to be able to keep relying on the sensible defaults (for security, reliability, and performance) that Giant Swarm currently provides.
The above user story is split into two issues:
The split is based on technical challenges upstream that are currently blocking this issue, but are not present for the other one.
Providers
The text was updated successfully, but these errors were encountered: