RKE2 registry configs are malformed when switching to yaml view

[mantis-toboggan-md]

When creating an RKE2 cluster there is an option under the 'Registry' tab to set a cluster-wide custom registry. When switching to yaml view this configuration is messed up and lost if the cluster is saved from yaml view.

This does not appear to be specific to rke2. The data being fed into the createYaml utility (used in resource creation views generally) appears correct, but the result is malformed, so the problem is likely something in createYaml.

rkeConfig.registries.configs when switching to yaml view:

The POST request for the provisioning cluster looks the same:

rekConfig.registries.configs is missing from the response to that POST request:

When creating via form, the request looks like this:

The response to the POST request when saving in form view includes the rkeConfig.registries.configs field:

[gaktive]

Possible connection to #11020

[nwmac]

@richard-cox FYI - could be related to 11020.

[richard-cox]

Similar to #11020. Following backend changes, i tried to reproduce in v2.9-a84c3a2f and could not.

We just need to write some automation to prevent regression, or for quicker resolution change to manual QA.

[nwmac]

@richard-cox Already set to manual test, so moving to 'To Test' on the project board.

[sowmyav27]

On v2.9-a9355 and dashboard - master 30d8ecc, issue is not seen anymore.