Upgrade: Bump io.strimzi:api from 0.39.0 to 0.40.0

[dependabot]

Bumps io.strimzi:api from 0.39.0 to 0.40.0.

Release notes

Sourced from io.strimzi:api's releases.

0.40.0

⚠️ Important: From Strimzi 0.40 on, we support only Kubernetes 1.23 and newer. Kubernetes versions 1.21 and 1.22 are no longer supported.

Main changes since 0.39.0

This release contains the following new features and improvements:

• Add support for Apache Kafka 3.7.0. Remove support for Apache Kafka 3.5.0, 3.5.1, and 3.5.2.
• The UseKRaft feature gate moves to beta stage and is enabled by default. If needed, UseKRaft can be disabled in the feature gates configuration in the Cluster Operator.
• Add support for ZooKeeper to KRaft migration by enabling the users to move from using ZooKeeper to store metadata to KRaft.
• Add support for moving from dedicated controller-only KRaft nodes to mixed KRaft nodes
• Added support for Kafka Exporter offset.show-all parameter
• Prevent removal of the broker process role from KRaft mixed-nodes that have assigned partition-replicas
• Improve broker scale-down prevention to continue in reconciliation when scale-down cannot be executed
• Added support for Tiered Storage by enabling the configuration of custom storage plugins through the Kafka custom resource.
• Update HTTP bridge to the latest 0.28.0 release

All changes can be found under the 0.40.0 milestone.

Watch out also for some notable changes, deprecations, and removals:

• From Strimzi 0.40.0 on, we support only Kubernetes 1.23 and newer. Kubernetes 1.21 and 1.22 are not supported anymore.
• #9508 fixes the Strimzi CRDs and their definitions of labels and annotations. 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 template sections) 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"
  

• Support for the JmxTrans component is now completely removed. If you are upgrading from Strimzi 0.34 or earlier and have JmxTrans enabled in .spec.jmxTrans of the Kafka custom resource, you should disable it before the upgrade or delete it manually after the upgrade is complete.
• The api module was refactored and classes were moved to new packages.
• Strimzi Drain Cleaner 1.1.0 (included in the Strimzi 0.40.0 installation files) changes the way it handles Kubernetes eviction requests. It denies them instead of allowing them. This new behavior does not require the PodDisruptionBudget to be set to maxUnavailable: 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_EVICTION environment variable and set it to false to switch back to the old (legacy) mode.

Upgrading from Strimzi 0.39.0

See the documentation for upgrade instructions.

... (truncated)

Changelog

Sourced from io.strimzi:api's changelog.

0.40.0

• Add support for Apache Kafka 3.7.0. Remove support for Apache Kafka 3.5.0, 3.5.1, and 3.5.2.
• The UseKRaft feature gate moves to beta stage and is enabled by default. If needed, UseKRaft can be disabled in the feature gates configuration in the Cluster Operator.
• Add support for ZooKeeper to KRaft migration by enabling the users to move from using ZooKeeper to store metadata to use KRaft.
• Add support for moving from dedicated controller-only KRaft nodes to mixed KRaft nodes
• Fix NullPointerException from missing listenerConfig when using custom auth
• Added support for Kafka Exporter offset.show-all parameter
• Prevent removal of the broker process role from KRaft mixed-nodes that have assigned partition-replicas
• Improve broker scale-down prevention to continue in reconciliation when scale-down cannot be executed
• Added support for Tiered Storage by enabling the configuration of custom storage plugins through the Kafka custom resource.
• Update HTTP bridge to latest 0.28.0 release

Changes, deprecations and removals

• From Strimzi 0.40.0 on, we support only Kubernetes 1.23 and newer. Kubernetes 1.21 and 1.22 are not supported anymore.
• #9508 fixes the Strimzi CRDs and their definitions of labels and annotations. 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 template sections) 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"
  

• Support for the JmxTrans component is now completely removed. If you are upgrading from Strimzi 0.34 or earlier and have JmxTrans enabled in .spec.jmxTrans of the Kafka custom resource, you should disable it before the upgrade or delete it manually after the upgrade is complete.
• The api module was refactored and classes were moved to new packages.
• Strimzi Drain Cleaner 1.1.0 (included in the Strimzi 0.40.0 installation files) changes the way it handles Kubernetes eviction requests. It denies them instead of allowing them. This new behavior does not require the PodDisruptionBudget to be set to maxUnavailable: 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_EVICTION environment variable and set it to false to switch back to the old (legacy) mode.

Commits

• 1b5ce12 Prepare for 0.40.0 release
• 7d774f0 Updated bridge to 0.28.0 (#9787)
• 69f095e Update Kaniko to 1.21.1 (#9800)
• df3985e Fix wrong escaping of OAuth configuration in Mirror Maker 2 (#9799)
• 73dba1b [ST] Disable flaky assertNoCoErrorsLogged (#9797)
• 9bb6b31 [ST] Update test-clients to 0.7.0 after the release (#9785)
• 7058ee2 [ST] Add NetworkPolicies for OpenTelemetryST when running on OCP (#9793)
• e88ce87 [ST] AZP - Make it possible to run tests on main branch without building imag...
• bafba34 Update OAuth library version to 0.15.0 (#9774)
• ee322a5 Remove Kotlin from third party libs. (#9758)
• 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 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.