Harrison

#951 was merged yesterday, so this issue can be tested with the latest commit of the provider. Test steps: 1. Create a new `.tf` file for an RKE2 cluster on...

The tests have been implemented in https://github.com/rancher/terraform-provider-rancher2/commit/9f7ba67f6467cfc8f8e1381b0be98d10b6124e52, (which is misnamed 944 vs 943), this should be good to test

This issue can be tested with the latest terraform release. This change is related to https://github.com/rancher/rancher/issues/37943#event-7066651715, but does not require the IMDSv2 AWS policy to be enabled on your IAM...

@jocelynthode The root cause of the issue seems to be the use of `[]map[string]interface{}` in some parts of this PR, specifically how the plugins are being handled for the admission...

Now that the UI ticket has been closed this issue can be moved to to-test. I've done a quick smoke test (my account still has IMDSv2 enabled, for this ticket...

~~After looking into this a bit more I found that this issue cannot be addressed by web hook changes. Controllers within rancher will begin to take action before the web...

After discussion with the team we have decided that if we were to prevent users from scaling down specific pools outside of the UI that we would likely break existing...

This issue is related to https://github.com/rancher/rancher/issues/35189

This work will be included in `2.7.0-rc1` ### Root cause Rancher was passing the `--system-default-registry` flag to RKE2 even in situations where a cluster level registry was defined, causing images...

/backport v2.6.9