chore(deps): bump strimzi/kafka from 1.2.0-kafka-4.3.1 to 1.3.0-kafka-4.3.1

[dependabot]

Warning

Cooldown could not be applied because no publication date was available from the registry.

Bumps strimzi/kafka from 1.2.0-kafka-4.3.1 to 1.3.0-kafka-4.3.1.

Release notes

Sourced from strimzi/kafka's releases.

1.3.0-rc1

⚠️ Important: Strimzi 1.3.0 supports only Kubernetes 1.32 and newer. Kubernetes 1.30 and 1.31 are not supported anymore.

⚠️ ⚠️ ⚠️ Important: From Strimzi 1.0.0, the only supported version of CRD API is v1. The older v1beta2, v1beta1, and v1alpha1 APIs are no longer supported. Before upgrading to Strimzi 1.0.0 and above, make sure to convert all custom resources and upgrade the CRDs.

---

Main Changes Since 1.2.0

The most important new features are:

• (Early Access) Configurable internal cluster security allows users to configure encryption and authentication on the internal connections within the Apache Kafka cluster.
• Add support for Kafka 4.2.2.
• Update Kafka Exporter to 1.10.0.
• Support for mounting projected service account tokens into Strimzi-managed Pods.
• The UseConnectBuildWithBuildah feature gate moves to GA stage, is enabled by default without option to be disabled.
• The UseBackgroundPodDeletion feature gate moves to beta stage and is enabled by default. If needed, UseBackgroundPodDeletion can be disabled in the feature gates configuration in the Cluster Operator.
• (Early Access) Integration with cert-manager for issuing certificates. While the cert-manager feature is in Early Access it is not recommended for use in production.
• Updated HTTP Bridge to 1.2.0
• Add fenced brokers, offline replicas and ISR shrink/expand/failed update panels to the example Kafka Grafana dashboards

Major changes, deprecations, and removals

• PKCS12 format certificates are deprecated. The STRIMZI_PKCS12_KEYSTORE_GENERATION env var will be set to false by default in a future release.
• Kaniko is removed and Buildah is the only tool used for building Connect images.

All changes can be found under the 1.3.0 milestone or in the CHANGELOG.md.

Upgrading from Strimzi 1.2.0

See the documentation for upgrade instructions.

Maven Artifacts

To test the Maven artifacts that are part of this release, use the 1.3.0 version in your pom.xml.

Container Images

The following container images are part of this release:

Name	Image
Operators	quay.io/strimzi/operator@sha256:f6b0ace76ff8b22db333e2ff4709729edb0e118ee8c6c766f7a096dc30c56acd
Apache Kafka 4.2.0	quay.io/strimzi/kafka@sha256:fa16760ef0625d2ad4563f0379a87176408059d2c88ef140425d3672f35d7fb6
Apache Kafka 4.2.1	quay.io/strimzi/kafka@sha256:8e915aabba9f813a583b49e705a28f83d500dc18137c8417e33adbadc2450cc3
Apache Kafka 4.2.2	quay.io/strimzi/kafka@sha256:092e4ab3bc5c76c00c387aa52dcdec083b9ec5df35370d7e71181f7e9dda1f85

... (truncated)

Changelog

Sourced from strimzi/kafka's changelog.

CHANGELOG

1.4.0

• Use ubi9-micro as a base image for operators, kafka-based, and maven-builder images.
• Strimzi Drain Cleaner updated to 1.7.0 (included in the Strimzi installation files)

Major changes, deprecations, and removals

• The Prometheus JMX Exporter configuration from the metrics ConfigMap is now parsed as YAML 1.2 (using the Core schema) instead of YAML 1.1. Unquoted yes, no, on, and off values are not converted to booleans anymore and are passed to the JMX Exporter as strings. The JMX Exporter fails to start when these values are used for boolean options such as lowercaseOutputName, which prevents the container from starting. Before upgrading, make sure your metrics configuration uses true and false for boolean values.

1.3.0

• (Early Access) Configurable internal cluster security allows users to configure encryption and authentication on the internal connections within the Apache Kafka cluster.
• Add support for Kafka 4.2.2
• Update Kafka Exporter to 1.10.0
• Support for mounting projected service account tokens into Strimzi-managed Pods
• The UseConnectBuildWithBuildah feature gate moves to GA stage, is enabled by default without option to be disabled
• The UseBackgroundPodDeletion feature gate moves to beta stage and is enabled by default. If needed, UseBackgroundPodDeletion can be disabled in the feature gates configuration in the Cluster Operator.
• (Early Access) Integration with cert-manager for issuing certificates. While the cert-manager feature is in Early Access it is not recommended for use in production.
• Updated HTTP Bridge to 1.2.0
• Add fenced brokers, offline replicas and ISR shrink/expand/failed update panels to the example Kafka Grafana dashboards

Major changes, deprecations, and removals

• From Strimzi 1.3.0 on, we support only Kubernetes 1.32 and newer. Kubernetes 1.30 and 1.31 are not supported anymore.
• PKCS12 format certificates are deprecated. The STRIMZI_PKCS12_KEYSTORE_GENERATION env var will be set to false by default in a future release and then eventually removed completely. Once removed, the CA certificate Secrets and User Secrets will only contain certificates in the PEM format.

1.2.0

• Add support for Apache Kafka 4.3.1
• Support templated (per-pod) additional volumes for Kafka, Kafka Connect and Kafka MirrorMaker 2 operands
• Stop auto-mounting Service Account tokens into Pods and mount them through a volume instead
• The ServerSideApplyPhase1 feature gate moves to GA stage and is permanently enabled without the possibility to disable it.
• Support for configuring Maven mirrors for Kafka Connect Build
• Connectors that request the stopped or paused state via spec.state are now created directly in that state instead of being started first and then stopped or paused.
• Added support for broker cordoning KIP-1066 during auto-rebalancing on scale down for Kafka 4.3+.
• Removed deprecated resource state metrics - the KSM (kube-state-metrics) should be used instead.
• Update Strimzi metrics-reporter to 0.4.0
• Update strimzi-kafka-oauth to 0.18.0

Major changes, deprecations, and removals

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)