This message was deleted.
# general
a
This message was deleted.
c
v2.10 is out, so all releases of 2.9 after 2.9.3 will be Prime only.
w
we're on the prime channel
c
then you should know that prime-only releases are only on the prime registry, not in DH
w
we're on the prime registry
c
I couldn’t find 2.9.4 tags in dockerhub.
why were you looking for prime tags on DH if you know it’s only on prime?
w
yea, i'm sorry, i can't find any documentation on how to switch to the trusted registry, it's very very confusing
c
yeah I think so? I just know that they’re just not publicly available.
w
can I get them through SCC faster?
c
cc @bumpy-farmer-58104
w
i'd rather not put in a ticket for something that should be so obvious
cc @ambitious-intern-36135
c
you should have been given that info when you were onboarded as a customer
I’m an engineer sorry, I don’t know much more than that
w
it's ok, I understand. I know it should be obvious, but it isn't
b
It could be up to their AE or the CSM to work though enabling SCC more quickly. That’s all about when enablements are active
You can DM me the name if you’d like Colin and I can check internally to see what’s happening
w
yea the install guides I have are from 2.8, and they substitute steps with the prime registry details, but don't go any deeper into the registry switch. so I was looking for updated docs in SCC specific to rancher-prime upgrades or migration to/from community and can't find any. most references just link to the public docs.
👍 I'll send you a DM through the SUSE slack
👍 1
To get moved over completely, I had to update both systemDefaultRegistry and rancherImage values in the helm chart. otherwise Rancher was still trying to pull from dockerhub. We're on 2.9.4 now thankfully (and the prebootstrap harvester provisioning loop issue is fixed), but the https://scc.suse.com/rancher-docs/rancherprime/latest/en/suse-rancher-prime/migrating-to-the-prime-registry.html docs could really use some of these details.
👀 1