Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions .github/workflows/ci-operator.yml
Original file line number Diff line number Diff line change
Expand Up @@ -168,6 +168,21 @@ jobs:
docker build -f operator/Dockerfile -t kates-operator:ci .
kind load docker-image kates-operator:ci --name ci-test

# A release PR pins kates-tester and Kates to the tag its release has yet
# to publish, so ghcr.io answers 404: strimzi-operator's CRD hook and the
# Kates pod wait on the pull until the install times out. Build both from
# this checkout under the pinned tags and load them into the nodes, as
# integration.yml does for kates-tester; the kubelet then uses them
# (IfNotPresent). Kates is the JVM build: native is too slow for PR CI.
- name: Load the kates-tester and Kates images the charts pin
run: |
set -euo pipefail
tag=$(sed -nE 's/^appVersion:[[:space:]]*"?([^"]+)"?[[:space:]]*$/\1/p' charts/kates/Chart.yaml)
scripts/retry.sh 3 docker build -t "ghcr.io/bmscomp/kates-tester:${tag}" tester/
scripts/retry.sh 3 docker build -f kates/Dockerfile -t "ghcr.io/bmscomp/kates:${tag}" .
kind load docker-image "ghcr.io/bmscomp/kates-tester:${tag}" "ghcr.io/bmscomp/kates:${tag}" --name ci-test
echo "KATES_TAG=${tag}" >> "$GITHUB_ENV"

- name: Deploy Kafka, Kates and the operator
run: operator/e2e-stack.sh docker.io/library/kates-operator:ci

Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -208,7 +208,7 @@ This repository is also a GitHub Action, **Kates Quality Gate**. It installs the
```yaml
- name: Kafka performance gate
id: gate
uses: bmscomp/kates@v1.38.0
uses: bmscomp/kates@v1.39.0
with:
api-url: ${{ vars.KATES_URL }}
api-key: ${{ secrets.KATES_API_KEY }}
Expand All @@ -232,7 +232,7 @@ This repository is also a GitHub Action, **Kates Quality Gate**. It installs the

Outputs: `run-id`, `grade`, and `passed` (`true` or `false`).

The runner has to reach the Kates API. The default `http://localhost:8080` suits a self-hosted runner beside the cluster after `kates ports`; a GitHub-hosted runner needs the API exposed to it. The action runs on Linux and macOS runners, amd64 or arm64, and needs `curl`, `tar` and `python3`. Pin a release tag such as `v1.38.0`, or `v1` to follow the latest 1.x release: each stable release moves it.
The runner has to reach the Kates API. The default `http://localhost:8080` suits a self-hosted runner beside the cluster after `kates ports`; a GitHub-hosted runner needs the API exposed to it. The action runs on Linux and macOS runners, amd64 or arm64, and needs `curl`, `tar` and `python3`. Pin a release tag such as `v1.39.0`, or `v1` to follow the latest 1.x release: each stable release moves it.

## Other clusters

Expand Down
8 changes: 5 additions & 3 deletions charts/connect-cluster/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@ apiVersion: v2
name: connect-cluster
description: A Helm chart for deploying Strimzi Kafka Connect clusters
type: application
# Minor: rbac.scope, cluster (default) or namespace: nothing cluster-scoped,
# so a namespace admin installs the release.
version: 2.2.0
# Patch: testImages.kubectl moves to kates-tester 1.39.0, the tag the v1.39.0 release publishes;
# every chart that runs it pins the same one.
version: 2.2.1
# Tracks the Kafka line the workers run, as mirror-maker2's does. The plugin
# set is in the image; its pin is the kates.io/connect-image annotation.
appVersion: "4.3.1"
Expand All @@ -31,6 +31,8 @@ annotations:
artifacthub.io/category: streaming-messaging
artifacthub.io/license: Apache-2.0
artifacthub.io/changes: |
- kind: changed
description: "testImages.kubectl moves to kates-tester 1.39.0, the tag the v1.39.0 release publishes; scripts/check-versions.sh holds it to the kates chart's appVersion, as it does for every chart that runs the image. The image is unchanged since 1.38.0 — nothing under tester/ moved — so this is the pin, not the tooling."
- kind: added
description: "rbac.scope (or global.rbacScope): namespace leaves nothing cluster-scoped behind, so a namespace admin installs the release. It drops rack, for which Strimzi binds the workers to a ClusterRole, and the PriorityClass. Default cluster: unchanged"
- kind: changed
Expand Down
2 changes: 1 addition & 1 deletion charts/connect-cluster/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ imagePullPolicy: ""

