Deployed 5bd68f4c to develop in public with MkDocs 1.6.0 and mike 2.1.2

public/develop/architecture/CRIDGE/CRIDGEforDevelopers/index.html

@@ -2697,7 +2697,7 @@ These scenarios may include service bundles that involve multiple systems, such
 <p>OSL in general is responible for exposing service specifications  which are ready to be ordered and orchestrated, through tmforum Open APIs as defined in the OSL Service Spec Catalog. Usually for a service specification a corresponding (one or more) resource specification (resourceSpecificationReference) is registered in the OSL Resource Spec Catalog.</p>
 </blockquote>
 <p>The following image illustrates the approach.</p>
-<p><img src="img01.png" width=1024px></p>
+<p><a href=""><img alt="img01.png" src="../img01.png" /></a></p>
 <ol>
 <li>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</li>
 <li>Service Orders can be created for this service specification. The OSL Orchestrator (OSOM) will manage the lifecycle of the Service Order.</li>
@@ -2708,7 +2708,7 @@ These scenarios may include service bundles that involve multiple systems, such
 </ul>
 </li>
 </ol>
-<p><img src="img02.png" width=800px></p>
+<p><a href=""><img alt="img02.png" src="../img02.png" /></a></p>
 <p>The provided image illustrates the architecture and workflow of the CRIDGE service, showing how it interacts with other components within a Kubernetes (K8s) cluster. Here is an explanation of the key components and flow in the diagram:</p>
 <ul>
 <li>Other OSL Services: This box represents various OSL services such as Service Spec Catalogue, Resource Spec Catalogue, Service Inventory, Resource Inventory, and OSOM (OpenSlice Service Orchestration and Management).</li>
@@ -2749,7 +2749,7 @@ These scenarios may include service bundles that involve multiple systems, such
 </ul>
 <h1 id="handling-more-than-one-clusters">Handling more than one clusters</h1>
 <p>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:</p>
-<p><img src="img03.png" width=1024px></p>
+<p><a href=""><img alt="img03.png" src="../img03.png" /></a></p>
 <p>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. 
  - Each CRIDGE service has for example its own configuration to connect to target cluster
  - Each CRIDGE can be installed either in the managed cluster or at the remote clusters. Connectivity is handled via the service bus
@@ -2762,7 +2762,7 @@ These scenarios may include service bundles that involve multiple systems, such
 <p>CRDs and CRs can appear (disappear) or change status at any time in a cluster. OSL Resource Inventory need to be aware of these events.</p>
 </blockquote>
 <p>The sync process is found in the code and explained by the following picture:</p>
-<p><img src="img04.png" width=1024px></p>
+<p><a href=""><img alt="img04.png" src="../img04.png" /></a></p>
 <p>WatcherService is executed when the cridge service application starts (see onApplicationEvent). First things:</p>
 <ul>
 <li>KubernetesClientResource is a class that wraps fabric8’s KubernetesClient<ul>
@@ -2799,7 +2799,7 @@ These scenarios may include service bundles that involve multiple systems, such
 </li>
 </ul>
 <h1 id="deployment-of-a-new-cr-based-on-a-crd">Deployment of a new CR based on a CRD</h1>
-<p><img src="img05.png" width=1024px></p>
+<p><a href=""><img alt="img05.png" src="../img05.png" /></a></p>
 <ul>
 <li>A message arrives to deploy a CR<ul>
 <li>The call examines if this CRIDGE service can handle the request (based on context and masterURL)</li>