https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
c
yes, you need to be using the prime registry
m
I would like to but can't find any documentation on it
We have a Prime subscription and are on the Stable channel
c
You should be able to get that through your support contact
m
Weird that this never came up in our POC or site review. I see our subscription in SCC. Any Customer Docs I can find just point back to the Rancher Manager docs.
c
prime requires use of a different chart repo and image repository. only community releases are in the public charts repo and on docker hub.
m
In that case, we'll file a support case and delay our planned updates until next week, it seems.
c
cc @bumpy-farmer-58104
b
hey @miniature-salesclerk-33951 sorry to hear that. If you have furhter issues please do DM me and i will assist further.
m
I submitted a support case - 01551335
b
yep, I was just coming to say that I see it there
👍 1
w
adding to the above, the documentation makes it seem like rancher prime and rancher stable registries should have version parity. Is that document going to be updated?
Copy code
Once the release is determined to be stable, it will be released to the SUSE Prime Registry and to the rancher-stable helm chart repo. As a result, Prime customers using the trusted registry will receive only stable, community-tested releases.
👍 1
c
that is only true for the latest minor. For older minors, nothing goes to the public chart repo. Is that not clear from the doc?
w
no, i dont think it's clear
m
That was not clear to me, either
That implies that community get all releases first and ones that are supported end up in the stable channel, which until very recently was the behavior
☝️ 2
c
@bumpy-farmer-58104 perhaps we can track that with the docs team. The community docs around the different release channels need to be updated to reflect the new prime progression for alpha/latest/stable. I’m not even sure we’re updating alpha any more.
👍 1
m
As a Prime customer, this has been very confusing.
➕ 1
I suspect not any less so for community release users as well.
➕ 1
w
Maybe also perceived as a little bit of a silly remark, but it's also confusing that the version info in the Readme doesn't match what's released
c
yeah we could probably pull that too
w
I've also had questions from customers about whether the prime release is stable or not, since it's inferred that latest is not stable and prime = latest
(not dumping on it, just a good chance to provide feedback!)
c
We won’t release a patch version to prime until it is stable (makes it through a period of community release without any major issues being found) if that makes any sense. So 2.9.0 was not available on prime, but 2.9.1 is.
m
Until today my assumption was that a Prime subscription covered releases in the support matrix that also reflected the releases in the stable channels: https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-9-1/
c
Note that there is no 2.9.0 on the support matrix…
m
Sure, so I wouldn't expect 2.9.0 in the stable release channel
2.8.6 is there, however, but not in the stable release channel
This is the most clear articulation I've seen of the change: https://github.com/rancher/rancher/issues/46614#issuecomment-2285750715 Just odd to see it as a GitHub comment and not a more clear communication to users and customers.
"Rancher 
latest
releases are available in the rancher-latest helm chart repo and on Github before being promoted to 
stable
and added to the SUSE Prime Registry _and rancher-stable helm chart repo._" Emphasis mine.
Likewise: "Once the release is determined to be 
stable
, it will be released to the SUSE Prime Registry and to the rancher-stable helm chart repo." There's no distinction between Prime and rancher-stable for what releases they get in any public docs I can find.
c
cc @careful-piano-35019
h
maybe its just me but I think it would be helpful if on guthub page and/or on support matrix if it is clearly listed: v2.8 • Prime - v2.8.6 - • Latest - v2.8.5 - 
rancher/rancher:v2.8.5
/ 
rancher/rancher:latest
- Read the full release notes. • Stable - v2.8.5 - 
rancher/rancher:v2.8.5
/ 
rancher/rancher:stable
- Read the full release notes. v2.7 • Prime - v2.7.11 • Latest - v2.7.10 - 
rancher/rancher:v2.7.10
- Read the full release notes. • Stable - v2.7.10 - 
rancher/rancher:v2.7.10
- Read the full release notes.
n
Elemental docs are also showing confusing information regarding Prime: https://github.com/rancher/elemental-docs/issues/348
w
@miniature-salesclerk-33951 it looks like 2.9.1 hit the stable repo today
👍 2
m
As a Rancher Prime user, the community having access to all versions is beneficial as a means of having more eyes on testing, troubleshooting, and patching, and the community not having access to those versions undercuts the claim the Prime versions are stable, community tested. I understand that this model isn't novel, but wanted to voice my feedback about this perceived change. There are plenty of compelling reasons already, IMO, for people running Rancher in production to pay for commercial support without having to muck things up with the community channels.
h
I will second that... I get it; you have to make money some way... if you have to delay the releases to community that is better than never
2 Views
Open in Slack
PreviousNext
Powered by