chore: Update k8s version to 1.30

[nikoshet]

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.95%. Comparing base (0397210) to head (870c629).
Report is 86 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3748      +/-   ##
==========================================
- Coverage   83.96%   83.95%   -0.02%     
==========================================
  Files         162      162              
  Lines       18508    18508              
==========================================
- Hits        15540    15538       -2     
- Misses       2106     2107       +1     
- Partials      862      863       +1     

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

[github-actions]

Published E2E Test Results

  4 files    4 suites   3h 18m 54s ⏱️
112 tests 101 ✅  7 💤 4 ❌
452 runs  420 ✅ 28 💤 4 ❌

For more details on these failures, see this check.

Results for commit 870c629.

♻️ This comment has been updated with latest results.

[github-actions]

Published Unit Test Results

2 257 tests   2 257 ✅  2m 59s ⏱️
  128 suites      0 💤
    1 files        0 ❌

Results for commit 870c629.

♻️ This comment has been updated with latest results.

[zachaller]

We should remove on on the tail end like 1.26.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[mansing2]

Any plan in near future to support K8S v1.30. We want to upgrade the k8s and we are blocked.

[zachaller]

@mansing2 I would not let what clients Rollouts uses cause you to not upgrade your k8s cluster. As long as you do not use any of the new pod spec fields if there are any it will be ok we use very little k8s feature set. The only big one being the embedded pod spec into the rollout resource.

[blkperl]

This was resolved in #3858