...
The table below provides an overview of the applications listed in the default catalogue. These can be installed on the cluster during manual provisioning or added to templated clusters at a later stage once provisioned. The applications are deployed in form of managed Helm charts with the option of customizing their values via the Dashboard UI before deployment.
| Application Name | Description | Home Page/Documentation | Notes |
|---|---|---|---|
| Ingress-Nginx Controller | Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer supporting HTTP and HTTPS protocols. | https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/ |
|
| External Secrets | External Secrets management for Kubernetes. | Only the External Secrets Operator is installed. The secret store (vault) is to be provided and configured by the users. | |
| Cert-Manager | A Kubernetes addon to automate the management and issuance of TLS certificates from various issuing sources. |
| |
| ExternalDNS | ExternalDNS synchronizes exposed Kubernetes Services and Ingresses with DNS providers. | The application is currently provided without a EWC-specific configuration. It's up to the users to configure the integration with the DNS system of their choice. | |
| GPU Operator | A customized NVIDIA GPU Operator Helm Chart preconfigured for the use of the Time-slicing GPU sharing feature on EWC machines. | https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/index.html | A EWC-specific configuration for time-slicing GPU sharing feature on Ubuntu worker nodes is provided. Other GPU sharing features are currently not supported in the EUMETSAT side of the EWC. Note: Only Ubuntu GPU nodes are currently available in the EUMETSAT side of the EWC. |
Application Deployment
In order to add an application from the catalogue to your cluster, select it during the manual cluster deployment, or add to the cluster later once it is deployed. The process as of Step 2 is the same in both cases.
...