Skip to content
Snippets Groups Projects
Select Git revision
  • 77a14519675c0e000ae34c43e2a059af32d9210c
  • main default protected
  • v0.10
  • rework-examples
  • otel-demo-dynatrace-example
  • support-empty-query-response
  • java-operator-sdk
  • rework-state-handling
  • quarkus-36
  • bump-kotlinlogging-to-5.0.2
  • use-internal-registry protected
  • v0.9 protected
  • kafka-nodeport-config-windows
  • v0.8 protected
  • test-k3d protected
  • simpleuc4 protected
  • reduce-code-duplication
  • test-coverage
  • code-cleanup
  • cleanup-commit-interval protected
  • delete-action-for-other-namespace
  • v0.10.0 protected
  • v0.9.0 protected
  • v0.8.6 protected
  • v0.8.5 protected
  • v0.8.4 protected
  • v0.8.3 protected
  • v0.8.2 protected
  • v0.8.1 protected
  • v0.8.0 protected
  • v0.7.0 protected
  • v0.5.2 protected
  • v0.6.4 protected
  • v0.6.3 protected
  • v0.6.2 protected
  • v0.6.1 protected
  • v0.6.0 protected
  • v0.5.1 protected
  • v0.5.0 protected
  • v0.4.0 protected
  • v0.3.0 protected
41 results

helm

Theodolite Helm Chart

Installation

The Theodolite Helm chart with all its dependencies can be installed via:

helm dependencies update .
helm install theodolite .

Additionally, a PersistentVolumeClaim with the name theodolite-pv-claim needs to be created or the results volume can be disabled as done with the minimal configuration, described below.

Customize Installation

As usual, the installation with Helm can be configured by passing a values YAML file:

helm install theodolite . -f <your-config.yaml>

We provide a minimal configuration, especially suited for development environments, with the preconfigs/minimal.yaml file.

Per default, Helm installs the Theodolite CRDs used for the operator. If Theodolite will not be used as operator or if the CRDs are already installed, you can skip their installation by adding the flag --skip-crds.

Test Installation

Test the installation with:

helm test theodolite

Our test files are located here. Many subcharts have their own tests, which are also executed. Please note: If a test fails, Helm will stop testing.

Uninstall this Chart

The Theodolite Helm can easily be removed with:

helm uninstall theodolite

Helm does not remove any CRDs created by this chart. You can remove them manually with:

# CRDs from Theodolite
kubectl delete crd executions.theodolite.com
kubectl delete crd benchmarks.theodolite.com
# CRDs from Prometheus operator (see https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack#uninstall-chart)
kubectl delete crd alertmanagerconfigs.monitoring.coreos.com
kubectl delete crd alertmanagers.monitoring.coreos.com
kubectl delete crd podmonitors.monitoring.coreos.com
kubectl delete crd probes.monitoring.coreos.com
kubectl delete crd prometheuses.monitoring.coreos.com
kubectl delete crd prometheusrules.monitoring.coreos.com
kubectl delete crd servicemonitors.monitoring.coreos.com
kubectl delete crd thanosrulers.monitoring.coreos.com

Development

Dependencies

The following 3rd party charts are used by Theodolite:

  • Kube Prometheus Stack (to install the Prometheus Operator, which is used to create a Prometheus instances)
  • Grafana (including a dashboard and a data source configuration)
  • Confluent Platform (for Kafka and Zookeeper)
  • Kafka Lag Exporter (used to collect monitoring data of the Kafka lag)

Hints

Grafana

Grafana ConfigMaps contain expressions like {{ topic }}. Helm uses the same syntax for template function. More information here

  • Escape braces: {{ "{{" topic }}
  • Let Helm render the template as raw string: {{ {{ <config>}} }}