METRICO Documentation (fix for #14)

The following image illustrates the approach.

The following image illustrates the approach.

![img01.png](img01.png)

![img01.png](./images/cridge/img01.png)

1. A CRD in a cluster will be mapped in TMF model as a Resource specification and therefore can be exposed as a service specification in a catalog

1. A CRD in a cluster will be mapped in TMF model as a Resource specification and therefore can be exposed as a service specification in a catalog

2. Service Orders can be created for this service specification. The OSL Orchestrator (OSOM) will manage the lifecycle of the Service Order.

2. Service Orders can be created for this service specification. The OSL Orchestrator (OSOM) will manage the lifecycle of the Service Order.

![img02.png](img02.png)

![img02.png](./images/cridge/img02.png)

A CRIDGE service is usually responsible for managing one cluster. In the following diagram we show how it can be used for managing multiple clusters:

A CRIDGE service is usually responsible for managing one cluster. In the following diagram we show how it can be used for managing multiple clusters:

![img03.png](img03.png)

![img03.png](./images/cridge/img03.png)

We assume that there is an OSL Management cluster that OSL is installed. CRIDGE is also installed there if we would like to manage resources in the same management cluster. 

We assume that there is an OSL Management cluster that OSL is installed. CRIDGE is also installed there if we would like to manage resources in the same management cluster. 

The implemented synchronization process is explained by the following diagram:

The implemented synchronization process is explained by the following diagram:

![img04.png](img04.png)

![img04.png](./images/cridge/img04.png)

 WatcherService is executed when the CRIDGE service application starts (see onApplicationEvent). Specifically:

 WatcherService is executed when the CRIDGE service application starts (see onApplicationEvent). Specifically:

## Exposure of CRDs as Service Specifications 

## Exposure of CRDs as Service Specifications 

See [Exposing Kubernetes Resources](../../service_design/kubernetes/exposing_kubernetes_resources.md) section for ways to design services around CRDs.

See [Exposing Kubernetes Resources](../service_design/kubernetes/exposing_kubernetes_resources.md) section for ways to design services around CRDs.

## Service Orchestration and CRDs/CRs

## Service Orchestration and CRDs/CRs

The implemented process to deploy a CR is explained by the following diagram:

The implemented process to deploy a CR is explained by the following diagram:

![img05.png](img05.png)

![img05.png](./images/cridge/img05.png)

- A message arrives to deploy a CR

- A message arrives to deploy a CR

	- The call examines if this CRIDGE service can handle the request (based on context and masterURL)

	- The call examines if this CRIDGE service can handle the request (based on context and masterURL)

## Probe further

## Probe further

- See examples of exposing Kubernetes Operators as a Service via OpenSlice:

See examples of exposing Kubernetes Operators as a Service via OpenSlice:

    - [Offering "Calculator as a Service"](../../service_design/examples/calculator_crd_aas/calculator_crd_aas.md)

    - [Offering "Helm installation as a Service" (Jenkins example)](../../service_design/examples/jenkins_helm_install_aas/jenkins_helm_install_aas.md)

- [Offering "Calculator as a Service"](../service_design/examples/calculator_crd_aas/calculator_crd_aas.md)

- [Offering "Helm installation as a Service" (Jenkins example)](../service_design/examples/jenkins_helm_install_aas/jenkins_helm_install_aas.md)