Setup of Git repo during OSM installation for Continuous Deployment operation
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.
Description
This feature proposes the setup of an internal Git repository during OSM installation that will be used by a Continuous Deployment (CD) operator like FluxCD to run new operations (cluster management, deployment of PaaS, etc.) over public and private clouds.
New operations will be done in a declarative way through Kubernetes manifests, expresssing the desired state. They will be defined in a Git repository and the CD controller will monitor changes in the Git repository and will be responsible of monitoring and reconciling the deployed objects.
The specific Kubernetes manifests to be used for the new operations are out of the scope of this feature.
Demo or definition of done
OSM installation will come bundled with an internal Git repository configured to work with the Continuous Deployment operator. All tests in OSM must pass and should not be affected by the changes in the installation.