feat: testing new k8s version

[emirot]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (argocd27@a40c95a). Click here to learn what that means.
Patch has no changes to coverable lines.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@             Coverage Diff             @@
##             argocd27       #3   +/-   ##
===========================================
  Coverage            ?   48.95%           
===========================================
  Files               ?      247           
  Lines               ?    42934           
  Branches            ?        0           
===========================================
  Hits                ?    21020           
  Misses              ?    19792           
  Partials            ?     2122           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.