rancher: system-charts release-v2.4 branch breaks cluster monitoring
What kind of request is this (question/bug/enhancement/feature request): Bug
Steps to reproduce (least amount of steps as possible): Have Rancher v2.4.3 installed Try to install cluster monitoring No installable candidates
-or-
Have Rancher v2.4.3 installed with cluster-monitoring v0.1.0 System-library catalog is tracking release-v2.4 branch Cluster monitoring stops working
Result: No installable candidates for cluster-monitoring Clusters show message “Template system-library-rancher-monitoring allowed rancher version not match current server”
Other details that may be helpful: 2 days ago this commit was merged into the release-v2.4 branch: https://github.com/rancher/system-charts/commit/d623a935af05fec5b6b868afc2ecce996bb5ebd8
This disallows cluster-monitoring v0.1.0 for anything > v2.3.7 Cluster-monitoring v0.1.1 has minimum version v2.4.5-rc0
Environment information
- Rancher version (
rancher/rancher/rancher/serverimage tag or shown bottom left in the UI): v2.4.3 - Installation option (single install/HA): HA
Cluster information
-
Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom
-
Machine type (cloud/VM/metal) and specifications (CPU/memory): Metal
-
Kubernetes version (use
kubectl version): v1.17.4 -
Docker version (use
docker version): 19
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 18 (2 by maintainers)
Verified on 2.4.4 - system-charts branch
release-v2.4Monitoring version
0.1.0is now available. User is able to enable on a cluster@nikkelma all looks resolved now; thank you for the quick action 👍
I’ve documented the default username and password for Grafana here https://github.com/rancher/docs/commit/876c74b3ea475ab090c791a664af6311c497f1fe
@armsnyder It will resolve itself on next catalog refresh when the change is fully merged - either automatically in the background or by performing a manual refresh of the
system-librarycatalog.