Deployment Guide
The SKA Permissions API is built for continuous operation within a Kubernetes cluster. It functions as a service that enables access permissions services required by users authenticated by MS Entra.
Helm chart configuration options
This section details the configuration options available when deploying the SKA Permissions API in Kubernetes using Helm.
Ingress:
Value |
Default |
Comment |
---|---|---|
|
|
Whether the Ingress should be enabled. |
|
|
Whether the namespace should be added to the ingress prefix. |
|
|
The domain name where the application will be hosted. Used for MS Entra redirect URI. |
Permissions API:
Value |
Default |
Comment |
---|---|---|
|
|
If the ska-permissions-api should be enabled. |
|
|
The image pull policy of the ska-permissions-api. |
|
|
The link to the artefact repository |
|
|
The version of the ska-permissions-api to use. |
|
|
What the prefix for the ska-permissions-api path should be. |
|
|
Enables the deployment to retrieve WEB API registration details from the SKAO vault. |
|
|
Path to the secrets in the vault. |
|
|
Placeholder env variable for MS Entra application registration client ID. |
|
|
Placeholder env variable for MS Entra application registration tenant ID. |
|
|
The amount of time between refreshing the data. |
|
|
The base engine in which the secrets are stored. |
|
|
The requested minimum CPU usage of the api. |
|
|
The requested minimum memory usage of the api. |
|
|
The maximum CPU usage of the api. |
|
|
The maximum memory usage of the api. |