***Nginx Ingress Controller (Kubernetes Community Edition):** The ingress resource is configured to use an Nginx type ingress controller.
***Nginx Ingress Controller (Kubernetes Community Edition):** The ingress resource is configured to use an Nginx type ingress controller.
* If you need to expose the message bus service (Artemis), which communicates using the TCP protocol, you must use version **>= 1.9.13** of the Nginx Ingress Controller (a prerequisite for [managing multiple kubernetes clusters](#management-of-multiple-kubernetes-clusters)). This version or higher includes the required functionality to handle TCP services. Otherwise, earlier versions may suffice depending on your configuration.
* If you need to expose the message bus service (Artemis), which communicates using the TCP protocol, you must use version **>= 1.9.13** of the Nginx Ingress Controller (a prerequisite for [managing multiple kubernetes clusters](#management-of-multiple-kubernetes-clusters)). This version or higher includes the required functionality to handle TCP services. Otherwise, earlier versions may suffice depending on your configuration.
* To install or upgrade to the required version, run the following command:
* To install or upgrade to the required version, run the following command:
Replace `<helm-release-name>` with the name of your OpenSlice Helm release.
Replace `<helm-release-name>` with the name of your OpenSlice Helm release.
* More details regarding the Nginx Ingress Controller (Kubernetes Community Edition) can be found [here](https://kubernetes.github.io/ingress-nginx/deploy/).
* More details regarding the Nginx Ingress Controller (Kubernetes Community Edition) can be found [here](https://kubernetes.github.io/ingress-nginx/deploy/).
* **Other Ingress Controller:** For non-Nginx ingress controllers, modify `[repo-root]/kubernetes/helm/openslice/templates/openslice-ingress.yaml` to meet your controller’s requirements.
* **Other Ingress Controller:** For non-Nginx ingress controllers, modify `[repo-root]/kubernetes/helm/openslice/templates/openslice-ingress.yaml` to meet your controller’s requirements.
@@ -201,16 +203,20 @@ Similarly, to configure CRIDGE, there are three different ways to provide this k
2.**Passing the Kubeconfig File Using Helm (`--set-file`)**:
2.**Passing the Kubeconfig File Using Helm (`--set-file`)**:
- If you do not wish to manually copy the file, you can pass it directly during the Helm installation using the `--set-file` option:
- If you do not wish to manually copy the file, you can pass it directly during the Helm installation using the `--set-file` option:
- This method encodes the kubeconfig content and passes it directly to the CRIDGE container.
- This method encodes the kubeconfig content and passes it directly to the CRIDGE container.
> **Note:** Regardless of the method you choose, if you're using a non-standard kubeconfig file name, make sure to adjust the references or rename the file as needed.
> **Note:** Regardless of the method you choose, if you're using a non-standard kubeconfig file name, make sure to adjust the references or rename the file as needed.