# -- Images the chart's own pods use
testImages:
kubectl: "ghcr.io/bmscomp/kates-tester:1.38.0"
kubectl: "ghcr.io/bmscomp/kates-tester:1.39.0"

# ── Workers ─────────────────────────────────────────────────────────────────
# -- Number of worker replicas (seeded from autoscaling.minReplicas under an HPA)
Expand Down
8 changes: 5 additions & 3 deletions charts/kafka-cluster/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@ apiVersion: v2
name: kafka-cluster
description: A Strimzi Kafka cluster in KRaft mode — node pools, topics, users, rebalancing, tiered storage, network policy and observability
type: application
# Minor: rbac.scope, cluster (default) or namespace: nothing cluster-scoped,
# so a namespace admin installs the release.
version: 1.1.0
# Patch: testImages.kubectl and testImages.kafka move to kates-tester 1.39.0,
# the tag the v1.39.0 release publishes; every chart that runs it pins the same one.
version: 1.1.1
appVersion: "4.3.1"
icon: https://raw.githubusercontent.com/bmscomp/kates/main/docs/assets/charts/kafka-cluster.svg
home: https://strimzi.io/
Expand Down Expand Up @@ -38,6 +38,8 @@ annotations:
# newer; never lower it without removing the feature that set it.
kates.io/kafka-floor: "4.2.0"
artifacthub.io/changes: |
- kind: changed
description: "testImages.kubectl and testImages.kafka move to kates-tester 1.39.0, the tag the v1.39.0 release publishes; scripts/check-versions.sh holds them to the kates chart's appVersion, as it does for every chart that runs the image. The image is unchanged since 1.38.0 — nothing under tester/ moved — so this is the pin, not the tooling."
- kind: added
description: "rbac.scope (or global.rbacScope): namespace leaves nothing cluster-scoped behind, so a namespace admin installs the release. It drops kafka.rack, for which Strimzi binds the brokers to a ClusterRole, and the Kyverno ClusterPolicy, and refuses a NodePort listener, which needs the same binding. Default cluster: unchanged"
- kind: changed
Expand Down
4 changes: 2 additions & 2 deletions charts/kafka-cluster/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -71,8 +71,8 @@ global:
# -- Images of the Helm-test pods (tests.imageRegistry mirrors them). Pinned:
# scripts/check-versions.sh keeps them aligned with the other charts.
testImages:
kafka: "ghcr.io/bmscomp/kates-tester:1.38.0"
kubectl: "ghcr.io/bmscomp/kates-tester:1.38.0"
kafka: "ghcr.io/bmscomp/kates-tester:1.39.0"
kubectl: "ghcr.io/bmscomp/kates-tester:1.39.0"
# -- Pull policy for test pods (empty: Kubernetes' default)
pullPolicy: IfNotPresent

Expand Down
8 changes: 5 additions & 3 deletions charts/kates-chaos/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
apiVersion: v2
name: kates-chaos
# Minor: rbac.scope, cluster (default) or namespace: nothing
# cluster-scoped, Litmus namespaced.
version: 2.5.0
# Patch: images.tester moves to kates-tester 1.39.0, the tag the v1.39.0 release publishes;
# every chart that runs it pins the same one.
version: 2.5.1
# Tracks the LitmusChaos execution-plane version this chart deploys.
appVersion: "3.28.0"
description: Kates Chaos Engineering — wraps the LitmusChaos execution plane (operator, exporter, CRDs) with Kafka-specific RBAC, experiment/engine templating, and monitoring
Expand All @@ -27,6 +27,8 @@ annotations:
artifacthub.io/category: skip-prediction
artifacthub.io/prerelease: "false"
artifacthub.io/changes: |
- kind: changed
description: "images.tester moves to kates-tester 1.39.0, the tag the v1.39.0 release publishes; scripts/check-versions.sh holds it to the kates chart's appVersion, as it does for every chart that runs the image. The image is unchanged since 1.38.0 — nothing under tester/ moved — so this is the pin, not the tooling."
- kind: added
description: "rbac.scope (or global.rbacScope) and values-namespace.yaml: namespace renders nothing cluster-scoped, so a namespace admin installs Litmus and runs chaos in that namespace. Hook and test ClusterRoles become Roles and find the CRDs by discovery; the coordinator gets a Role; node chaos, other target namespaces and a non-namespaced Litmus are refused, the Kyverno ClusterPolicy skipped. Default cluster: unchanged"
- kind: changed
Expand Down
2 changes: 1 addition & 1 deletion charts/kates-chaos/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Left out: chaos in other namespaces, node chaos, the Kyverno ClusterPolicy. The
| `images.kubectl.repository` | Image for the installer Job | `registry.k8s.io/kubectl` |
| `images.kubectl.tag` | kubectl image tag | `v1.33.0` |
| `images.kubectl.digest` | Pin by digest (wins over tag) | `""` |
| `images.tester` | Image for GameDay and the Helm tests, whose scripts need a shell; runs as uid 1000 | `ghcr.io/bmscomp/kates-tester:1.38.0` |
| `images.tester` | Image for GameDay and the Helm tests, whose scripts need a shell; runs as uid 1000 | `ghcr.io/bmscomp/kates-tester:1.39.0` |
| `images.goRunner.repository` | Default runtime for experiments | `litmuschaos/go-runner` |
| `images.goRunner.tag` | go-runner image tag | `3.28.0` |

Expand Down
2 changes: 1 addition & 1 deletion charts/kates-chaos/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ images:
# tester — kates-tester, for GameDay and the Helm tests, whose scripts need
# the shell the kubectl image lacks. Runs as uid 1000. Pinned to the kates
# appVersion, like every chart's test image (scripts/check-versions.sh).
tester: "ghcr.io/bmscomp/kates-tester:1.38.0"
tester: "ghcr.io/bmscomp/kates-tester:1.39.0"
# go-runner — default runtime for ChaosExperiment definitions
goRunner:
repository: litmuschaos/go-runner
Expand Down
8 changes: 5 additions & 3 deletions charts/kates-platform/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,9 @@ name: kates-platform
description: Umbrella chart for the full Kates platform — Kafka, Kates, and supporting infrastructure
icon: https://raw.githubusercontent.com/bmscomp/kates/main/docs/assets/charts/kates-platform.svg
type: application
# Minor: global.rbacScope, the release's install mode (cluster or namespace),
# read by every subchart as its rbac.scope default.
version: 0.9.0
# Patch: the umbrella packs the subcharts the v1.39.0 release pins: kates
# 0.19.1, kafka-cluster 1.1.1, connect-cluster 2.2.1, mirror-maker2 0.12.1.
version: 0.9.1
appVersion: "1.0.0"
keywords:
- kafka
Expand Down Expand Up @@ -42,6 +42,8 @@ dependencies:
condition: connect-cluster.enabled
annotations:
artifacthub.io/changes: |
- kind: changed
description: "The umbrella moves with the v1.39.0 release: it packs kates 0.19.1, kafka-cluster 1.1.1, connect-cluster 2.2.1 and mirror-maker2 0.12.1 as they are at that tag."
- kind: added
description: "global.rbacScope, the release's install mode: cluster (default; a cluster admin) or namespace (a namespace admin; nothing cluster-scoped, no rack awareness, NodePort listeners, chaos or disruption). Every subchart reads it as its rbac.scope default."
- kind: changed
Expand Down
10 changes: 6 additions & 4 deletions charts/kates/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,14 +2,14 @@ apiVersion: v2
name: kates
description: Kates — Kafka Advanced Testing & Engineering Suite
type: application
# Minor: rbac.scope, cluster (default) or namespace: nothing cluster-scoped,
# so a namespace admin installs the release.
version: 0.19.0
# Patch: appVersion and the image tag move to 1.39.0, the tag the v1.39.0
# release publishes.
version: 0.19.1
# The non-blocking health endpoints this chart's probes now point at come from
# a BUILD-TIME property (quarkus.messaging.health.enabled=false), so they only
# exist in the image built from this branch. Keep appVersion and
# image.tag in values.yaml pinned to that release.
appVersion: "1.38.0"
appVersion: "1.39.0"
keywords:
- kafka
- testing
Expand All @@ -28,6 +28,8 @@ annotations:
artifacthub.io/category: integration-delivery
artifacthub.io/license: Apache-2.0
artifacthub.io/changes: |
- kind: changed
description: "appVersion 1.39.0 and the image tag move to 1.39.0. The backend is unchanged since 1.38.0 — nothing under kates/src moved — so the image is a rebuild of the same code."
- kind: added
description: "rbac.scope defaults to empty and falls back to global.rbacScope, then cluster, so an umbrella sets every chart's scope with one key. An unset scope still means cluster"
- kind: changed
Expand Down
2 changes: 1 addition & 1 deletion charts/kates/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ All configuration is in [values.yaml](values.yaml). Key sections:
| Parameter | Default | Description |
|-----------|---------|-------------|
| `image.repository` | `ghcr.io/bmscomp/kates` | Container image name |
| `image.tag` | `1.38.0` | Container image tag, pinned in `values.yaml` to match the chart's `appVersion`. Keep it at 1.22.0 or newer: the probes use health endpoints older images lack |
| `image.tag` | `1.39.0` | Container image tag, pinned in `values.yaml` to match the chart's `appVersion`. Keep it at 1.22.0 or newer: the probes use health endpoints older images lack |
| `image.pullPolicy` | `IfNotPresent` | Image pull policy |
| `global.imageRegistry` | `""` | Prepended, with a slash, to every image the chart renders: the API, PostgreSQL, the init container, the jobs, the helm test pods and `chaos.stressImage` |
| `imagePullSecrets`, `global.imagePullSecrets` | `[]` | Pull secrets, both lists, on every pod the chart renders. An entry is a Secret name (`regcred`) or `{name: regcred}` |
Expand Down
2 changes: 1 addition & 1 deletion charts/kates/values-native.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@

image:
# Published as <appVersion>-native alongside the JVM tag.
tag: "1.38.0-native"
tag: "1.39.0-native"

# Not read by a native image — see above.
jvm:
Expand Down
2 changes: 1 addition & 1 deletion charts/kates/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ image:
repository: ghcr.io/bmscomp/kates
# -- Image tag. Must be the release that carries the non-blocking health
# endpoints the probe defaults below depend on (>= 1.22.0).
tag: "1.38.0"
tag: "1.39.0"
# -- Image pull policy
pullPolicy: IfNotPresent

Expand Down
8 changes: 5 additions & 3 deletions charts/mirror-maker2/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@ apiVersion: v2
name: mirror-maker2
description: Strimzi KafkaMirrorMaker2 — cross-cluster replication, DR, and cross-version migration (2.x/3.x → 4.x)
type: application
# Minor: rbac.scope, cluster (default) or namespace: nothing cluster-scoped,
# so a namespace admin installs the release.
version: 0.12.0
# Patch: testImages.kubectl moves to kates-tester 1.39.0, the tag the v1.39.0 release publishes;
# every chart that runs it pins the same one.
version: 0.12.1
# Tracks the Kafka line the MM2 Connect workers run (STRIMZI_KAFKA_VERSION).
appVersion: "4.3.1"
kubeVersion: ">=1.27.0-0"
Expand All @@ -31,6 +31,8 @@ annotations:
artifacthub.io/category: streaming-messaging
artifacthub.io/license: Apache-2.0
artifacthub.io/changes: |
- kind: changed
description: "testImages.kubectl moves to kates-tester 1.39.0, the tag the v1.39.0 release publishes; scripts/check-versions.sh holds it to the kates chart's appVersion, as it does for every chart that runs the image. The image is unchanged since 1.38.0 — nothing under tester/ moved — so this is the pin, not the tooling."
- kind: added
description: "rbac.scope (or global.rbacScope): namespace leaves nothing cluster-scoped behind, so a namespace admin installs the release. It drops rack, for which Strimzi binds the workers to a ClusterRole. Default cluster: unchanged"
- kind: changed
Expand Down
2 changes: 1 addition & 1 deletion charts/mirror-maker2/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ global:

# -- Images used by the Helm test pods
testImages:
kubectl: "ghcr.io/bmscomp/kates-tester:1.38.0"
kubectl: "ghcr.io/bmscomp/kates-tester:1.39.0"

