[Snyk] Security upgrade io.kubernetes:client-java from 17.0.2 to 22.0.1-legacy

[caniszczyk]

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

Snyk changed the following file(s):

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Improper Certificate Validation SNYK-JAVA-ORGBOUNCYCASTLE-18519194	751	io.kubernetes:client-java: 17.0.2 -> 22.0.1-legacy No Known Exploit
	Uncontrolled Recursion SNYK-JAVA-ORGBOUNCYCASTLE-18519010	721	io.kubernetes:client-java: 17.0.2 -> 22.0.1-legacy No Known Exploit
	Improper Validation of Integrity Check Value SNYK-JAVA-ORGBOUNCYCASTLE-18519127	721	io.kubernetes:client-java: 17.0.2 -> 22.0.1-legacy No Known Exploit
	Improper Validation of Integrity Check Value SNYK-JAVA-ORGBOUNCYCASTLE-18519148	721	io.kubernetes:client-java: 17.0.2 -> 22.0.1-legacy No Known Exploit
	Improper Validation of Integrity Check Value SNYK-JAVA-ORGBOUNCYCASTLE-18519163	721	io.kubernetes:client-java: 17.0.2 -> 22.0.1-legacy No Known Exploit
	Memory Allocation with Excessive Size Value SNYK-JAVA-ORGBOUNCYCASTLE-18519180	721	io.kubernetes:client-java: 17.0.2 -> 22.0.1-legacy 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:

🦉 Uncontrolled Recursion

[caniszczyk]

This is a major version upgrade across five major versions, from 17.0.2 to 22.0.1-legacy. This introduces significant breaking changes and risks that require careful validation.

Key Breaking Changes & Risks:

• Kubernetes API Model Changes: Each major version of this library corresponds to a new Kubernetes API version. This upgrade spans from Kubernetes ~1.25 (for client v17) to 1.31 (for client v22). APIs deprecated or removed in these Kubernetes versions will cause breaking changes in the application code. Code must be updated to use the newer, stable API resource versions.
• Java Version Incompatibility Risk: The -legacy suffix is intended to provide an artifact that retains the older API style and, crucially, supports Java 8. However, a bug was reported for v22.0.0-legacy where it was incorrectly compiled with a Java 11 requirement. It is not confirmed if this is fixed in 22.0.1-legacy. This poses a significant risk if the target environment is Java 8.
• API Behavior Changes: Starting with v20.0.0, the non-legacy client introduced major API refactoring, such as consolidating optional parameters into a single options object. While the legacy artifact avoids this specific refactoring, the underlying code has still changed significantly across five major versions.

Recommendation:

1. Verify Java Version: Before merging, confirm that the 22.0.1-legacy artifact is compatible with your project's target Java version (especially if it is Java 8).
2. Audit Kubernetes API Usage: Review all code that interacts with the Kubernetes API. Identify and update any usage of deprecated or removed API versions that occurred between Kubernetes 1.25 and 1.31.
3. Thorough Testing: Due to the scale of this upgrade, extensive testing is required to validate application behavior against a target Kubernetes cluster.

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