Rancher suggests users upgrade the k3s-packaged Traefik chart, breaking ingress

[brandond]

A recent PR added a Traefik chart to partner-charts:

• Traefik chart #205

K3s also packages Traefik. If you go into Installed Apps in Apps and Marketplace, there is an option to update it:

If the user clicks through the new version, the chart upgrade will succeed, but the traefik pod will go into ImagePullBackoff because the tag used by version 10.6.0 of the chart (v2.5.3) is not mirrored in the rancher Docker Hub org. This will leave the ingress broken and (if it is being used to access Rancher) lock the user out of Rancher. At this point the user would have to either restart k3s (so that the packaged chart is reinstalled) or use kubectl to roll back the chart update.

I believe that the Rancher UI should not offer upgrades to K3s or RKE2 packaged components. Especially not on the local cluster.

[brandond]

We've addressed this on the K3s/RKE2 side; closing.