Deployed 574a018e to develop in public with MkDocs 1.6.1 and mike 2.1.3

</ul>

</li>

<li><strong>Helm:</strong> For managing the deployment of OpenSlice.</li>

<li><strong>Ingress Controller:</strong> Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. Traffic routing is controlled by rules defined on the Ingress resource. An Ingress may be configured to give Services externally-reachable URLs, load balance traffic, terminate SSL / TLS, and offer name-based virtual hosting. An Ingress controller is responsible for fulfilling the Ingress, usually with a load balancer, though it may also configure your edge router or additional frontends to help handle the traffic. You must have an Ingress controller to satisfy an Ingress.<ul>

<li>

<p><strong>Ingress Controller:</strong> Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. Traffic routing is controlled by rules defined on the Ingress resource. An Ingress may be configured to give Services externally-reachable URLs, load balance traffic, terminate SSL / TLS, and offer name-based virtual hosting. An Ingress controller is responsible for fulfilling the Ingress, usually with a load balancer, though it may also configure your edge router or additional frontends to help handle the traffic. You must have an Ingress controller to satisfy an Ingress.</p>

<ul>

<li><strong>Nginx Ingress Controller (Kubernetes Community Edition):</strong>  The ingress resource is configured to use an Nginx type ingress controller. </li>

<li>If you need to expose the message bus service (Artemis), which communicates using the TCP protocol, you must use version <strong>&gt;= 1.9.13</strong> of the Nginx Ingress Controller (a prerequisite for <a href="#management-of-multiple-kubernetes-clusters">managing multiple kubernetes clusters</a>). This version or higher includes the required functionality to handle TCP services. Otherwise, earlier versions may suffice depending on your configuration.</li>

<li>To install or upgrade to the required version, run the following command:

  <code>bash

  helm upgrade nginx-ingress ingress-nginx/ingress-nginx --namespace ingress \

  --set tcp.61616="&lt;openslice-namespace&gt;/&lt;openslice-helm-release-name&gt;-artemis:61616"</code>

  Replace <code>&lt;helm-release-name&gt;</code> with the name of your OpenSlice Helm release.</li>

<li>More details regarding the Nginx Ingress Controller (Kubernetes Community Edition) can be found <a href="https://kubernetes.github.io/ingress-nginx/deploy/">here</a>.</li>

<li><strong>Other Ingress Controller:</strong>  For non-Nginx ingress controllers, modify <code>[repo-root]/kubernetes/helm/openslice/templates/openslice-ingress.yaml</code> to meet your controller’s requirements.</li>

<li>To install or upgrade to the required version, run the following command:</li>

</ul>

<p><code>bash

  helm upgrade nginx-ingress ingress-nginx/ingress-nginx --namespace ingress \

  --set tcp.61616="&lt;openslice-namespace&gt;/&lt;openslice-helm-release-name&gt;-artemis:61616"</code></p>

<p>Replace <code>&lt;helm-release-name&gt;</code> with the name of your OpenSlice Helm release.

  * More details regarding the Nginx Ingress Controller (Kubernetes Community Edition) can be found <a href="https://kubernetes.github.io/ingress-nginx/deploy/">here</a>.

* <strong>Other Ingress Controller:</strong>  For non-Nginx ingress controllers, modify <code>[repo-root]/kubernetes/helm/openslice/templates/openslice-ingress.yaml</code> to meet your controller’s requirements.</p>

</li>

</ul>

<h3 id="exposure">Exposure</h3>

<li>

<p><strong>Passing the Kubeconfig File Using Helm (<code>--set-file</code>)</strong>:</p>

<ul>

<li>If you do not wish to manually copy the file, you can pass it directly during the Helm installation using the <code>--set-file</code> option:

 <code>bash

 helm install cridge-release . --set-file kubeconfig.raw=path/to/kubeconfig.yaml</code></li>

<li>If you do not wish to manually copy the file, you can pass it directly during the Helm installation using the <code>--set-file</code> option:</li>

</ul>

<p><code>bash

helm install cridge-release . --set-file kubeconfig.raw=path/to/kubeconfig.yaml</code></p>

<ul>

<li>This method reads the specified kubeconfig file and mounts it into the CRIDGE container during deployment.</li>

</ul>

</li>

<li>

<p><strong>Passing a Base64-Encoded Kubeconfig Using Helm (<code>--set</code>)</strong>:</p>

<ul>

<li>Alternatively, you can pass the kubeconfig as a base64-encoded string:

 <code>bash

 helm install cridge-release . --set kubeconfig.base64="$(base64 path/to/kubeconfig.yaml)"</code></li>

<li>Alternatively, you can pass the kubeconfig as a base64-encoded string:</li>

</ul>

<p><code>bash

helm install cridge-release . --set kubeconfig.base64="$(base64 path/to/kubeconfig.yaml)"</code></p>

<ul>

<li>This method encodes the kubeconfig content and passes it directly to the CRIDGE container.</li>

</ul>

</li>