K8s Cluster Management via common API provided by CSP's

[o-otte]

As a user of SCS (Service Provider and/or Enduser), I want a standardized way of deploying container infrastructure so that Containers can be set up in an easy and predictable way.

For this, a Central API should be implemented that acts as a user interface for managing the Infrastructure. This API should be build as a K8s API running on a Management Cluster.

The focus should be CaaS/KaaS/PaaS and not IaaS, for now.

The Responsibilities of Service Provider (Operator) and Users (DevOps Team) need to be defined.

The Provider should provide a Cluster-API endpoint as a standard service.

Open Question: Should the management cluster / central API be per tenant or global (multi-tenant (e.g. via Namespaces in K8s of Cluster-API))

Definition of Ready:

• User Story is small enough to be finished within one sprint
• User Story is clear and understood by the whole team
• Acceptance criteria are defined
• Acceptance criteria are clear and understood by the whole team

Definition of Done:

• All acceptance criteria are met
• Changes have been reviewed
• CI tests have run successfully
• Documentation has been updated
• Release Notes have been updated

[joshmue]

Open Question: Should the management cluster / central API be per tenant or global (multi-tenant (e.g. via Namespaces in K8s of Cluster-API))

To elaborate on that: In order to provide strong multi tenancy, we may...

• use a full, yet stripped down node-less K8s control plane for each tenant (possibly using e. g. k0s)
  • disable unused API's whether possible
  • statically run e. g. CAPI controllers alogside
• (later) embrace kcp's (experimental) concept of logical clusters reducing resource consumption

[jschoone]

Hi @o-otte, I will close and archive this as we now follow the idea of #321, which meets almost all of the goals of this issue. We have the concepts of logical clusters on our radar and will use parts of this asap.
What doesn't mean the idea of an SCS API is discarded, imho we should still follow this but need to refine how to.

[jschoone]

Reopen as I probably misunderstood the point of this issue. Please excuse me if this was the case @o-otte and @joshmue
Since the issue is still old and wasn't touched long time I'd keep the needs refinement label.
Can possibly be combined with #326

[joshmue]

Thanks for reopening. I tried to explain the potential differences in #339.