Bump strimzi-test-container from 0.22.1 to 0.23.0

[dependabot]

Bumps strimzi-test-container from 0.22.1 to 0.23.0.

Release notes

Sourced from strimzi-test-container's releases.

0.23.0-rc1

Main changes since 0.22

• Add support for Kafka 2.8.0 and 2.6.2, remove support for Kafka 2.5.x
• Make it possible to configure maximum number of connections and maximum connection creation rate in listener configuration
• Add support for configuring finalizers for loadbalancer type listeners
• Use dedicated Service Account for Kafka Connect Build on Kubernetes
• Remove direct ZooKeeper access for handling user quotas in the User Operator. Add usage of Admin Client API instead.
• Migrate to CRD v1 (required by Kubernetes 1.22+)
• Support for configuring custom Authorizer implementation
• Changed Reconciliation interval for Topic Operator from 90 to 120 seconds (to keep it the same as for other operators)
• Changed Zookeeper session timeout default value to 18 seconds for Topic and User Operators (for improved resiliency)
• Removed requirement for replicas and partitions KafkaTopic spec making these parameters optional
• Support to configure a custom filter for parent CR's labels propagation into subresources
• Allow disabling service links (environment variables describing Kubernetes services) in Pod template
• Update Kaniko executor to 1.6.0
• Add support for separate control plane listener (disabled by default, available via the ControlPlaneListener feature gate)
• Support for Dual Stack networking

All changes can be found under the 0.23.0 milestone.

CRD Upgrades

!!! IMPORTANT !!!

This release supports only the API version v1beta2 and CRD version apiextensions.k8s.io/v1. Migration to v1beta2 needs to be completed for all Strimzi CRDs and CRs before the upgrade to 0.23 is done!

For more details about the CRD upgrades, see the documentation.

Changes, deprecations and removals

• Strimzi API versions v1alpha1 and v1beta1 were removed from all Strimzi custom resources apart from KafkaTopic and KafkaUser (use v1beta2 versions instead)
• The following annotations have been removed and cannot be used anymore:
  • cluster.operator.strimzi.io/delete-claim (used internally only - replaced by strimzi.io/delete-claim)
  • operator.strimzi.io/generation (used internally only - replaced by strimzi.io/generation)
  • operator.strimzi.io/delete-pod-and-pvc (use strimzi.io/delete-pod-and-pvc instead)
  • operator.strimzi.io/manual-rolling-update (use strimzi.io/manual-rolling-update instead)
• When the class field is configured in the configuration section of an Ingress-type listener, Strimzi will not automatically set the deprecated kubernetes.io/ingress.class annotation anymore. In case you still need this annotation, you can set it manually in the listener configuration using the annotations field or in the .spec.kafka.template section.
• The .spec.kafkaExporter.template.service section in the Kafka custom resource has been deprecated and will be removed in the next API version (the service itself was removed several releases ago).

Upgrading from Strimzi 0.22

See the documentation for upgrade instructions.

Changelog

Sourced from strimzi-test-container's changelog.

0.23.0

• Add support for Kafka 2.8.0 and 2.6.2, remove support for Kafka 2.5.x
• Make it possible to configure maximum number of connections and maximum connection creation rate in listener configuration
• Add support for configuring finalizers for loadbalancer type listeners
• Use dedicated Service Account for Kafka Connect Build on Kubernetes
• Remove direct ZooKeeper access for handling user quotas in the User Operator. Add usage of Admin Client API instead.
• Migrate to CRD v1 (required by Kubernetes 1.22+)
• Support for configuring custom Authorizer implementation
• Changed Reconciliation interval for Topic Operator from 90 to 120 seconds (to keep it the same as for other operators)
• Changed Zookeeper session timeout default value to 18 seconds for Topic and User Operators (for improved resiliency)
• Removed requirement for replicas and partitions KafkaTopic spec making these parameters optional
• Support to configure a custom filter for parent CR's labels propagation into subresources
• Allow disabling service links (environment variables describing Kubernetes services) in Pod template
• Update Kaniko executor to 1.6.0
• Add support for separate control plane listener (disabled by default, available via the ControlPlaneListener feature gate)
• Support for Dual Stack networking

Changes, deprecations and removals

• Strimzi API versions v1alpha1 and v1beta1 were removed from all Strimzi custom resources apart from KafkaTopic and KafkaUser (use v1beta2 versions instead)
• The following annotations have been removed and cannot be used anymore:
  • cluster.operator.strimzi.io/delete-claim (used internally only - replaced by strimzi.io/delete-claim)
  • operator.strimzi.io/generation (used internally only - replaced by strimzi.io/generation)
  • operator.strimzi.io/delete-pod-and-pvc (use strimzi.io/delete-pod-and-pvc instead)
  • operator.strimzi.io/manual-rolling-update (use strimzi.io/manual-rolling-update instead)
• When the class field is configured in the configuration section of an Ingress-type listener, Strimzi will not automatically set the deprecated kubernetes.io/ingress.class annotation anymore. In case you still need this annotation, you can set it manually in the listener configuration using the annotations field or in the .spec.kafka.template section.
• The .spec.kafkaExporter.template.service section in the Kafka custom resource has been deprecated and will be removed in the next API version (the service itself was removed several releases ago).

0.22.0

• Add v1beta2 version for all resources. v1beta2 removes all deprecated fields.
• Add annotations that enable the operator to restart Kafka Connect connectors or tasks. The annotations can be applied to the KafkaConnector and the KafkaMirrorMaker2 custom resources.
• Add additional configuration options for the Kaniko executor used by the Kafka Connect Build on Kubernetes
• Add support for JMX options configuration of all Kafka Connect (KC, KC2SI, MM2)
• Update Strimzi Kafka OAuth to version 0.7 and add support for new features:
  • OAuth authentication over SASL PLAIN mechanism
  • Checking token audience
  • Validating tokens using JSONPath filter queries to perform custom checks
• Fix Cruise Control crash loop when updating container configurations
• Configure external logging ConfigMap name and key.
• Add support for configuring labels and annotations in ClusterRoleBindings created as part of Kafka and Kafka Connect clusters
• Add support for Ingress v1 in Kubernetes 1.19 and newer
• Add support for Kafka 2.6.1
• List topics used by a Kafka Connect connector in the .status section of the KafkaConnector custom resource
• Bump Cruise Control to v2.5.37 for Kafka 2.7 support. Note this new version of Cruise Control uses Log4j 2 and is supported by dynamic logging configuration (where logging properties are defined in a ConfigMap). However, existing Log4j configurations must be updated to Log4j 2 configurations.
• Support pausing reconciliation of CR with annotation strimzi.io/pause-reconciliation

Changes, deprecations and removals

... (truncated)

Commits

• 5315369 Prepare for 0.23.0 release
• b264a4d [DOC] Use PKCS12 files directly when configuring client access from outside K...
• e717422 [DOC] Update the upgrade steps to split version updates (#4834)
• b097922 Revert " [MO] - [unit + integration co tests] -> method wide parallelism (#48...
• c006f03 [DOC] Update external configuration to include DirectoryConfigProvider (#4841)
• 1fccfd7 [DOC] Update Helm upgrade docs (#4929)
• 847083b Improve azp and apply some fixes for regression and helm pipelines (#4935)
• 9a02329 split kafka clusters to seperate namespaces (#4925)
• 681e758 [DOC] Add ControlPlaneListener feature gate documentation (#4918)
• 4e614e4 [MO] - [unit + integration co tests] -> method wide parallelism (#4860)
• Additional commits viewable 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)