v0.10.3

This is the release of Theodolite 0.10.3. It provides a few small improvements:

• Resources are now applied in the order they are specified and deleted in reverse.
• Theodolite now waits for all pods of Deployments and StatefulSets to be successfully deleted before continuing with the next experiment.
• A bug with a leaking file resource was fixed, causing problems in a few deployments.

Theodolite uses per default an older Strimzi version, which officially does not support the newest Kubernetes version. Theodolite benchmarks should still work when setting the Helm configuration:

strimzi-kafka-operator:
  createGlobalResources: false # Might disable some of Strimzi's features
  extraEnvs:
    - name: STRIMZI_KUBERNETES_VERSION
      value: "major=1,minor=28"

v0.10.2

This is the release of Theodolite 0.10.2. It provides a few small improvements:

• A warning about duplicate port names is fixed.
• Kafka helper pods are labels, which allows using them in exec actions.

Theodolite uses per default an older Strimzi version, which officially does not support the newest Kubernetes version. Theodolite benchmarks should still work when setting the Helm configuration:

strimzi-kafka-operator:
  createGlobalResources: false # Might disable some of Strimzi's features
  extraEnvs:
    - name: STRIMZI_KUBERNETES_VERSION
      value: "major=1,minor=28"

v0.10.1

This is the release of Theodolite 0.10.1. It provides a few small improvements:

• Benchmark images are now based on eclipse-temurin
• Support for factors, prefix and suffix when patching generic resources
• Support for patching environment variables in initContainers
• Allow setting volumeName in Theodolite's results PVC to store results in existing volume

v0.10.0

This is the release of Theodolite 0.10.0. The most important changes are:

• New SLO aggregations are now available in the generic SLO checker: first and last take only the first or last value from a time series. trend uses linear regression to return the increase/decrease per second from the time series.
• For the generic SLO checker, the two true and false operator are now available, which always evaluate to true or false. They can be used to track additional metrics that now be considered for the demand/capacity computation.
• The step resolution for Prometheus queries is now configurable.
• For a Prometheus query that returns multiple time series, it is now possible to take all instead of just the first one. To enable it, set takeOnlyFirstMetric: false in the SLO checker's properties.
• Prometheus and Strimzi are upgraded and their configurability is improved. Also some Theodolite-specific configurations have been removed.
• Managing Kafka resources by setting a kafkaConfig in a benchmark is now deprecated. Instead Strimzi should be used to manage Kafka topics as Kubernetes resources.

v0.9.0

This is the release of Theodolite 0.9.0. The most important new features are:

• SLO thresholds can now be defined relatively to tested load intensities and provisioned resources. Even arbitrary complex mathematical expressions with load and resources as variables are possible.
• A new generic patcher allows to patch arbitrary Kubernetes resources (including CRDs) by specifying the JSON path ob the field to be patched.
• The configuration and implementations of the Theodolite stream processing benchmarks are further aligned to allow for a better comparison of different frameworks.
• The Theodolite benchmark definitions for the stream processing benchmarks are extended to include options for vertical scaling and provide a dropped records SLO. They also define topics now using Strimzi.
• Configurability of the Strimzi Kafka deployment is improved.

v0.8.6

This is the release of Theodolite 0.8.6. It introduces the following changes:

• Theodolite's Hazelcast Jet benchmarks can be now installed via Helm
• A bug is fixed regarding the restriction search
• Consumer group filters are added to all benchmarks (required if used with Strimzi)
• Benchmarks are assigned Kubernetes labels
• Theodolite's CPU and memory resources are now configurable via Helm

v0.8.5

This is the release of Theodolite 0.8.5. It introduces support for setting nodeSelectors or nodeAffinities for Strimzi's Kafka Exporter and the ZooEntrance pods via Helm.

v0.8.4

This is the release of Theodolite 0.8.4. It fixes an issue introduced with the release of 0.8.3.

v0.8.3

This is the release of Theodolite 0.8.3. It provides a bug fix for setting Strimzi's ZooKeeper Pod templates via Helm.

v0.8.2

This is the release of Theodolite 0.8.2. It upgrades the kube-prometheus-stack to v41.7.* in our Helm chart. This comes with the following under-the-hood changes:

• We now use Grafana from kube-prometheus-stack instead of own subchart.
  • This also upgrades Grafana to the latest version.
  • As Grafana is only used for passive observation, nothing should have changed concerning the benchmark execution. However, to recover the old installation, set kube-prometheus-stack.grafana.enabled to false and set grafana to the default configuration from v0.8.1 in your values.yaml.
• The optional full-stack monitoring is now enhanced.
  • Note that this should not change anything in the default configuration but only if you use the kube-prometheus-stack to collect cluster metrics, node-level metrics, etc.
  • For full-stack monitoring, the default Prometheus from kube-prometheus-stack can now be used.
  • We provide a Helm values file for enabling full-stack monitoring.
  • Using this file now enables additional Kubernetes metrics exporters and Grafana dashboards.