This message was deleted.
# general
a
This message was deleted.
r
I don't think it's publicly posted, so I think it might vary by customer. You likely need to contact their sales folks and get a quote and in the process they'll talk through options & costs & whatnot.
a
This is not what I expected as an answer. I thought it was more transparent than that.
r
I suspect it's at least partially because what you're buying is support, so it's going to be somewhat regional. When I spoke with sales folks a couple of years ago they said they had no different binaries (or repos) than what's publicly available.
So based on time zones & labor costs in different areas of the world & if you have any other odd requirements their cost to provide support would vary somewhat.
a
I heard that with the coming of Rancher Prime, this is changing and the free versions will not have access to the subscribed repositories. I'm not sure if we are already there though.
In the old days (old licencing model) I was told that the master and infrastructure nodes didn't need licenses, only the nodes with application workloads needed to be licensed. They were quite specific about what workloads were allowed on the non-licensed nodes.
r
No clue, but my info is a couple of years old and I don't know a thing about Rancher Prime. My last job was interested in Rancher & RKE2, current one is using K3S & K3D and might switch to RKE2 at some point but doesn't have any interest in Rancher, so I haven't been paying attention to it and am primarily still here for tips & good karma for K3S, K3D, & RKE2.
If your old sales contact is still around, they could probably point you to anything public or get you a quote update.
a
For many things K3S and K3D is sufficient but in my current project the customer is obliged to have mfg support. Yes, I've contacted the sales, but he is as clueless. He said he would contact SuSE regarding this.
r
Manufacturer support is appropriate for production workloads, but my customer is still in development so it's not an issue at the moment, and even in prod it'd be one off clusters so it'd be K3S or RKE2 support rather than Rancher.
a
RKE2 support is now covered by Rancher Prime subscriptions.
That I was able to learn from the sales guy.
And based on the number of subscriptions purchased a number of rancher server installations are also supported.
r
Well, here's hoping Rancher Prime is as reasonable as their old way was. The sales guy I talked with a couple of years ago was very reasonable and seemed focused on being reasonable to deal with to secure long-term customers rather than squeeze all the licensing profit possible in the short-term (which I appreciated).
Ah, probably getting fewer people who want Rancher Manager but lots of RKE2 so trying to seed a market.
a
That could be it, however from what I heard, reasonable is not the word I would use. For one, if you want to import for instance an EKS cluster to Rancher to have a central management, you need to have Rancher subscription for the EKS nodes. This is when you have a licensed Rancher.
r
Some of how I'd consider that reasonable would depend on how it's priced and what's included with support. Any addition of what you can call support about does have some cost on their side, so my concern is less "a cost" than "a reasonable cost for service required to provide." Though also comparative to whatever other vendors I'm dealing with.