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

[caniszczyk]

Snyk has created this PR to fix 1 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
	Uncaught Exception SNYK-JS-QS-19432019	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:

🦉 Uncaught Exception

[caniszczyk]

This is a major version upgrade that introduces significant breaking changes, requiring code modifications.

Key Breaking Changes:

• ESM Only Package: The library has been converted to be an ES Module (ESM) only package. This means you can no longer use require('@kubernetes/client-node') to import it. All imports must be updated to use the import syntax.
• HTTP Backend Changed: The underlying HTTP client has been switched from the deprecated request library to node-fetch. While many use cases may work without modification, any code that relied on the specific implementation or configuration of the request library will break.
• No Migration Guide: The official release notes state that there is no migration guide available, and users should refer to examples to understand the new usage patterns.

Recommendation: This upgrade will cause your application to fail without significant refactoring of how the module is imported. Before merging, you must update your project to handle ESM imports (e.g., by converting your code to ESM or using dynamic import()). Review your usage of the client for any dependencies on the previous request-based implementation.

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.}