Helm chart
This is a summary of the Helm chart parameters that can be used to customise the SDP deployment. The current default values can be found in the chart’s values file.
Global
These are settings that affect the entire install, including sub-charts.
Parameter |
Description |
Default |
---|---|---|
|
Namespace for SDP dynamic deployments |
|
|
Name of data product PVC that is set as a global value to allow subcharts to access the same PVC |
|
|
Host address and port for the Tango Database |
|
Tango infrastructure
Parameters for the ska-tango-base subchart and Tango dsconfig. The ska-tango-base subchart must be enabled to support the Tango devices when running the SDP stand-alone.
Parameter |
Description |
Default |
---|---|---|
|
Enable the ska-tango-base subchart |
|
|
Enable the ITango console in the ska-tango-base subchart |
|
|
Tango dsconfig container image settings |
See values file |
SDP QA
Sub-chart for the SDP QA data API
Parameter |
Description |
Default |
---|---|---|
|
Enable the QA data API |
|
Taranta and TangoGQL
These two sub-charts need to be enabled together if one wants to access the Taranta Dashboard for SDP
Parameter |
Description |
Default |
---|---|---|
|
Enable the Taranta Dashboard |
|
|
Enable TangoGQL |
|
Kafka
When enabled, Apache Kafka is installed.
Parameter |
Description |
Default |
---|---|---|
|
Enable the Kafka deployment |
|
|
Maximum size of message in Bytes |
|
|
Maximum size of a request in Bytes that the socket server will accept |
|
|
Resource requests and limits for Kafka |
See values file |
|
Persist Kafka data to storage |
|
|
Zookeeper settings |
See values file |
|
The cluster’s domain |
|
Configuration database
The configuration database is implemented on top of etcd.
Parameter |
Description |
Default |
---|---|---|
|
etcd container image |
|
|
etcd container version |
See values file |
|
etcd container image pull policy |
|
|
Number of etcd server replicas |
|
|
Logging level for etcd |
|
|
Resource requests and limits for the pod |
|
|
Enable persistence of etcd database in persistent volume claim |
|
|
Size of persistent volume claim |
|
|
Storage class name for persistent volume claim |
|
|
Auto compaction retention for key-value store in hours |
|
|
Auto compaction mode |
|
|
Enable periodic etcd defragmentation |
|
|
Schedule in Cron format for etcd defragmentation |
|
|
Number of successful finished jobs to retain |
|
|
Maximum number of operations per transaction |
|
Console
The console provides a command-line interface to monitor and control the SDP by interacting with the configuration database.
Parameter |
Description |
Default |
---|---|---|
|
Enable the console |
|
|
Console container image |
|
|
Console container version |
See values file |
|
Console container image pull policy |
|
|
Resource requests and limits for the pod |
|
Processing controller
Parameter |
Description |
Default |
---|---|---|
|
Processing controller container image |
|
|
Processing controller container version |
See values file |
|
Processing controller container image pull policy |
|
|
Resource requests and limits for the pod |
|
|
Processing controller idle loop time (seconds) |
See values file |
|
Processing controller Kubernetes liveness probe configuration |
See values file |
Helm deployer
Parameter |
Description |
Default |
---|---|---|
|
Helm deployer container image |
|
|
Helm deployer container version |
See values file |
|
Helm deployer container image pull policy |
|
|
Resource requests and limits for the pod |
|
|
Prefix for Helm release names |
|
|
Prefix for Helm chart names |
|
|
Chart repository URL |
|
|
Chart repository refresh interval (in seconds) |
|
|
Maximum number of releases to list at once |
|
|
Helm deployer idle loop time (seconds) |
See values file |
|
Helm deployer Kubernetes liveness probe configuration |
See values file |
|
If
true then add credentials for helm deployer to list/get/watchthe network-attachment-definitions system CRD.
|
|
LMC (Tango devices)
Parameter |
Description |
Default |
---|---|---|
|
Enable the LMC. If set to |
|
|
LMC container image |
|
|
LMC container version |
See values file |
|
LMC container image pull policy |
|
|
Number of subarrays to deploy |
|
|
Telescope prefix for Tango device names (e.g. |
|
|
Use new-style Tango device names defined in ADR-9 |
|
|
Enable all Tango device commands to receive a transaction ID |
|
|
Enable strict validation of subarray command schemas |
|
|
LMC devices idle loop time (seconds) |
See values file |
|
LMC devices Kubernetes liveness probe configuration |
See values file |
|
Controller device settings |
See values file |
|
Subarray device settings |
See values file |
|
Timeout for AssignResources command (seconds) |
|
|
Timeout for Configure command (seconds) |
|
|
QueueConnector device settings |
See values file |
Data Persistent Volume Claim (PVC)
Configure the SDP to use an existing volume or create a new one, and configure the processing scripts to write the data to that volume. When creating new PVCs, one will be created in the control system namespace and the other in the processing namespace.
If the clone-pvc
and clone-pvc-namespace
values are set, then the PVCs
will be created as clones of an existing PVC in another namespace. This allows
the storage volume to be shared between namespaces. It depends on the
SKAO-specific shared volume infrastructure being available in the cluster.
Parameter |
Description |
Default |
---|---|---|
|
Name of data product PVC that is set as a global value to allow subcharts to access the same PVC |
|
|
Enable creation of PVCs |
|
|
Size of PVC |
|
|
Storage class name for PVC |
|
|
Name of PVC to clone |
Not set |
|
Namespace containing the PVC to clone |
Not set |
Processing scripts
Processing script definitions to be used by SDP. These map the script kind, name and version to a container image. By default the definitions are read from the scripts repository in GitLab at SDP installation time. A different URL may be specified. A schedule can be established to reload the definitions periodically. Alternatively a list of script definitions can be passed to the chart.
Parameter |
Description |
Default |
---|---|---|
|
URL from which to read the script definitions |
|
|
List of script definitions. If present, used instead of the URL. See the example below |
Not set |
|
The cronjob schedule
at which script definitions are re-loaded.
Only relevant when not using |
Not set |
Example of script definitions in a values file:
scripts:
definitions:
- type: realtime
id: test-realtime
version: 0.3.0
image: artefact.skao.int/ska-sdp-script-test-batch:0.3.0
- type: batch
id: test-batch
version: 0.3.0
image: artefact.skao.int/ska-sdp-script-test-realtime:0.3.0
Proxy settings
Proxy settings are applied to the components that retrieve configuration data via HTTPS: the script definitions and the Helm charts.
Parameter |
Description |
Default |
---|---|---|
|
Address of proxy server |
Not set |
|
List of addresses or subnets for which the proxy should not be used |
Not set |
Example of proxy settings in a values file:
proxy:
server: http://proxy.mydomain
noproxy:
- 192.168.0.1
- 192.168.0.2