Caleb Warren

waiting on a new RC to be cut so that we may use a non-docker registry

when using the `suse` branding, the favicon appears to still be blue. Could we update that? everything else that should be green, is, on the latest tag fo 2.7.0-rc3. ![Screen...

that is the only logo that is blue that I could find, is there some rule we're following for when something will be Suse green and when it isn't?

any update on this, @weskerfoot ? A potential workaround would be to start from the first post on the page, instead of the most recent, by default (I'm assuming if...

tested on rancher v2.7-head (c567ef3): * with an IMDSv2 policy user, create an ec2 rke2 cluster with `Allow access to EC2 metadata` and `Use tokens for metadata` enabled -- pass...

after speaking with Matt offline, we will move this ticket to blocked. The PR above allows a registry to be set upon building the rancher image. So QA will need...

I would prefer to wait until we have all updates regarding chart and image are available before testing this feature. Otherwise, it puts some unnecessary setup on QA that would...

this ticket was validated using 2.7.0-rc3 in both a docker and rke install of rancher using a non-docker registry

tested on v2.7.0-rc3: * setup 2 registries * setup rancher to use 1 registry as the global registry * provision an rke2 cluster, specifying the 2nd registry at the cluster...

using v2.7.0-rc3, both with and without authentication registries have been tested. on k3s v1.24.6+k3s1, the dashboard-shell container uses the container level registry.