Update Helm release strimzi-kafka-operator to v0.42.0 #841
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/strimzi-kafka-operator-0.x
branch
from
997c1ed
to
c18ba8d
Compare
renovate
bot
force-pushed
the
renovate/strimzi-kafka-operator-0.x
branch
from
c18ba8d
to
9f6bc8f
Compare
|
We won't be updating this here and instead will move these services to the new Roundtable. |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.14.0->0.42.0Release Notes
strimzi/strimzi-kafka-operator (strimzi-kafka-operator)
v0.42.0Compare Source
UseKRaftfeature gate moves to GA stage and is permanently enabled without the possibility to disable it.To use KRaft (ZooKeeper-less Apache Kafka), you still need to use the
strimzi.io/kraft: enabledannotation on theKafkacustom resources or migrate from an existing ZooKeeper-based cluster.KafkaBridgeresource with consumer inactivity timeout and HTTP consumer/producer enablement.publishNotReadyAddresseson services for listener types other than internal.kafka-metrics.yamlexample file.strimziorkafkain theKafkacustom resource.The Strimzi Quotas plugin version was updated to 0.3.1.
Changes, deprecations and removals
reconciliationIntervalSecondsconfiguration for the Topic and User Operators is deprecated, and will be removed when upgrading schemas to v1.Use
reconciliationIntervalMsconverting the value to milliseconds.Additionally, from Strimzi 0.42.0 the plugin should be configured in
.spec.kafka.quotassection - the configuration of the plugin inside.spec.kafka.configis ignored and should be removed.v0.41.0Compare Source
Strimzi Operatorsdashboard to include certificate expiration per cluster.(Note: JBOD support in KRaft mode is considered early-access in Apache Kafka 3.7.x)
KafkaNodePoolsfeature gate moves to GA stage and is permanently enabled without the possibility to disable it.To use the Kafka Node Pool resources, you still need to use the
strimzi.io/node-pools: enabledannotation on theKafkacustom resources.externalIPsfield in node port type services.UnidirectionalTopicOperatorfeature gate moves to GA stage and is permanently enabled without the possibility to disable it.If the topics whose names start with
strimzi-store-topicandstrimzi-topic-operatorstill exist, you can delete them.AWS_MSK_IAM)strimzi.io/manual-rolling-updateannotation (when theContinueReconciliationOnManualRollingUpdateFailurefeature gate is enabled).Changes, deprecations and removals
tlsSidecarconfiguration for the Entity Operator is now deprecated and will be ignored.zookeeperSessionTimeoutSecondsandtopicMetadataMaxAttemptsconfigurations for the Entity Topic Operator have been removed and will be ignored.v0.40.0Compare Source
Remove support for Apache Kafka 3.5.0, 3.5.1, and 3.5.2.
UseKRaftfeature gate moves to beta stage and is enabled by default.If needed,
UseKRaftcan be disabled in the feature gates configuration in the Cluster Operator.offset.show-allparameterbrokerprocess role from KRaft mixed-nodes that have assigned partition-replicasChanges, deprecations and removals
Kubernetes 1.21 and 1.22 are not supported anymore.
This change brings our CRDs in-sync with the Kubernetes APIs.
After this fix, the label and annotation definitions in our CRDs (for example in the
templatesections) cannot contain integer values anymore and have to always use string values.If your custom resources use an integer value, for example:
template:
apiService:
metadata:
annotations:
discovery.myapigateway.io/port: 8080
You might get an error similar to this when applying the resource:
* spec.template.apiService.metadata.annotations.discovery.myapigateway.io/port: Invalid value: "integer": spec.template.apiService.metadata.annotations.discovery.myapigateway.io/port in body must be of type string: "integer"
To fix the issue, just use a string value instead of an integer:
template:
apiService:
metadata:
annotations:
discovery.myapigateway.io/port: "8080"
If you are upgrading from Strimzi 0.34 or earlier and have JmxTrans enabled in
.spec.jmxTransof theKafkacustom resource, you should disable it before the upgrade or delete it manually after the upgrade is complete.apimodule was refactored and classes were moved to new packages.It denies them instead of allowing them.
This new behavior does not require the
PodDisruptionBudgetto be set tomaxUnavailable: 0.We expect this to improve the compatibility with various tools used for scaling Kubernetes clusters such as Karpenter.
If you observe any problems with your toolchain or just want to stick with the previous behavior, you can use the
STRIMZI_DENY_EVICTIONenvironment variable and set it tofalseto switch back to the old (legacy) mode.v0.39.0Compare Source
StableConnectIdentitiesfeature gate moves to GA stage and is now permanently enabled without the possibility to disable it.All Connect and Mirror Maker 2 operands will now use StrimziPodSets.
KafkaNodePoolsfeature gate moves to beta stage and is enabled by default.If needed,
KafkaNodePoolscan be disabled in the feature gates configuration in the Cluster Operator.UnidirectionalTopicOperatorfeature gate moves to beta stage and is enabled by default.If needed,
UnidirectionalTopicOperatorcan be disabled in the feature gates configuration in the Cluster Operator.Changes, deprecations and removals
StableConnectIdentitiesfeature gate moves to GA stage and cannot be disabled anymore.When using Connect or Mirror Maker 2 operands, direct downgrade to Strimzi versions older than 0.34 is not supported anymore.
You have to first downgrade to Strimzi version between 0.34 to 0.38, disable the
StableConnectIdentitiesfeature gate, and only then downgrade to an older Strimzi version.From Strimzi 0.40.0 on, we will support only Kubernetes 1.23 and newer.
v0.38.0Compare Source
cosignstrimzi.io/manual-rolling-updateannotation (supported only whenStableConnectIdentitiesfeature gate is enabled)+UseKRaftfeature gate is enabledincludeAcceptHeaderoption to OAuth client and listener authentication configuration and tokeycloakauthorization. If set tofalseit turns off sending ofAcceptheader when communicating with OAuth / OIDC authorization server. This feature is enabled by the updated Strimzi Kafka OAuth library (0.14.0).Changes, deprecations and removals
Kafka.KafkaStatus.ListenerStatus.typeproperty has been deprecated for a long time, and now we do not use it anymore.The current plan is to completely remove this property in the next schema version.
If needed, you can use the
Kafka.KafkaStatus.ListenerStatus.nameproperty, which has the same value.strimzi.io/kraftannotation to be applied onKafkacustom resource, together with the+UseKRaftfeature gate enabled, to declare a ZooKeeper or KRaft based cluster.enabledtheKafkaresource defines a KRaft-based cluster.disabled, missing or any other value, the operator handle theKafkaresource as a ZooKeeper-based cluster.io.strimzi.kafka.EnvVarConfigProviderconfiguration provider is now deprecated and will be removed in Strimzi 0.42. Users should migrate to Kafka's implementation,org.apache.kafka.common.config.provider.EnvVarConfigProvider, which is a drop-in replacement.For example:
config:...
...
v0.37.0Compare Source
StableConnectIdentitesfeature gate moves to beta stage.By default, StrimziPodSets are used for Kafka Connect and Kafka Mirror Maker 2.
If needed,
StableConnectIdentitescan be disabled in the feature gates configuration in the Cluster Operator.ppc64leplatformKafkacustom resource status to track install and upgrade stateChanges, deprecations and removals
tracing.type: jaegerconfiguration, inKafkaConnect,KafkaMirrorMaker,KafkaMirrorMaker2andKafkaBridgeresources, is not supported anymore.tracing.type: opentelemetry.When the auto-restart feature is enabled in
KafkaConnectororKafkaMirrorMaker2custom resources, it will now continue to restart the connectors indefinitely rather than stopping after 7 restarts, as previously.If you want to use the original behaviour, use the
.spec.autoRestart.maxRestartsoption to configure the maximum number of restarts.For example:
...
...
v0.36.1Compare Source
v0.36.0Compare Source
Changes, deprecations and removals
Kubernetes 1.19 and 1.20 are not supported anymore.
UseKRaftfeature gate is now possible only together with theKafkaNodePoolsfeature gate.To deploy a Kafka cluster in the KRaft mode, you have to use the
KafkaNodePoolresources.https://strimzi.io/charts/is now deprecated.Please use the Helm Chart OCI artifacts from our Helm Chart OCI repository instead.
customClaimCheckof 'oauth' authentication which relies on JsonPath changed the handling of equal comparison againstnullas the behaviour was buggy and is now fixed in the updated version of JsonPath library OAuth #196v0.35.1Compare Source
Main changes since 0.35.0
Bug Fixes
Upgrading from Strimzi 0.35.0
See the documentation for upgrade instructions.
Upgrading from Strimzi 0.22 or earlier
Direct upgrade from Strimzi 0.22 or earlier is not supported anymore! You have to upgrade first to one of the previous versions of Strimzi. You will also need to convert the CRD resources. For more details, see the documentation.
Container images
The following container images are part of this release:
quay.io/strimzi/operator@sha256:06a94a3021cf028ccc1a49271f35f79216029e344536e664f196c1725ff2c663quay.io/strimzi/kafka@sha256:4de4874a7b722ad813f4dcc58acf509527bca0609999b81e70d81e3b38534d9dquay.io/strimzi/kafka@sha256:0d910e7138cb49e1cd8cd84cef88bce35698b93ddd683a3398f1d485a3162693quay.io/strimzi/kafka@sha256:54c6b25b31f51ef401c1b6e2a1b27432911e819bf3e502e05186f01be3f798e5quay.io/strimzi/kafka-bridge@sha256:d6be183e492f8f88157ab9fe0af53950df8b6711a8a8c33da465de6064f6f86equay.io/strimzi/kaniko-executor@sha256:39778b90c2b2afc30261e4ad5135805e1a10a2b60e2e53108fb9f80487f1208aquay.io/strimzi/maven-builder@sha256:88a79eff3b3a386880a630658964b7754caed9e99dd6e645a4c0d23d0fdb47eev0.35.0Compare Source
UseStrimziPodSetsto GA and remove support for StatefulSetsChanges, deprecations and removals
From Strimzi 0.36.0 on, we will support only Kubernetes 1.21 and newer.
If you have JMX Trans enabled in your
Kafkacustom resource in the.spec.jmxTranssection, you should remove it.If you upgrade to Strimzi 0.35.0 or newer with JMX Trans deployed / enabled in the
Kafkacustom resource, Strimzi will be automatically deleted after the upgrade.UseStrimziPodSetshas graduated to GA and cannot be disabled anymore.The StatefulSet template properties in the
Kafkacustom resource in.spec.zookeeper.template.statefulSetand.spec.kafka.template.statefulSetare deprecated and will be ignored.You should remove them from your custom resources.
v0.34.0Compare Source
StableConnectIdentities)httpRetriesandhttpRetryPauseMsoptions to OAuth authentication configuration. They are set to0by default - no retries, no backoff between retries. Also added analogoushttpRetriesoption in thekeycloakauthorization configuration. These features are enabled by the updated Strimzi Kafka OAuth library (0.12.0).v0.33.2Compare Source
Main changes since 0.33.1
Bug Fixes
v0.33.1Compare Source
Main changes since 0.33.0
Bug Fixes
Leaseresource from installation filesv0.33.0Compare Source
api,crd-generator,crd-annotations, andtestRecreatedeployment strategyImageStreamvalidation for Kafka Connect builds on OpenShiftKnown issues
If you use
type: ingresslistener with enabled mTLS authentication, we recommend you to test if your clients are affected or not.If needed, you can also disable the session ticket extension in the Kafka brokers in your
Kafkacustom resource by setting thejdk.tls.server.enableSessionTicketExtensionJava system property tofalse:...
spec:
...
...
ssl.secure.random.implementationoption in Kafka brokers was always set toSHA1PRNG.From Strimzi 0.33 on, it is using the default SecureRandom implementation from the Java Runtime.
If you want to keep using
SHA1PRNGas your SecureRandom, you can configure it in.spec.kafka.configin yourKafkacustom resource.It is currently planned to be removed in Strimzi 0.35.0.
type: jaegertracing based on Jaeger clients and OpenTracing API was deprecated in the Strimzi 0.31 release.As the Jaeger clients are retired and the OpenTracing project is archived, we cannot guarantee their support for future versions.
In Strimzi 0.32 and 0.33, we added support for OpenTelemetry tracing as a replacement.
If possible, we will maintain the support for
type: jaegertracing until June 2023 and remove it afterwards.Please migrate to OpenTelemetry as soon as possible.
The Jaeger exporter is even not included in the Kafka images anymore, so if you want to use it you have to add the binary by yourself.
The
OTEL_EXPORTER_OTLP_ENDPOINTenvironment variable has to be used instead of theOTEL_EXPORTER_JAEGER_ENDPOINTin order to specify the OTLP endpoint to send traces to.If you are using Jaeger as the backend system for tracing, you need to have 1.35 release at least which is the first one exposing an OTLP endpoint.
v0.32.0Compare Source
ControlPlaneListenerfeature gate moves to GAcluster-iplistener. We can use it with a tcp port configuration in an ingress controller to expose kafka with an optional tls encryption and a single LoadBalancer.Changes, deprecations and removals
ClusterRolefrom file020-ClusterRole-strimzi-cluster-operator-role.yamlwas split into two separate roles:strimzi-cluster-operator-namespacedClusterRolein the file020-ClusterRole-strimzi-cluster-operator-role.yamlcontains the rights related to the resources created based on some Strimzi custom resources.strimzi-cluster-operator-watchedClusterRolein the file023-ClusterRole-strimzi-cluster-operator-role.yamlcontains the rights required to watch and manage the Strimzi custom resources.When deploying the Strimzi Cluster Operator as cluster-wide, the
strimzi-cluster-operator-watchedClusterRoleneeds to be always granted at the cluster level.But the
strimzi-cluster-operator-namespacedClusterRolemight be granted only for the namespaces where any custom resources are created.ControlPlaneListenerfeature gate moves to GA.Direct upgrade from Strimzi 0.22 or earlier is not possible anymore.
You have to upgrade first to one of the Strimzi versions between 0.22 and 0.32 before upgrading to Strimzi 0.32 or newer.
Please follow the docs for more details.
spec.authorization.acls[*].operationfield in theKafkaUserresource has been deprecated in favour of the fieldspec.authorization.acls[*].operationswhich allows to set multiple operations per ACLRule.v0.31.1Compare Source
sasl.server.max.receive.sizebroker option user configurablev0.31.0Compare Source
Deprecations and removals
From Strimzi 0.32.0 on, we will support only Kubernetes 1.19 and newer.
The supported Kubernetes versions will be re-evaluated again in Q1/2023.
type: jaegertracing support based on Jaeger clients and OpenTracing API is now deprecated.Because the Jaeger clients are retired and the OpenTracing project is archived, we cannot guarantee their support for future Kafka versions.
In the future, we plan to replace it with a new tracing feature based on the OpenTelemetry project.
v0.30.0Compare Source
simpleauthorization and for the User Operator to the experimentalUseKRaftfeature gate(Note: Due to KAFKA-13909, broker restarts currently don't work when authorization is enabled.)
ServiceAccountPatchingfeature gate moves to GA.It cannot be disabled anymore and will be permanently enabled.
UseStrimziPodSetsfeature gate moves to beta stage.By default, StrimziPodSets are used instead of StatefulSets.
If needed,
UseStrimziPodSetscan be disabled in the feature gates configuration in the Cluster Operator.For existing clusters, the certificates will not be updated during upgrade but only next time the PKCS12 store is created.
v0.29.0Compare Source
/tmpvolumes to 5Mi to allow unpacking of compression libraries/healthzendpoint for Kafka Exporter health checksspec.rack.topologyKeyproperty in Mirror Maker 2 to enable "fetch from the closest replica" feature.(The s390x support is currently considered as experimental. We are not aware of any issues, but the s390x build doesn't at this point undergo the same level of testing as the AMD64 container images.)
KafkaRebalancecustom resourcefull: this mode runs a full rebalance moving replicas across all the brokers in the cluster. This is the default one if not specified.add-brokers: after scaling up the cluster, this mode is used to move replicas to the newly added brokers specified in the custom resource.remove-brokers: this mode is used to move replicas off the brokers that are going to be removed, before scaling down the cluster.UseKRaftfeature gate.Important: Use it for development and testing only!
Changes, deprecations and removals
.spec.cruiseControl.tlsSidecarand.spec.cruiseControl.template.tlsSidecarin the Kafka custom resource are now deprecated.v0.28.0Compare Source
StrimziPodSetresources (disabled by default through theUseStrimziPodSetsfeature gate)createBootstrapServicein the Kafka Spec to disable the creation of the bootstrap service for the Load Balancer Type Listener. It will save the cost of one load balancer resource, specially in the public cloud.connectTimeoutSecondsandreadTimeoutSecondsoptions to OAuth authentication configuration. The default connect and read timeouts are set to 60 seconds (previously there was no timeout). Also addedgroupsClaimandgroupsClaimDelimiteroptions in the listener configuration of Kafka Spec to allow extracting group information from JWT token at authentication time, and making it available to the custom authorizer. These features are enabled by the updated Strimzi Kafka OAuth library (0.10.0).Changes, deprecations and removals
io.strimzi.kafka.connect.mirror.IdentityReplicationPolicy) is now deprecated and will be removed in the future.Please update to Kafka's own Identity Replication Policy (class
org.apache.kafka.connect.mirror.IdentityReplicationPolicy).typefield inListenerStatushas been deprecated and will be removed in the future.diskandcpuUtilizationfields in thespec.cruiseControl.capacitysection of the Kafka resource have been deprecated, are ignored, and will be removed in the future.v0.27.1Compare Source
Main changes since 0.27.0
All changes can be found under the 0.27.1 milestone.
Upgrading from previous Strimzi versions
See the documentation for upgrade instructions.
Upgrading from Strimzi 0.22 or earlier
This release supports only the API version
v1beta2and CRD versionapiextensions.k8s.io/v1. If upgrading from Strimzi 0.22, migration tov1beta2needs to be completed for all Strimzi CRDs and CRs before the upgrade to 0.27 is done! If upgrading from Strimzi version earlier than 0.22, you need to first install the CRDs from Strimzi 0.22 and complete the migration tov1beta2for all Strimzi CRDs and CRs before the upgrade to 0.27 is done!For more details about the CRD upgrades, see the documentation.
v0.27.0Compare Source
(The support AArch64 is currently considered as experimental. We are not aware of any issues, but the AArch64 build doesn't at this point undergo the same level of testing as the AMD64 container images.)
STRIMZI_ZOOKEEPER_ADMIN_SESSION_TIMEOUT_MSControlPlaneListenerandServiceAccountPatchingfeature gates are now in the beta phase and are enabled by default.extraEnvsvalue.Changes, deprecations and removals
ControlPlaneListenerfeature gate is now enabled by default.When upgrading from Strimzi 0.22 or earlier, you have to disable the
ControlPlaneListenerfeature gate when upgrading the cluster operator to make sure the Kafka cluster stays available during the upgrade.When downgrading to Strimzi 0.22 or earlier, you have to disable the
ControlPlaneListenerfeature gate before downgrading the cluster operator to make sure the Kafka cluster stays available during the downgrade.v0.26.1Compare Source
Main changes since 0.26.0
v0.26.0Compare Source
/tmpvolume size via Pod template. By default1Miis used.Changes, deprecations and removals
As a result, the
KafkaMirrorMakercustom resource which is used to deploy Kafka MirrorMaker 1 has been deprecated in Strimzi as well. (#5617)The
KafkaMirrorMakerresource will be removed from Strimzi when we adopt Apache Kafka 4.0.0.As a replacement, use the
KafkaMirrorMaker2custom resource with theIdentityReplicationPolicy.v0.25.0Compare Source
KafkaUserresourcetls-externalauthentication to User Operator to allow management of ACLs and Quotas for TLS users with user certificates generated externally (#5249)STRIMZI_NETWORK_POLICY_GENERATIONenvironment variable tofalseto disable network policies. (#5258)emptyDirvolumes used for temporary files (#5340)Changes, deprecations and removals
KafkaConnectS2Iresource has been removed and is no longer supported by the operator.Please use the migration guide to migrate your
KafkaConnectS2Ideployments toKafkaConnectBuild instead.The new release introduces a new format of the input data sent to the Open Policy Agent server.
For more information about the new format and how to migrate from the old version, see the OPA Kafka plugin v1.0.0 release notes.
All operations done by the User Operator now use Kafka Admin API and connect directly to Kafka instead of ZooKeeper.
As a result, the environment variables
STRIMZI_ZOOKEEPER_CONNECTandSTRIMZI_ZOOKEEPER_SESSION_TIMEOUT_MSwere removed from the User Operator configuration.emptyDirvolumes used by Strimzi for temporary files have now configured a fixed size limit.v0.24.0Compare Source
ServiceAccountPatchingfeature gate.strimzi.io/pause-reconciliationChanges, deprecations and removals
KafkaConnectS2Icustom resource will be removed after the 0.24.0 release.Please use the migration guide to migrate your
KafkaConnectS2Ideployments toKafkaConnectBuild instead.topicsBlacklistPatternandgroupsBlacklistPatternin theKafkaMirrorMaker2resource are deprecated and will be removed in the future.They are replaced by new fields
topicsExcludePatternandgroupsExcludePattern.whitelistin theKafkaMirrorMakerresource is deprecated and will be removed in the future.It is replaced with a new field
include.bind-utilsremoved from containers to improve security posture.If your artifact requires a specific name, you can use the new
type: otherartifact and itsfileNamefield.enableECDSAof Kafka CRauthenticationof typeoauthhas been deprecated and is ignored.ECDSA token signature support is now always enabled without the need for Strimzi Cluster Operator installing the BouncyCastle JCE crypto provider.
BouncyCastle library is no longer packaged with Strimzi Kafka images.
v0.23.0Compare Source
loadbalancertype listenersControlPlaneListenerfeature gate)Changes, deprecations and removals
v1alpha1andv1beta1were removed from all Strimzi custom resources apart fromKafkaTopicandKafkaUser(usev1beta2versions instead)cluster.operator.strimzi.io/delete-claim(used internally only - replaced bystrimzi.io/delete-claim)operator.strimzi.io/generation(used internally only - replaced bystrimzi.io/generation)operator.strimzi.io/delete-pod-and-pvc(usestrimzi.io/delete-pod-and-pvcinstead)operator.strimzi.io/manual-rolling-update(usestrimzi.io/manual-rolling-updateinstead)classfield is configured in theconfigurationsection of an Ingress-type listener, Strimzi will not automatically set the deprecatedkubernetes.io/ingress.classannotation anymore. In case you still need this annotation, you can set it manually in the listener configuration using theannotationsfield or in the.spec.kafka.templatesection..spec.kafkaExporter.template.servicesection in theKafkacustom resource has been deprecated and will be removed in the next API version (the service itself was removed several releases ago).v0.22.1Compare Source
Main changes since 0.22.0
See the 0.22.0 release for information about CRD upgrades, deprecations and removals.
Upgrading from Strimzi 0.21.x and 0.22.0
See the documentation for upgrade instructions.
v0.22.0Compare Source
v1beta2version for all resources.v1beta2removes all deprecated fields.ConfigMapname and key..statussection of theKafkaConnectorcustom resourceLog4j 2and is supported by dynamic logging configuration (where logging properties are defined in a ConfigMap). However, existingLog4jconfigurations must be updated toLog4j 2configurations.strimzi.io/pause-reconciliationChanges, deprecations and removals
In the past, when no Ingress class was specified in the Ingress-type listener in the Kafka custom resource, the
kubernetes.io/ingress.classannotation was automatically set tonginx. Because of the support for the newIngressClass resource and the new
ingressClassNamefield in the Ingress resource, the default value will not be setanymore. Please use the
classfield in.spec.kafka.listeners[].configurationto specify the class name.The
KafkaConnectS2Icustom resource is deprecated and will be removed in the future. You can use the newKafkaConnectbuild feature instead.Removed support for Helm2 charts as that version is now unsupported. There is no longer the need for separate
helm2andhelm3binaries, onlyhelm(version 3) is required.The following annotations are deprecated for a long time and will be removed in 0.23.0:
cluster.operator.strimzi.io/delete-claim(used internally only - replaced bystrimzi.io/delete-claim)operator.strimzi.io/generation(used internally only - replaced bystrimzi.io/generation)operator.strimzi.io/delete-pod-and-pvc(usestrimzi.io/delete-pod-and-pvcinstead)operator.strimzi.io/manual-rolling-update(usestrimzi.io/manual-rolling-updateinstead)External logging configuration has changed.
spec.logging.nameis deprecated. Moved tospec.logging.valueFrom.configMapKeyRef.name. Key in theConfigMapis configurable viaspec.logging.valueFrom.configMapKeyRef.key.Existing Cruise Control logging configurations must be updated from
Log4jsyntax toLog4j 2syntax.cruisecontrol.root.loggerproperty withrootLogger.level.Configuration
📅 Schedule: Branch creation - "before 6am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.