Let Renovate Bot update the Kubernetes version

[twz123]

Description

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Manual test
• Auto test added

Checklist

• My code follows the style guidelines of this project
• My commit messages are signed-off
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[twz123]

Blocked by

• Remove hack/tool folder #6424
• Use fake version in update server inttest #6426

[juanluisvaladas]

I don't understand how both 0.X.Y and 1.X.Y work, but if it gets the job done it's welcome

[twz123]

From Renovate's point of view, these are different dependencies. The k8s.io/* dependencies from the go datasource have the version 0.xx, the k8s.io/kubernetes dependency has 1.xx. So Renovate will simply bump all of them to the newest version. This only works out because Kubernetes releases everything together at the same time. One disadvantage is that the PR title won't contain the Kubernrnetes version number, as Renovate will only include a version number in the title if it's unambiguous, but we have two.

I'm still investigating. I noticed this afternoon that some bits are still missing.

[github-actions]

This pull request has merge conflicts that need to be resolved.

[github-actions]

The PR is marked as stale since no activity has been recorded in 30 days