[Snyk] Security upgrade io.strimzi:api from 0.16.2 to 0.30.0

[snyk-io]

Snyk has created this PR to fix 3 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• debezium-testing/debezium-testing-openshift/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-IONETTY-18170202	170	io.strimzi:api: 0.16.2 -> 0.30.0 No Path Found Proof of Concept
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-IONETTY-18170204	170	io.strimzi:api: 0.16.2 -> 0.30.0 No Path Found Proof of Concept
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-IONETTY-18170213	125	io.strimzi:api: 0.16.2 -> 0.30.0 No Path Found No Known Exploit

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[snyk-io]

This major version upgrade from 0.16.2 to 0.30.0 spans multiple significant releases and includes mandatory Custom Resource Definition (CRD) API version changes.

Key Breaking Changes:

• CRD API Version Upgrade: Strimzi 0.23.0 and newer versions exclusively support the v1beta2 API version for all Strimzi custom resources. The v1alpha1 and v1beta1 versions, used in older releases like 0.16.2, are no longer supported. All existing Strimzi custom resources (like Kafka, KafkaTopic, KafkaUser, etc.) must be migrated to the v1beta2 API version before upgrading the operator to 0.23.0 or later.
• StrimziPodSets: Starting from version 0.30.0, Strimzi uses StrimziPodSets by default instead of StatefulSets to manage Kafka broker pods. This feature gate was moved to beta and enabled by default.
• Configuration Changes: Deprecated properties have been removed in the v1beta2 API. For example, listener configuration is now array-based, and metrics configuration has a new format.

Recommendation:
This upgrade cannot be performed directly without careful planning and execution. A multi-step upgrade process is required. You must first upgrade to an intermediate Strimzi version (like 0.22.x) that supports both old and new API versions to perform the CRD migration, before finally upgrading to 0.30.0. Review the official Strimzi upgrade documentation for the specific steps to migrate your CRDs from v1alpha1/v1beta1 to v1beta2.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.