RKE2/Containerd Not Applying Rewrite Rules in /etc/rancher/rke2/registries.yaml

[dustin-groh-dev]

Environmental Info:

RKE2 v1.28.8
Rancher v2.8.3

Describe the bug:

When creating a new cluster via Rancher, RKE2 / containterd isn't applying the rewrite rules from /etc/rancher/rke2/registries.yaml specifically if the files have mirrors.[*].registry..... when the docs and example don't have that wildcard so it's potentially a formatting change that got missed.

Steps To Reproduce:

For a customer this was reproducible for any cluster they were attempting to create via pipeline as they use the same registries.yaml.
The fix was to edit the /var/lib/rancher/rke2/agent/etc/containerd/config.toml.tmpl to add in the mirror registry/rewrite rules and rerun the pipeline to create the cluster.

Expected behavior:

For RKE2 / containerd to apply the rewrite rules specified in the registries.yaml file even when they include a wildcard.

Additional context / logs:
Potentially related to #3227

[brandond]

I am not aware of any issues with rewrites. Can you provide a specific example of registries.yaml content that does not apply rewrites?

Note that rewrite rules ONLY apply when pulling images from a mirror endpoint; rewrites are NOT intended to apply when pulling an image directly from the registry itself (ie, when using the registry's default endpoint). If you add a wildcard entry with rewrites, but no endpoints, this is not expected to do anything.