The original issue has been fixed in v0.12, yet the workaround description was omitted from Rancher v2.9.9 release notes. Documenting it on the troubleshooting page makes it accessible to users.