Inject version requirement and bundle ID into charts

[brandond]

Proposed Changes

Inject version requirement and bundle ID into charts

On cluster upgrades, this will ensure that the apiserver has been restarted with the new Kubernetes version before the chart upgrade proceeds. Starting helm chart upgrades before the apiserver has been upgraded is a frequent cause of pending/failed chart upgrades, as the apiserver restart is disruptive to Helm.

This also adds a bundle-id to the chart to prevent the Rancher UI from suggesting upgrades. Manual chart upgrades should not be suggested by the Rancher UI.

Types of Changes

bugfix

Verification

1. Create multi-node RKE2 cluster of older version
2. Upgrade cluster to version containing this change
3. Note that chart update jobs fail and are retried until apiserver static pods have completed their upgrade to the new RKE2 version.

Linked Issues

• Controller delete the release during the upgrade process without warning k3s-io/helm-controller#110 (comment)
• Rancher suggests users upgrade the k3s-packaged Traefik chart, breaking ingress dashboard#4442

Further Comments