-
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
Implement Giant Swarm Kubernetes and Component Defaults within Cluster API #425
Comments
@puja108 do we need this issue still? |
I'm not sure if this is implemented. @alex-dabija @cornelius-keller @gawertm can you confirm wether this is done (most probably in form of the default configs we roll out with the cluster app)? |
The OS defaults are not implemented because we still use Ubuntu as our OS for all CAPI providers. The hardening we have on Vintage configured for Flatcar was not ported to Ubuntu. We might not ported the OS hardening to Ubuntu because our long-term plan, at least for now, is to have Flatcar as the OS. We might want to revisit this decision before we start working on Flatcar support. |
@pipo02mix is actually currently working on Automatic Upgrades . Within that Story he touched the Kubernetes and OS defaults, where to set them (cluster- chart), etc. this seems very much related. |
The OS default in this case means actual settings in the operating system. The upgrade story if I understood correctly, refers to the actual default OS image. |
oh yes correct. Upgrade referred to OS Image |
there's a bit of a confusion, the OS defaults are in the other ticket this ticket is about k8s defaults, which I think we have right? that's why I was asking for confirmation. |
so again, do we have all Kubernetes component settings that we had set for best practice and other (I hope good) reasons in k8scloudconfig also in the cluster apps set? @alex-dabija @gawertm @cornelius-keller cc @Rotfuks If that's the case I'd like to close this ticket |
For CAPA & CAPG we have the same settings for the Kubernetes components (API, scheduler, controller manger) as we do on Vintage, but we don't have any of the OS defaults in place because we still use Ubuntu instead of Flatcar. |
cool, I suppose we are doing the same for VCD right? cc @vxav for OS we have a separate ticket. |
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 the 2nd issue, but are not present for this one.
The text was updated successfully, but these errors were encountered: