diff --git a/.github/workflows/ci-operator.yml b/.github/workflows/ci-operator.yml index f607984a..c83fe5dc 100644 --- a/.github/workflows/ci-operator.yml +++ b/.github/workflows/ci-operator.yml @@ -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 diff --git a/README.md b/README.md index 13356266..008aecb0 100644 --- a/README.md +++ b/README.md @@ -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 }} @@ -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 diff --git a/charts/connect-cluster/Chart.yaml b/charts/connect-cluster/Chart.yaml index 97e40ec9..46ae4166 100644 --- a/charts/connect-cluster/Chart.yaml +++ b/charts/connect-cluster/Chart.yaml @@ -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" @@ -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 diff --git a/charts/connect-cluster/values.yaml b/charts/connect-cluster/values.yaml index baf321b3..318fc03f 100644 --- a/charts/connect-cluster/values.yaml +++ b/charts/connect-cluster/values.yaml @@ -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) diff --git a/charts/kafka-cluster/Chart.yaml b/charts/kafka-cluster/Chart.yaml index 2a9324f9..10c2580b 100644 --- a/charts/kafka-cluster/Chart.yaml +++ b/charts/kafka-cluster/Chart.yaml @@ -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/ @@ -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 diff --git a/charts/kafka-cluster/values.yaml b/charts/kafka-cluster/values.yaml index bb66e31d..ef2432e1 100644 --- a/charts/kafka-cluster/values.yaml +++ b/charts/kafka-cluster/values.yaml @@ -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 diff --git a/charts/kates-chaos/Chart.yaml b/charts/kates-chaos/Chart.yaml index 88434a53..c30e5e49 100644 --- a/charts/kates-chaos/Chart.yaml +++ b/charts/kates-chaos/Chart.yaml @@ -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 @@ -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 diff --git a/charts/kates-chaos/README.md b/charts/kates-chaos/README.md index 290fec4e..7cdc7447 100644 --- a/charts/kates-chaos/README.md +++ b/charts/kates-chaos/README.md @@ -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` | diff --git a/charts/kates-chaos/values.yaml b/charts/kates-chaos/values.yaml index 454cef50..a3c72f5a 100644 --- a/charts/kates-chaos/values.yaml +++ b/charts/kates-chaos/values.yaml @@ -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 diff --git a/charts/kates-platform/Chart.yaml b/charts/kates-platform/Chart.yaml index 535d11fa..01651064 100644 --- a/charts/kates-platform/Chart.yaml +++ b/charts/kates-platform/Chart.yaml @@ -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 @@ -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 diff --git a/charts/kates/Chart.yaml b/charts/kates/Chart.yaml index 4a457c8c..d1306d0a 100644 --- a/charts/kates/Chart.yaml +++ b/charts/kates/Chart.yaml @@ -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 @@ -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 diff --git a/charts/kates/README.md b/charts/kates/README.md index 257cd877..cae42013 100644 --- a/charts/kates/README.md +++ b/charts/kates/README.md @@ -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}` | diff --git a/charts/kates/values-native.yaml b/charts/kates/values-native.yaml index 1d1c3a47..e6069afb 100644 --- a/charts/kates/values-native.yaml +++ b/charts/kates/values-native.yaml @@ -23,7 +23,7 @@ image: # Published as -native alongside the JVM tag. - tag: "1.38.0-native" + tag: "1.39.0-native" # Not read by a native image — see above. jvm: diff --git a/charts/kates/values.yaml b/charts/kates/values.yaml index 6d9e8f6d..c30d5f32 100644 --- a/charts/kates/values.yaml +++ b/charts/kates/values.yaml @@ -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 diff --git a/charts/mirror-maker2/Chart.yaml b/charts/mirror-maker2/Chart.yaml index 3989852d..06b45176 100644 --- a/charts/mirror-maker2/Chart.yaml +++ b/charts/mirror-maker2/Chart.yaml @@ -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" @@ -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 diff --git a/charts/mirror-maker2/values.yaml b/charts/mirror-maker2/values.yaml index b24f3457..dbd741c9 100644 --- a/charts/mirror-maker2/values.yaml +++ b/charts/mirror-maker2/values.yaml @@ -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 diff --git a/charts/strimzi-operator/Chart.yaml b/charts/strimzi-operator/Chart.yaml index cc549f49..3300eb45 100644 --- a/charts/strimzi-operator/Chart.yaml +++ b/charts/strimzi-operator/Chart.yaml @@ -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. @@ -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 diff --git a/charts/strimzi-operator/README.md b/charts/strimzi-operator/README.md index a443d7e2..82eaa330 100644 --- a/charts/strimzi-operator/README.md +++ b/charts/strimzi-operator/README.md @@ -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 | diff --git a/charts/strimzi-operator/values.yaml b/charts/strimzi-operator/values.yaml index bef31dab..b4f5f9b8 100644 --- a/charts/strimzi-operator/values.yaml +++ b/charts/strimzi-operator/values.yaml @@ -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: diff --git a/config/litmus/experiments/consumer-latency-probe.yaml b/config/litmus/experiments/consumer-latency-probe.yaml index d6716ab2..106ec8fc 100644 --- a/config/litmus/experiments/consumer-latency-probe.yaml +++ b/config/litmus/experiments/consumer-latency-probe.yaml @@ -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 diff --git a/config/litmus/experiments/isr-health-probe.yaml b/config/litmus/experiments/isr-health-probe.yaml index 8a85cc13..88c37aaa 100644 --- a/config/litmus/experiments/isr-health-probe.yaml +++ b/config/litmus/experiments/isr-health-probe.yaml @@ -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 @@ -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 diff --git a/config/litmus/experiments/kafka-chaos-cronjob.yaml b/config/litmus/experiments/kafka-chaos-cronjob.yaml index e2dd8ace..c5f8d425 100644 --- a/config/litmus/experiments/kafka-chaos-cronjob.yaml +++ b/config/litmus/experiments/kafka-chaos-cronjob.yaml @@ -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: @@ -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: @@ -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: diff --git a/config/litmus/experiments/kafka-gameday-workflow.yaml b/config/litmus/experiments/kafka-gameday-workflow.yaml index b7c4c138..36f24e01 100644 --- a/config/litmus/experiments/kafka-gameday-workflow.yaml +++ b/config/litmus/experiments/kafka-gameday-workflow.yaml @@ -192,7 +192,7 @@ spec: - name: experiment-type - name: extra-env 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: @@ -255,7 +255,7 @@ spec: parameters: - name: phase 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: @@ -300,7 +300,7 @@ spec: parameters: - name: phase 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: @@ -333,7 +333,7 @@ spec: # Final report - name: chaos-report 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: diff --git a/config/litmus/experiments/kates-chaos-integration-job.yaml b/config/litmus/experiments/kates-chaos-integration-job.yaml index abaafcf8..aa8e103e 100644 --- a/config/litmus/experiments/kates-chaos-integration-job.yaml +++ b/config/litmus/experiments/kates-chaos-integration-job.yaml @@ -18,7 +18,7 @@ spec: restartPolicy: Never containers: - name: chaos-runner - image: ghcr.io/bmscomp/kates-tester:1.38.0 + image: ghcr.io/bmscomp/kates-tester:1.39.0 imagePullPolicy: IfNotPresent env: - name: KATES_API_URL diff --git a/config/litmus/experiments/producer-throughput-probe.yaml b/config/litmus/experiments/producer-throughput-probe.yaml index f118e0fc..c7d11f70 100644 --- a/config/litmus/experiments/producer-throughput-probe.yaml +++ b/config/litmus/experiments/producer-throughput-probe.yaml @@ -45,7 +45,7 @@ spec: criteria: ">=" value: "10.0" # Minimum 10 records/sec source: - image: ghcr.io/bmscomp/kates-tester:1.38.0 + image: ghcr.io/bmscomp/kates-tester:1.39.0 hostNetwork: false --- # Standalone producer throughput ConfigMap for reuse diff --git a/docs/book/14-recipes.md b/docs/book/14-recipes.md index 97408b30..efa6f5ed 100644 --- a/docs/book/14-recipes.md +++ b/docs/book/14-recipes.md @@ -710,7 +710,7 @@ jobs: kafka-gates: runs-on: ubuntu-latest env: - KATES_VERSION: v1.38.0 + KATES_VERSION: v1.39.0 KATES_NAMESPACE: team KATES_URL: http://localhost:8080 KATES_API_KEY: ${{ secrets.KATES_API_KEY }} diff --git a/docs/book/appendix-d-versions.md b/docs/book/appendix-d-versions.md index 00af3eb7..87aa4d00 100644 --- a/docs/book/appendix-d-versions.md +++ b/docs/book/appendix-d-versions.md @@ -16,18 +16,18 @@ Every version the platform pins, in one place. This table is generated from the | Go (CLI) | 1.26.0 | `cli/go.mod` | | `apicurio-registry` chart | 0.5.1 (app 3.3.0) | `charts/apicurio-registry/Chart.yaml` | | `cdc-postgresql` chart | 0.3.1 (app 16.15) | `charts/cdc-postgresql/Chart.yaml` | -| `connect-cluster` chart | 2.2.0 (app 4.3.1) | `charts/connect-cluster/Chart.yaml` | +| `connect-cluster` chart | 2.2.1 (app 4.3.1) | `charts/connect-cluster/Chart.yaml` | | `headlamp` chart | 0.3.0 (app 0.40.1) | `charts/headlamp/Chart.yaml` | -| `kafka-cluster` chart | 1.1.0 (app 4.3.1) | `charts/kafka-cluster/Chart.yaml` | +| `kafka-cluster` chart | 1.1.1 (app 4.3.1) | `charts/kafka-cluster/Chart.yaml` | | `kafka-common` chart | 0.1.3 (library) | `charts/kafka-common/Chart.yaml` | | `kafka-ui` chart | 0.3.4 (app v1.5.0) | `charts/kafka-ui/Chart.yaml` | -| `kates-chaos` chart | 2.5.0 (app 3.28.0) | `charts/kates-chaos/Chart.yaml` | -| `kates-platform` chart | 0.9.0 (app 1.0.0) | `charts/kates-platform/Chart.yaml` | -| `kates` chart | 0.19.0 (app 1.38.0) | `charts/kates/Chart.yaml` | +| `kates-chaos` chart | 2.5.1 (app 3.28.0) | `charts/kates-chaos/Chart.yaml` | +| `kates-platform` chart | 0.9.1 (app 1.0.0) | `charts/kates-platform/Chart.yaml` | +| `kates` chart | 0.19.1 (app 1.39.0) | `charts/kates/Chart.yaml` | | `legacy-kafka` chart | 0.2.2 (app 3.9.1) | `charts/legacy-kafka/Chart.yaml` | -| `mirror-maker2` chart | 0.12.0 (app 4.3.1) | `charts/mirror-maker2/Chart.yaml` | +| `mirror-maker2` chart | 0.12.1 (app 4.3.1) | `charts/mirror-maker2/Chart.yaml` | | `monitoring` chart | 1.9.0 (app 82.4.3) | `charts/monitoring/Chart.yaml` | -| `strimzi-operator` chart | 0.5.0 (app 1.2.0) | `charts/strimzi-operator/Chart.yaml` | +| `strimzi-operator` chart | 0.5.1 (app 1.2.0) | `charts/strimzi-operator/Chart.yaml` | | `velero` chart | 11.4.0 (app 1.17.1) | `charts/velero/Chart.yaml` | diff --git a/docs/kafka-cluster-runbook.md b/docs/kafka-cluster-runbook.md index d36a31f3..b3f160af 100644 --- a/docs/kafka-cluster-runbook.md +++ b/docs/kafka-cluster-runbook.md @@ -10,7 +10,7 @@ kubectl -n $NS get kafka $CLUSTER -o jsonpath='{range .status.conditions[*]}{.ty kubectl -n $NS get kafkanodepools,pods -l strimzi.io/cluster=$CLUSTER # A client shell with the platform's backend credentials: kubectl -n $NS run kcat --rm -it --restart=Never --labels kates.io/test-pod=true \ - --image=ghcr.io/bmscomp/kates-tester:1.38.0 -- bash + --image=ghcr.io/bmscomp/kates-tester:1.39.0 -- bash ``` Inside that shell, `/opt/kafka/bin/kafka-topics.sh --bootstrap-server $CLUSTER-kafka-bootstrap:9092 --command-config client.properties …` answers most partition questions; `kafka-metadata-quorum.sh … describe --status` answers quorum questions. diff --git a/docs/registry/kates-tester.md b/docs/registry/kates-tester.md index 20821986..f64c5fb3 100644 --- a/docs/registry/kates-tester.md +++ b/docs/registry/kates-tester.md @@ -98,8 +98,8 @@ Override it like any other value: ```yaml testImages: - kubectl: ghcr.io/bmscomp/kates-tester:1.38.0 - kafka: ghcr.io/bmscomp/kates-tester:1.38.0 + kubectl: ghcr.io/bmscomp/kates-tester:1.39.0 + kafka: ghcr.io/bmscomp/kates-tester:1.39.0 ``` --- @@ -155,7 +155,7 @@ docker run --rm -it -v "$HOME/.kube:/home/kates/.kube:ro" \ | Tag | Meaning | |---|---| -| `1.38.0` | Release version — what the charts pin | +| `1.39.0` | Release version — what the charts pin | | `latest` | Latest default-branch build | | `sha-` | Exact commit | diff --git a/docs/registry/kates.md b/docs/registry/kates.md index b242a795..a4cf6291 100644 --- a/docs/registry/kates.md +++ b/docs/registry/kates.md @@ -43,8 +43,8 @@ unhealthy on `/api/health` — which is expected, not a bug. See | Tag pattern | What it is | |---|---| -| `1.38.0`, `1.37`, `1` | JVM build — Eclipse Temurin 21 JRE | -| `1.38.0-native`, … | GraalVM native build — ahead-of-time compiled, UBI 9 minimal | +| `1.39.0`, `1.39`, `1` | JVM build — Eclipse Temurin 21 JRE | +| `1.39.0-native`, … | GraalVM native build — ahead-of-time compiled, UBI 9 minimal | | `latest` | Latest default-branch build (JVM) | | `` | Exact commit | @@ -54,7 +54,7 @@ are signed with [cosign](https://docs.sigstore.dev/). ### Which variant should you run? -| | JVM (`1.38.0`) | Native (`1.38.0-native`) | +| | JVM (`1.39.0`) | Native (`1.39.0-native`) | |---|---|---| | Start-up | Seconds | Milliseconds | | Memory floor | Higher | Substantially lower | @@ -68,7 +68,7 @@ it, so the chart's `jvm.options` are silently inert. Its heap comes from the def chart's `containerArgs`) or by passing arguments to `docker run`: ``` -docker run --rm ghcr.io/bmscomp/kates:1.38.0-native -XX:MaximumHeapSizePercent=50 +docker run --rm ghcr.io/bmscomp/kates:1.39.0-native -XX:MaximumHeapSizePercent=50 ``` Rule of thumb: **JVM for sustained benchmarking**, where JIT warm-up pays for itself over a diff --git a/kates/k8s/deployment.yaml b/kates/k8s/deployment.yaml index ada5c054..697c6056 100644 --- a/kates/k8s/deployment.yaml +++ b/kates/k8s/deployment.yaml @@ -32,7 +32,7 @@ spec: type: RuntimeDefault containers: - name: kates - image: ghcr.io/bmscomp/kates:1.38.0 + image: ghcr.io/bmscomp/kates:1.39.0 imagePullPolicy: IfNotPresent securityContext: allowPrivilegeEscalation: false diff --git a/operator/e2e-stack.sh b/operator/e2e-stack.sh index b640d961..9d9e1543 100755 --- a/operator/e2e-stack.sh +++ b/operator/e2e-stack.sh @@ -4,6 +4,8 @@ # # KUBECONFIG= operator/e2e-stack.sh # +# KATES_TAG picks the Kates image tag; it defaults to the chart's appVersion, native. +# # Scratch clusters only: it installs Strimzi and Kafka, as a CI job would. set -euo pipefail cd "$(dirname "$0")/.." @@ -22,7 +24,7 @@ kubectl -n kates create secret generic kates-backend --dry-run=client -o yaml \ tag=$(sed -nE 's/^appVersion:[[:space:]]*"?([^"]+)"?[[:space:]]*$/\1/p' charts/kates/Chart.yaml) # One broker: Kates' default of three replicas would refuse every topic. helm upgrade --install kates charts/kates -n kates --wait --timeout 8m \ - --set image.tag="$tag-native" \ + --set image.tag="${KATES_TAG:-$tag-native}" \ --set-string defaults.replicationFactor=1,defaults.minInsyncReplicas=1 \ --set-json 'extraEnv=[{"name":"KATES_OUTBOX_TOPIC_REPLICATION_FACTOR","value":"1"}]' diff --git a/server.json b/server.json index 6fbfb705..89eec9b0 100644 --- a/server.json +++ b/server.json @@ -3,7 +3,7 @@ "name": "io.github.bmscomp/kates", "title": "Kates MCP Server", "description": "Read-only Model Context Protocol (MCP) server for Apache Kafka cluster diagnostics, benchmark run analysis, chaos dry-run previews, and security posture audits.", - "version": "1.38.0", + "version": "1.39.0", "websiteUrl": "https://bmscomp.github.io/kates/", "repository": { "url": "https://github.com/bmscomp/kates", @@ -13,8 +13,8 @@ "packages": [ { "registryType": "mcpb", - "identifier": "https://github.com/bmscomp/kates/releases/download/v1.38.0/kates-linux-amd64.tar.gz", - "version": "1.38.0", + "identifier": "https://github.com/bmscomp/kates/releases/download/v1.39.0/kates-linux-amd64.tar.gz", + "version": "1.39.0", "transport": { "type": "stdio" },