# -- Number of MM2 (Connect) worker replicas
replicas: 3
Expand Down
8 changes: 5 additions & 3 deletions charts/strimzi-operator/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
apiVersion: v2
name: strimzi-operator
# Minor: rbac.scope namespace, an operator a namespace admin can install with no
# cluster-scoped object.
version: 0.5.0
# Patch: testImages.kubectl moves to kates-tester 1.39.0, the tag the v1.39.0 release publishes;
# every chart that runs it pins the same one.
version: 0.5.1
# Tracks the Strimzi operator version this chart deploys. The CLI rewrites this
# (and the dependency version) in a generated copy when another version is
# selected; the repository copy is the pin.
Expand Down Expand Up @@ -30,6 +30,8 @@ annotations:
artifacthub.io/category: streaming-messaging
artifacthub.io/license: Apache-2.0
artifacthub.io/changes: |
- kind: changed
description: "testImages.kubectl moves to kates-tester 1.39.0, the tag the v1.39.0 release publishes; scripts/check-versions.sh holds it to the kates chart's appVersion, as it does for every chart that runs the image. The image is unchanged since 1.38.0 — nothing under tester/ moved — so this is the pin, not the tooling."
- kind: added
description: "rbac.scope (or global.rbacScope) namespace and values-namespace.yaml: the operator's rights as Roles and RoleBindings in each watched namespace, with the rules of upstream's own ClusterRoles rendered from the subchart, and nothing cluster-scoped, so a namespace admin can install it. An admin installs the CRDs and grants escalate and bind on roles in the namespace once; rack awareness, NodePort addresses, volume-expansion checks and the drain cleaner are left out. The Helm tests use a Role and API discovery in this mode"
- kind: fixed
Expand Down
2 changes: 1 addition & 1 deletion charts/strimzi-operator/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ Left out, because only a cluster grant gives them: rack awareness (the operator
| Key | Default | Description |
|-----|---------|-------------|
| `strimziVersion` | `1.2.0` | Builds the CRD bundle URL. Must equal `Chart.yaml` `appVersion` + dependency version. |
| `testImages.kubectl` | `ghcr.io/bmscomp/kates-tester:1.38.0` | Image for the CRD hook Job and Helm tests |
| `testImages.kubectl` | `ghcr.io/bmscomp/kates-tester:1.39.0` | Image for the CRD hook Job and Helm tests |
| `crdUpgrade.enabled` | `true` | Apply CRDs via the pre-install/pre-upgrade hook |
| `crdUpgrade.url` | `""` | Override the bundle URL (empty = derive from `strimziVersion`). Use an internal mirror when airgapped. |
| `crdUpgrade.backoffLimit` | `3` | Job retries before the install/upgrade aborts |
Expand Down
2 changes: 1 addition & 1 deletion charts/strimzi-operator/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ strimziVersion: "1.2.0"
# tests). The operator's own image comes from the subchart.
testImages:
# -- kubectl image used by the CRD-upgrade hook Job and the Helm tests
kubectl: "ghcr.io/bmscomp/kates-tester:1.38.0"
kubectl: "ghcr.io/bmscomp/kates-tester:1.39.0"

# ── Helm tests ───────────────────────────────────────────────────────────────
tests:
Expand Down
2 changes: 1 addition & 1 deletion config/litmus/experiments/consumer-latency-probe.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ spec:
criteria: contains
value: "PASS"
source:
image: ghcr.io/bmscomp/kates-tester:1.38.0
image: ghcr.io/bmscomp/kates-tester:1.39.0
hostNetwork: false
---
# Consumer latency monitoring ConfigMap
Expand Down
4 changes: 2 additions & 2 deletions config/litmus/experiments/isr-health-probe.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ spec:
criteria: contains
value: "PASS"
source:
image: ghcr.io/bmscomp/kates-tester:1.38.0
image: ghcr.io/bmscomp/kates-tester:1.39.0
hostNetwork: false

# Min ISR check - ensure partitions can still accept writes
Expand Down Expand Up @@ -88,7 +88,7 @@ spec:
criteria: "<="
value: "5" # Allow up to 5 unavailable during chaos
source:
image: ghcr.io/bmscomp/kates-tester:1.38.0
image: ghcr.io/bmscomp/kates-tester:1.39.0
hostNetwork: false
---
# ISR health monitoring ConfigMap
Expand Down
6 changes: 3 additions & 3 deletions config/litmus/experiments/kafka-chaos-cronjob.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ spec:
# Pre-flight check
- name: preflight-check
container:
image: ghcr.io/bmscomp/kates-tester:1.38.0
image: ghcr.io/bmscomp/kates-tester:1.39.0
imagePullPolicy: IfNotPresent
command: ["/bin/bash"]
args:
Expand Down Expand Up @@ -96,7 +96,7 @@ spec:
- name: experiment
- name: duration
container:
image: ghcr.io/bmscomp/kates-tester:1.38.0
image: ghcr.io/bmscomp/kates-tester:1.39.0
imagePullPolicy: IfNotPresent
command: ["/bin/bash"]
args:
Expand Down Expand Up @@ -142,7 +142,7 @@ spec:
# Verify cluster recovery
- name: verify-cluster
container:
image: ghcr.io/bmscomp/kates-tester:1.38.0
image: ghcr.io/bmscomp/kates-tester:1.39.0
imagePullPolicy: IfNotPresent
command: ["/bin/bash"]
args:
Expand Down
Loading
Loading