/kind feature
Describe the solution you'd like
CAPC reconciles various resources in CloudStack, we want to see CAPC leverage and reconcile notion of a CAPC k8s cluster to a CKS (unmanaged) cluster.
The CKS cluster resource in CloudStack captures notion of a k8s cluster in CloudStack, and recently a feature improvement made it possible to have notion of unmanaged k8s cluster with apache/cloudstack#7515 with documentation at apache/cloudstack-documentation#315 and API support via go-sdk change apache/cloudstack-go#59. A PR proposed #250 which couldn't satisfy review from other stakeholders. With this issue, alternative options and approaches can be discussed or the previous PR reimagined.
As a CAPC user I would want the following:
- Ability to see my CAPC cluster show up as unmanaged CKS cluster in CloudStack (API and UI)
- Be able to see usage, of my CAPC cluster via CKS cluster (cpu, memory etc.)
- As MachineSets are added/removed, the related instances can be added removed in CKS 'unmanaged' cluster
- In large environment, esp a typical CI/CD use-cases, if as a user I lose/forget my CAPC admin cluster I should be able to manually delete the CAPC cluster resources (namely, VMs and networks)
- I should be able to do this as a user account type (note: a CloudStack role has a list of allowed/disallowed APIs, however, an account type control ability of an account type to do certain things such as acquire public IP of choice in a given shared/isolated/vpc network etc. needed typically for CAPC cluster)
- Prefer not to use another tool, than CAPC for reconciliation of a CAPC cluster to a CloudStack Kubernetes Service (CKS) cluster
Brief design doc: (to be expanded by @vishesh92)
/kind feature
Describe the solution you'd like
CAPC reconciles various resources in CloudStack, we want to see CAPC leverage and reconcile notion of a CAPC k8s cluster to a CKS (unmanaged) cluster.
The CKS cluster resource in CloudStack captures notion of a k8s cluster in CloudStack, and recently a feature improvement made it possible to have notion of unmanaged k8s cluster with apache/cloudstack#7515 with documentation at apache/cloudstack-documentation#315 and API support via go-sdk change apache/cloudstack-go#59. A PR proposed #250 which couldn't satisfy review from other stakeholders. With this issue, alternative options and approaches can be discussed or the previous PR reimagined.
As a CAPC user I would want the following:
Brief design doc: (to be expanded by @vishesh92)