Overview over Cluster Settings

garloff commented 2 years ago

As a SCS KaaS developer, I want to have an overview over the settings that various cluster management solutions offer. https://scs.sovereignit.de/nextcloud/apps/files/?dir=/Sovereign%20Cloud%20Stack/Technology&fileid=5021

Definition of Ready:

garloff commented 2 years ago

Discussion 2022-05-23:

Avoid having too high entry-barriers and complexity just to have a base SCS compatibility
Focus on core!
Things that can easily be added by the customer afterwards should not be part of the base requirement.
Example: ingress: Requires load-balancer, which should be required. (Ingress should not be required.)
Trouble is that some things that can be done afterwards ARE cloud-provider (and/or node image) dependent

garloff commented 2 years ago

Node images discussion:

Upstream CAPI images exist (but are not meant for production)
Provider-independent images are very hard to do (hard to avoid provider-specific things)
So we would to define requirements to images rather than the images themselves
Still be useful to feed standard requirements upstream

Need discussion with upstream CAPI image folks.

garloff commented 2 years ago

Discussion on node-problem-detector:

Can be deployed as daemonset, so does not need to be integrated in node image
daemonset is under user control, so this should be preferred (over the systemd unit approach)
Requirement for node images would be that they don't break the daemonset way of deploying n-p-d

Trouble is that Node-problem-detector implementation depends on the exact OS (linux distribution) used in the node image.

fkr commented 1 year ago

This issue is marked for R3. Will this be scope of R4?