When I search with helm and look at the index file it doesn't have all the stable versions in it. Shouldn't this have them there? releases.rancher.com/server-charts/stable/index.yaml

looks good, which stable version were you looking for?

I am looking to go from 2.11.3 to 2.11.16 to 2.12.12 and then all the way up to the latest stable. These are the only ones I see in the helm search and they match what is in the index file:

NAME                    CHART VERSION   APP VERSION     DESCRIPTION
rancher-stable/rancher  2.14.3          v2.14.3         Install Rancher Server to manage Kubernetes clu...
rancher-stable/rancher  2.14.2          v2.14.2         Install Rancher Server to manage Kubernetes clu...
rancher-stable/rancher  2.14.1          v2.14.1         Install Rancher Server to manage Kubernetes clu...
rancher-stable/rancher  2.13.3          v2.13.3         Install Rancher Server to manage Kubernetes clu...
rancher-stable/rancher  2.13.2          v2.13.2         Install Rancher Server to manage Kubernetes clu...
rancher-stable/rancher  2.13.1          v2.13.1         Install Rancher Server to manage Kubernetes clu...
rancher-stable/rancher  2.13.0          v2.13.0         Install Rancher Server to manage Kubernetes clu...
rancher-stable/rancher  2.12.3          v2.12.3         Install Rancher Server to manage Kubernetes clu...
rancher-stable/rancher  2.12.2          v2.12.2         Install Rancher Server to manage Kubernetes clu...
rancher-stable/rancher  2.12.1          v2.12.1         Install Rancher Server to manage Kubernetes clu...
rancher-stable/rancher  2.11.3          v2.11.3         Install Rancher Server to manage Kubernetes clu...
rancher-stable/rancher  2.11.2          v2.11.2         Install Rancher Server to manage Kubernetes clu...
rancher-stable/rancher  2.11.1          v2.11.1         Install Rancher Server to manage Kubernetes clu...

that tracks. once a minor version is released all new patches for previous minor versions are only provided to Prime customers. you should still be ok upgrading to the highest patch for that minor version before moving on to the next one though

It errors out. I have removed and re-added rancher-stable and that version doesn't show up in the index file, which makes sense that I get this error. This is what I get:

~ helm upgrade rancher rancher-stable/rancher \
  --namespace cattle-system \
  --set hostname=rancher.example.com \
  --set bootstrapPassword=supersecret \
  --set ingress.tls.source=letsEncrypt \
  --set letsEncrypt.email=email@example.com \
  --set letsEncrypt.ingress.class=nginx \
  --set ingress.ingressClassName=nginx \
  --version=2.11.16
Error: chart "rancher" matching 2.11.16 not found in rancher-stable index. (try 'helm repo update'): no chart version found for rancher-2.11.16

yes unfortunately 2.11.16 is a prime only version. the max community version will be 2.11.3

Ahhh. Thanks! So I can go to 2.12.3 then 2.13.3 and 2.14.3 without any problems?

So I can go to 2.12.3 then 2.13.3 and 2.14.3 without any problems?

That should work ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades#… For information about prime it's best to start at suse.com/products/rancher, there you should find some good first steps

Following up on this a bit, there's a 9.1 CVE in Rancher 2.14.3 and the 2.14.4 patch is only available to prime customers? Am I now forced to go to 2.15.0, with potential significant changes to patch a CVE that critical?

The latest community version will keep up to date with resolved CVEs. One of the main features of prime is that it benefits from backport efforts to address CVEs and important bug fixes