Helm Overview
This is the documentation for the Signal Metrics Helm Chart.
The helm chart has quite a few different options, and can used in multiple use cases, on this page you will find both the most common use cases as well as all the options.
Basic Installation
A basic setup has all options enabled, and will send periodic data to the frontend.
helm install qa-api ska/ska-sdp-qa \
--namespace <deploy-namespace> \
--set generator.enabled=true \
--set "generator.command={bash,/generator-helper.sh,plasma}"
SDP Usage
In the SDP installation, we have other settings enabled and disabled. To be able to install the Signal Helm chart in the same way as in SDP you would run the following:
helm install qa-api ska/ska-sdp-qa \
--namespace <deploy-namespace> \
--set api.workerCount=2 \
--set kafka.enabled=false \
--set api.sdp_config.host=ska-sdp-etcd \
--set api.sdp_config.port=2379 \
--set config.kafka.overrideUrl=ska-sdp-kafka:9092
Warning
An important note is that the API needs to know about the ETCD database. And as such the above sdp_config
values are very important to have set correctly.
All Configuration Options
Currently the full list of configuration options are:
Value |
Default |
Comment |
---|---|---|
|
|
The name of the Processing Namespace, for monitoring URLs |
|
|
Whether the Ingress should be enabled |
|
|
What the prefix for the path should be |
|
|
Whether the namespace should be added to the ingress prefix |
|
|
If the generator should be enabled (for testing) |
|
|
The container Docker link |
|
|
The version of the Generator to use |
|
|
The pull policy of the generator |
|
|
What command the generator should run by default. |
|
|
The requested minimum CPU usage of the generator |
|
|
The requested minimum memory usage of the generator |
|
|
The maximum CPU usage of the generator |
|
|
The maximum memory usage of the generator |
|
|
What file should we use for the sample data sending |
|
|
What is the name of the MS file after unzipping |
|
|
If the API is enabled |
|
|
The docker link of the API container |
|
|
The API version to use |
|
|
The pull policy of the API container |
|
|
The amount of processes to start up for the API |
|
|
Should profiling be enabled |
|
|
What type of data should the websocket use? |
|
|
How long we should keep data after the last update in Redis |
|
|
How wide should we generate thumbnails |
|
|
How high should we generate thumbnails |
|
|
The hostname for the SKA SDP Config DB |
|
|
The port for the SKA SDP Config DB |
|
|
The ID of the Grafana Dasboard to link to |
|
|
The host link for the Grafana monitoring server. |
|
|
The hostname of the Kibana monitoring server. |
|
|
The requested minimum CPU usage |
|
|
The requested minimum memory usage |
|
|
The maximum CPU usage |
|
|
The maximum memory usage |
|
|
If the display is enabled |
|
|
The docker link for the Display container |
|
|
The version of the Display image to use |
|
|
The pull policy for the Display image. |
|
|
How often to pull the statistics |
|
|
If we should skip the preflight check |
|
|
If the URLs should be manually overridden |
|
|
The URL for the API if overridden. |
|
|
The URL for the websocket if overriden |
|
|
Is the Kafka URL getting overriden |
|
|
The new URL for Kafka |
|
|
Is the redis URL getting overridden |
|
|
The new URL for redis |
|
|
Is the Kafka system enabled |
|
|
What should the name be of the Kafka instance |
|
|
What is the maximum message size allowed |
|
|
What is the maximum payload to be sent to Kafka |
|
|
Should kafka have persistence |
|
|
What should zookeepers full name be |
|
|
Should zookeeper have persistence |
|
|
Should redis be enabled |
|
|
What the full name should be of redis |
|
|
Which architecture should be used |
|
|
Should auth be enabled |
|
|
Should we use persistence |
|
|
What the requested minimum CPU usage be |
|
|
What the requested minimum memory usage be |
|
|
What the maximum CPU usage be |
|
|
What the maximum memory usage be |