Kubernetes SW units deployable over Kubernetes clusters
Proposers
- Gerardo García (Telefónica)
- Francisco Javier Ramón (Telefónica)
- Jayaprakash G (Tata Elxsi)
- Utkarsh Mishra (Tata Elxsi)
- Deepika E (Tata Elxsi)
- Sandhya J. S (Tata Elxsi)
- Priyadharshini S (Tata Elxsi)
- Shahithya Y (Tata Elxsi)
- Shrinithi R (Tata Elxsi)
- Ramesh Ramanathan (Tata Elxsi)
Reference
This feature is related to the long-term initiative presented in previous meetings:
- https://docbox.etsi.org/OSG/OSM/05-CONTRIBUTIONS/2023//OSM(23)000105_Telef_nica_s_Initiative_for_OSM_LTV.pptx
- https://docbox.etsi.org/OSG/OSM/05-CONTRIBUTIONS/2023//OSM(23)000081_Telef_nica_s_Initiative_proposal_for_Long_Term_View.pptx
The main purpose of the initiative is to use well known CRDs for new southbound operations (K8s clusters, PaaS/IaaS components, serverless workflows, Cluster API), relying on existing open source solutions such as Crossplane, FluxCD, ArgoCD, etc. These south-bound operations will be properly modeled and abstracted by OSM, which will provide a convenient user-facing modelling, in order to offer new use cases such as a complete cluster management from OSM and the support of PaaS-based deployment units.
Description
This feature proposes the creation of a new first class citizen in OSM named Kubernetes SW Units (KSU) to model individual SW components deployable over Kubernetes for the purpose of complementing the Kubernetes clusters with infra-related functionality (e.g. service mesh, monitoring, policy manager, certificate manager, etc.).
As first class citizens in OSM, CRUD operations (Create, Read, Update, Delete) could be done on them. As a general rule, in principle deletion shouldn't be allowed if other first class citizens are using them.
Demo or definition of done
A new Robot test will be created or updated to test the CRUD operations over KSUs using the osmclient.