rancher-charts repo doesn't have latest version? about backup-restore-operator

[MKlimuszka]

We just released 3.1.0, and the associated Rancher release 2.7.2. Check again to see if you are still having this problem. If you are, please comment with more info on your environment and how you are trying to install the chart.

[ajchiarello]

I'm following the instructions in the Quickstart section, which says to use helm to add the rancher-charts repo and then install the rancher-backup-crd and rancher-backup charts. When I try to do that, the version that installs is 2.1.5, which is also the version that shows when I run a helm search repo rancher-backup. I've updated to rancher 2.7.2, but that has not changed this output. Are the instructions in the Quickstart section of the README out of date?

[eliyamlevy]

Please give us more information on your setup i.e. cluster provisioning, hosting, node os, k8s version, so on. It might be the k8s version of your cluster is limiting whats shown. For example when I run it I get this output.

#> helm search repo backup
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /Users/eliyamlevy/workspace/cluster/ron/kubeconfig.yaml
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /Users/eliyamlevy/workspace/cluster/ron/kubeconfig.yaml
NAME                             	CHART VERSION  	APP VERSION	DESCRIPTION                                       
rancher-chart/rancher-backup     	102.0.0+up3.1.0	3.1.0      	Provides ability to back up and restore the Ran...
rancher-chart/rancher-backup-crd 	102.0.0+up3.1.0	3.1.0      	Installs the CRDs for rancher-backup.             
rancher-charts/rancher-backup    	102.0.0+up3.1.0	3.1.0      	Provides ability to back up and restore the Ran...
rancher-charts/rancher-backup-crd	102.0.0+up3.1.0	3.1.0      	Installs the CRDs for rancher-backup.    

[github-actions]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.