Release v3.1.2

What's Changed

• Remove cluster-fleet-* namespaced resources from backup by @eliyamlevy in #367
• Replace 3rd party action with native CLI by @rancher-security-bot in #363
• Update github.com/rancher/hull digest to 627ef53 by @renovate-rancher in #353
• Update module github.com/stretchr/testify to v1.8.4 by @renovate-rancher in #370
• Update docker.io/docker/buildx-bin Docker tag to v0.11.0 by @renovate-rancher in #375
• Update plugins/manifest Docker tag to v1.4.0 by @renovate-rancher in #376
• Excluding bundle deployments from default resourceSet by @eliyamlevy in #381
• Removing v1alpha4 cluster resources from backup by @eliyamlevy in #382

Release Notes

• Due to some changes made to the default resourceSet, downstream clusters may take longer to reconnect with the local after a migration is done. If you see a downstream cluster in updating state or error state immediately after a migration please let it attempt to resolve itself. This could take from 5 to 45 minutes to complete. The quicker you re-install Rancher after completing a migration the quicker it will take for clusters to come up.
• Any previous version of backup restore used to take a backup of rancher v2.7.7 will result in migrations hitting the above "capi-webhook-service" not found error. The solution is either to make sure that the 102.0.2+up3.1.2 version of Backup-Restore Operator (the version with cluster.x-k8s.io/v1alpha4 resources removed from the resourceSet) is used for taking the backups or if the latest chart version cannot be used then workaround will be to delete all cluster.x-k8s.io/v1alpha4 resources from the backup tar before using it to restore.

New Contributors

• @rancher-security-bot made their first contribution in #363

Full Changelog: v3.1.1...v3.1.2