chore: security fix for k8s client

[kostis-codefresh]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional with a list of types and scopes found here, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed my commits with DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My builds are green. Try syncing with master if they are not.
• My organization is added to USERS.md.

[github-actions]

Go Published Test Results

2 166 tests   2 166 ✅  2m 55s ⏱️
  119 suites      0 💤
    1 files        0 ❌

Results for commit 3d37c82.

[github-actions]

E2E Tests Published Test Results

  6 files    6 suites   5h 17m 28s ⏱️
111 tests 103 ✅  6 💤 2 ❌
668 runs  630 ✅ 36 💤 2 ❌

For more details on these failures, see this check.

Results for commit 3d37c82.