Strimzi 1.2 serves only the v1 API and runs Kafka 4.2 and 4.3. The node-pool hook no longer drives the ZooKeeper to KRaft migration or the drain that freed the shared "kafka" pool name: Strimzi 1.x has no ZooKeeper support, and the platform migration refuses to upgrade while a ZooKeeper cluster is left. A cluster migrated earlier keeps its "kafka" broker pool. Without the drain the hook takes seconds, so the seven-hour install timeout goes too. Kafka 4 rejects the topic configs it removed and a segment.bytes below 1 MiB, which Kafka 3.x accepted. A KafkaTopic that sets one stays NotReady while the release reports Ready, so the chart refuses to render such a topic. It reads segment.bytes the way Kafka does: trimmed, with an optional sign, leading zeros decimal. BREAKING CHANGE: the Kafka application accepts version v4.3 (default) and v4.2; v3.8 and v3.9 are gone, and the platform migration moves existing applications to v4.3. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <f@lex.la>
Managed Kafka Service
Node pools
The chart runs Kafka in KRaft mode with two KafkaNodePool resources, one for brokers and one for controllers. The pools are not regular chart manifests: a pre-install,pre-upgrade Helm hook applies them on every install and upgrade, before the main release apply. Every pool that exists today was created by that hook and is absent from every release manifest. Follow a run with kubectl logs -n <namespace> job/<release>-kafka-migration.
Each pool gets a short, release-hashed name (b-<hash> for brokers, c-<hash> for controllers). KafkaNodePool names are namespace-unique and each release hashes differently, so several Kafka instances can live in one namespace. The hash keeps the pool name at 10 characters, so the derived <cluster>-<pool>-<id> pod hostname grows only with the release name and the node ID. At the 44-character name limit it fits the 63-character limit only while every node ID is a single digit; controllers take node IDs from kafka.replicas upward.
A cluster migrated from ZooKeeper by an earlier chart keeps its broker pool named kafka: that pool adopted the cluster's original <cluster>-kafka-N brokers and their data. The controller pool pins its node IDs above the broker range (strimzi.io/next-node-ids), so the broker pool keeps [0..replicas-1].
Deletion and PVC retention
Both node pools set deleteClaim: false, so deleting a Kafka release intentionally leaves its data PVCs (data-0-<cluster>-<pool>-N) behind. The trade-off is that the PVCs keep consuming tenant quota until removed by hand, and recreating a same-named Kafka rebinds the stale volumes, whose on-disk cluster id will not match the new cluster (InconsistentClusterIdException, CrashLoop). To truly start over, delete the leftover PVCs before recreating: kubectl -n <namespace> delete pvc -l strimzi.io/cluster=<release>.
Upgrading from ZooKeeper and from Kafka 3.x
The operator behind this chart (Strimzi 1.x) runs neither ZooKeeper nor Kafka 3.x. A ZooKeeper-based instance must reach KRaft on the Cozystack release that ships the ZooKeeper to KRaft migration (v1.7) before the platform moves past it. On every platform variant, the platform upgrade refuses to switch package sources while Strimzi still serves v1beta2 and any Kafka lacks confirmed KRaft state. On the variants that run platform migrations, migration 61 checks the same evidence again, including on a repeat run after API conversion. Every Kafka must report a nonempty kafkaMetadataVersion and either kafkaMetadataState: KRaft or, without a state, Ready=True or the cozystack.io/kraft-verified annotation that migration 61 records on every Kafka it accepts before it stops the Strimzi operators. A kafkaMetadataState other than KRaft, a ZooKeeper section or a missing status blocks the upgrade, and the error names the reason for each Kafka. The API conversion deletes kafkaMetadataState and may change the spec, and neither invalidates that evidence on a retry. The migration also moves every instance on v3.8 or v3.9 to v4.3; Strimzi then rolls the brokers onto Kafka 4.3. Elsewhere those steps are manual, and the platform upgrade refuses to start while Strimzi still stores v1beta2: before upgrading the platform, run /migrations/61 from this release's platform-migrations image with cluster-admin credentials. That run is needed on every such cluster that has the kafka-operator package installed, through the paas bundle or bundles.enabledPackages, even if it runs no Kafka: the Strimzi CRDs list v1beta2 in their stored versions whether or not any object exists. The run stamps platform version 62 in the cozystack-version ConfigMap of cozy-system, and the migration runner starts from that stamp, so if the cluster later moves to an isp-* variant, the platform migrations numbered below 62 do not run there. Before it changes anything, the run checks the Kafkas, their topics and every Strimzi object, and refuses with the name and reason of each one it cannot move; it can be repeated after a failure. It then stops the Strimzi operators and converts with a Job from quay.io/strimzi/operator:0.51.0, pinned by digest, so a cluster that cannot reach quay.io needs that image mirrored under the same name and digest before the run. Until the platform upgrade the operators stay stopped, so a broker pod that is evicted or deleted is not recreated, and the HelmRelease of every application moved to v4.3 reports a values error, because the old chart accepts only v3.8 and v3.9: upgrade the platform right after the run. Outside that image the script, packages/core/platform/images/migrations/migrations/61, needs the lib/ directory next to it and kubectl, jq, gzip and base64, plus STRIMZI_CRD_FILE pointing at strimzi-crds-0.51.0.yaml from the Strimzi 0.51.0 release.
Kafka 4 no longer accepts clients older than Kafka 2.1: upgrade such clients before the platform upgrade. Kafka 4 also removed the message.format.version, message.downconversion.enable and message.timestamp.difference.max.ms topic settings, and it requires segment.bytes of at least 1048576 (1 MiB) where Kafka 3.x accepted much smaller values; a broker whose log holds a topic below that does not start. The platform upgrade refuses to start while a Kafka application sets one of them, migration 61 also refuses while a KafkaTopic does, and the chart refuses to render such a topic, so remove the removed settings and raise segment.bytes in the config of every topic before the upgrade. A topic created through the Kafka admin API without a KafkaTopic is not visible to these checks.
No downgrade
Neither lowering the version field on a running cluster nor rolling the app back to an earlier chart is supported: Strimzi refuses an in-place downgrade of the KRaft metadata version, and an earlier chart renders resources for an operator API this platform no longer serves. Take a backup before upgrading.
Parameters
Common parameters
| Name | Description | Type | Value |
|---|---|---|---|
external |
Enable external access from outside the cluster. | bool |
false |
tls |
TLS configuration. Strimzi manages the cluster PKI automatically (no cert-manager is involved for this chart): the operator auto-creates <release>-cluster-ca-cert and <release>-clients-ca-cert secrets, both exposed for client trust setup. The internal TLS listener on 9093 is always on; this toggle only controls the external listener on 9094. |
object |
{} |
tls.enabled |
Enable TLS on the external listener. When unset, inherits the value of external (TLS is on when external access is enabled). Warning: setting this to false while external is true exposes Kafka over plaintext on a public IP via LoadBalancer. Strimzi does not provide authentication on this listener unless SCRAM, mTLS, or OAuth is separately configured. Use only in controlled networks. |
*bool |
null |
version |
Kafka version to deploy. Upgrade-only: once a cluster's KRaft metadata is at a given version, Strimzi refuses an in-place downgrade, so lowering this on a running cluster (e.g. v4.3 back to v4.2) leaves the Kafka CR stuck in a reconcile error. Pick the target version at creation and only ever raise it. | string |
v4.3 |
Application-specific parameters
| Name | Description | Type | Value |
|---|---|---|---|
topics |
Topics configuration. | []object |
[] |
topics[i].name |
Topic name. | string |
"" |
topics[i].partitions |
Number of partitions. | int |
0 |
topics[i].replicas |
Number of replicas. | int |
0 |
topics[i].config |
Topic configuration. | *object |
null |
Kafka configuration
| Name | Description | Type | Value |
|---|---|---|---|
kafka |
Kafka configuration. | object |
{} |
kafka.replicas |
Number of Kafka replicas. | int |
3 |
kafka.resources |
Explicit CPU and memory configuration. When omitted, the preset defined in resourcesPreset is applied. |
object |
{} |
kafka.resources.cpu |
CPU available to each replica. | quantity |
"" |
kafka.resources.memory |
Memory (RAM) available to each replica. | quantity |
"" |
kafka.resourcesPreset |
Default sizing preset used when resources is omitted. |
string |
c1.small |
kafka.size |
Persistent Volume size for Kafka. | quantity |
10Gi |
kafka.storageClass |
StorageClass used to store the Kafka data. | string |
"" |
kafka.controllerStorageSize |
Persistent Volume size for KRaft controller metadata. | quantity |
5Gi |
Parameter examples and reference
resources and resourcesPreset
resources sets explicit CPU and memory configurations for each replica.
Every resource it leaves unset is taken from the preset defined in resourcesPreset.
resources:
cpu: 4000m
memory: 4Gi
resourcesPreset sets named CPU and memory configurations for each replica.
This setting is ignored if the corresponding resources value is set.
Presets follow a cloud-style <series>.<size> naming convention. Five series cover the full CPU-to-memory ratio range (t1 1:0.5, c1 1:1, s1 1:2, u1 1:4, m1 1:8) and each series ships eight sizes (nano through 4xlarge). The legacy flat names (nano, micro, small, medium, large, xlarge, 2xlarge) remain accepted as deprecated aliases and keep their original sizes, which do not follow one series: nano through small equal the t1 sizes of the same name, while medium equals c1.small rather than c1.medium.
See Resource management for the full size matrix and the legacy-to-instance-type mapping.
topics
topics:
- name: Results
partitions: 1
replicas: 3
config:
min.insync.replicas: 2
- name: Orders
config:
cleanup.policy: compact
segment.ms: 3600000
max.compaction.lag.ms: 5400000
min.insync.replicas: 2
partitions: 1
replicas: 3