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

Implement Giant Swarm Kubernetes and Component Defaults within Cluster API #425

Closed
puja108 opened this issue Aug 19, 2021 · 10 comments
Closed
Labels
area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service epic/capi team/rocket Team Rocket topic/capi

Comments

@puja108
Copy link
Member

puja108 commented Aug 19, 2021

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:

  1. Sensible defaults pertaining to Kubernetes and other user-space components Giant Swarm manages. (this issue)
  2. Sensible defaults pertaining to Operating System underlying the above-mentioned software Giant Swarm OS Defaults within Cluster API #426

The split is based on technical challenges upstream that are currently blocking the 2nd issue, but are not present for this one.

@puja108 puja108 added area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service epic/capi team/ludacris topic/capi labels Aug 19, 2021
@alex-dabija alex-dabija added team/phoenix Team Phoenix team/rocket Team Rocket labels Feb 10, 2022
@teemow teemow added this to Roadmap May 10, 2022
@teemow teemow moved this to Mid Term (3-6 months) in Roadmap May 10, 2022
@teemow
Copy link
Member

teemow commented Nov 11, 2022

@puja108 do we need this issue still?

@puja108
Copy link
Member Author

puja108 commented Nov 15, 2022

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)?

@alex-dabija
Copy link

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.

@gawertm
Copy link

gawertm commented Nov 16, 2022

@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.
see https://github.com/giantswarm/giantswarm/issues/23341

@alex-dabija
Copy link

@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. see giantswarm/giantswarm#23341

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.

@gawertm
Copy link

gawertm commented Nov 17, 2022

oh yes correct. Upgrade referred to OS Image

@puja108
Copy link
Member Author

puja108 commented Nov 17, 2022

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.

@puja108
Copy link
Member Author

puja108 commented Jan 5, 2023

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

@alex-dabija
Copy link

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.

@puja108
Copy link
Member Author

puja108 commented Jan 5, 2023

cool, I suppose we are doing the same for VCD right? cc @vxav

for OS we have a separate ticket.

@puja108 puja108 closed this as completed Jan 24, 2023
@github-project-automation github-project-automation bot moved this from Mid Term (3-6 months) to Released in Roadmap Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service epic/capi team/rocket Team Rocket topic/capi
Projects
Archived in project
Development

No branches or pull requests

4 participants