chore(deps): update dependency strimzi/strimzi-kafka-operator to v0.49.0 - abandoned #61
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.48.0->0.49.0Release Notes
strimzi/strimzi-kafka-operator (strimzi/strimzi-kafka-operator)
v0.49.0Compare Source
blockOwnerDeletiontotruein the owner references in Strimzi managed resources.Deleting the Strimzi custom resources will now by default wait for the deletion of all the owned Kubernetes resources.
v1API to Strimzi CRDs and move User and Topic Operators to use it.The
v1APi Conversion Tool can be used to convert the resources in files or in your Kubernetes cluter from thev1beta2API to thev1API..specsections required in thev1version of all Strimzi custom resources..spec.replicasproperties required in thev1of theKafkaBridge,KafkaConnect, andKafkaMirrorMaker2custom resources..spec.groupId,.spec.configStorageTopic,.spec.offsetStorageTopic, and.spec.statusStorageTopicin theKafkaConnectcustom resource for configuring Connect's group ID and internal topics..spec.target) and source clusters (.spec.mirrors[].source) in theKafkaMirrorMaker2custom resources.KafkaandKafkaNodePooltemplatesections.The templates are now merged at a property level.
If two different properties are defined in the two
templatesections, both are applied.If the same property is defined in both
templatesections, only the property from theKafkaNodePooltemplate is used.See the Strimzi Proposal 120 for more details.
UseConnectBuildWithBuildah(disabled by default) for running the Connect Build feature with Buildah instead of Kaniko on Kubernetes - according to Strimzi Proposal #114.spec.versionin theKafkaConnectercustom resource, and newversionfields for each connector underspec.mirrors[]in theKafkaMirrorMaker2custom resource for configuring the desired version of a connector..volumeAttributesClassforpersistent-claimtype Storage inKafkaandKafkaNodePoolcustom resource. Enables configuringVolumeAttributesClassforPersistentVolumeClaims available since Kubernetes v1.34.KeycloakAuthorizerissue on Kafka 4.1.0Major changes, deprecations, and removals
Before upgrading to Strimzi 0.49 or newer, make sure that you update your
KafkaUserresources to use the.spec.authorization.acls[]operationsfield instead of the deprecated.spec.authorization.acls[]operation.Especially when using Helm, make sure that the CRDs are updated when you upgrade the operator.
Kafkacustom resource (.spec.kafka.rack), Strimzi will not automatically add the best-effort-affinity rules for spreading the Kafka Pods between the zones.Please make sure to set your own
topologySpreadConstraintoraffinityrules instead..status.kafkaMetadataStatefield in theKafkacustom resource is deprecated and not used anymore.type: oauthauthentication in Kafka brokers and Kafka clients (Kafka Connect, MirrorMaker 2, and Strimzi HTTP Bridge) has been deprecated.Please use the
type: customauthentication instead.The Strimzi OAuth library continues to be packaged with the Strimzi container images.
Follow the documentation for the examples and migration details.
type: keycloak) has been deprecated and will be removed in the future.To use the Keycloak authorizer, you can use the
type: customauthorization.The Strimzi OAuth library with the Keycloak authorizer continues to be packaged with the Strimzi container images.
Follow the documentation for the examples and migration details.
.spec.kafka.resourcesis deprecated and will be removed in thev1CRD API.Please use the
KafkaNodePoolresources to configure CPU and memory for Kafka nodes.group.id,config.storage.topic,offset.storage.topic, andstatus.storage.topicfields in.spec.configsection of theKafkaConnectresource are deprecated and will be forbidden in thev1CRD API.Please use the new
.spec.groupId,.spec.configStorageTopic,.spec.offsetStorageTopic, and.spec.statusStorageTopicfields instead..spec.connectCluster,.spec.clusters,.spec.mirrors[].sourceCluster,.spec.mirrors[].targetCluster, and.spec.mirrors[].heartbeatConnectorfields of theKafkaMirrorMaker2resource are deprecated and will be removed in thev1CRD API.Please use the new fields
.spec.targetand.spec.mirrors[].sourceinstead to configure the source and target clusters.If you want to deploy and run the Heartbeat connector, you can use separate
KafkaConnectandKafkaConnectorcustom resources..spec.build.output.additionalKanikoOptionsfield in theKafkaConnectcustom resource is deprecated and will be removed in the future..spec.build.output.additionalBuildOptionsfield instead.templateproperties in theKafkaandKafkaNodePoolresources are handled has changed.See the 0.49.0 section or the Strimzi Proposal 120 for more details.
connector.plugin.versionunderspec.configin theKafkaConnectorcustom resource, and underspec.mirrors[].sourceConnector.config,spec.mirrors[].checkpointConnector.config, andspec.mirrors[].heartbeatConnector.configin theKafkaMirrorMaker2custom resource is deprecated and will be forbidden in Strimzi 0.50.0.Instead, please use
spec.versionin theKafkaConnectercustom resource, and the connector specificversionfields in theKafkaMirrorMaker2custom resource.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Renovate Bot.