[Snyk] Security upgrade @kubernetes/client-node from 0.17.0 to 0.21.0

[caniszczyk]

Snyk has created this PR to fix 4 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Infinite loop SNYK-JS-TAR-17909068	828
	Allocation of Resources Without Limits or Throttling SNYK-JS-TAR-17909152	828
	Incorrect Type Conversion or Cast SNYK-JS-TAR-17909104	738
	Uncaught Exception SNYK-JS-TAR-17909225	738

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
🦉 Uncaught Exception

[caniszczyk]

This upgrade spans multiple minor versions, from 0.17.0 to 0.21.0, which correspond to updates for Kubernetes versions 1.17 through 1.21. The most significant breaking change is the removal of a deprecated RBAC API version.

Breaking Changes:

• RBAC API Removal: The rbac.authorization.k8s.io/v1alpha1 and rbac.authorization.k8s.io/v1beta1 API versions were removed in Kubernetes 1.20 (client version 0.20.0). Code using these API versions must be updated to use rbac.authorization.k8s.io/v1.

Deprecation Warnings:

• Several v1beta1 APIs for resources like Ingress, CustomResourceDefinition, and ValidatingWebhookConfiguration are deprecated and will be removed in Kubernetes 1.22 (the version after this upgrade). While not breaking in 0.21.0, applications using them should plan for migration.

Source: Kubernetes Changelogs

Recommendation: Before merging, audit your codebase for any usage of the removed v1alpha1 and v1beta1 RBAC APIs and update them to the stable v1 API. It is also highly recommended to review usage of other deprecated v1beta1 APIs to prepare for future upgrades.

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

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}