Workflow for cloud-native operations in OSM following Gitops model

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:

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 implementation of a new workflow for cloud-native operations in OSM based on a Kubernetes operator. The workflow will include all the required transformations to obtain the desired Kubernetes objects for a given operation. The workflow will follow a Gitops model, and will include all the interactions with the Git repository to push the required changes for that given operation, so that it is possible to track the changes applied for a specific operation.

The workflow and transformations will be modelled independently from the specific Kubernetes objects, so that the workflow engine will run always the same workflow with the same steps.

Demo or definition of done

OSM installation will come with a Kubernetes operator to manage new workflows. All existing tests in OSM must pass and should not be affected by the additions. In addition, an NBI operation using that workflow should exist and must be part of one of the E2E Robot tests, which should pass.