Scope of this issue is to define the specification for the Krateo operator and what we expect from its controller.
This operator will offload all the orchestration logic from the Krateo CLI which will not be dropped but will help to produce or inquiry Krateo resources in the Kubernetes cluster.
With the Krateo operator implementation we want to let Krateo be installed with a gitops approach and the related lifecycle management.
We want as well to provide an additional operator that can be added to https://operatorhub.io/, meaning that every OpenShift cluster will be able to use it. If another Kubernetes distribution is available, then there will be another - but consistent - version of the operator.
Scope of this issue is to define the specification for the Krateo operator and what we expect from its controller. This operator will offload all the orchestration logic from the Krateo CLI which will not be dropped but will help to produce or inquiry Krateo resources in the Kubernetes cluster. With the Krateo operator implementation we want to let Krateo be installed with a gitops approach and the related lifecycle management. We want as well to provide an additional operator that can be added to https://operatorhub.io/, meaning that every OpenShift cluster will be able to use it. If another Kubernetes distribution is available, then there will be another - but consistent - version of the operator.