Bump monitoring, logging version per Rancher v2.7

[w13915984028]

Bump rancher-monitoring to 102.0.2+up40.1.2
Bump rancher-logging 102.0.1+up3.17.10
Bump harvester-eventrouter to v0.1.2

Problem:

Harvester v1.3.0 is using Rancher newer version v2.7.9, the related rancher-monitoring and rancher-logging charts are required to be bumped.

Solution:

Bump charts accordingly.

Note: PR #628 is included in this PR.

Related Issue:

harvester/harvester#4940
harvester/harvester#4941

Test plan:

(1) Install cluster from v1.3.0 new version
(2) Enable rancher-monitoring and rancher-logging addons, if they are disabled
(3) Check the addons are enabled/deployed successfully
(4) Check monitoring and logging related features are working correctly
(5) Check harvester-eventrouter is using new image version v0.1.2

[bk201]

Do we still need to keep old version patch files?

[bk201]

Missing images in the air-gapped env

• Pod cattle-monitoring-system/prometheus-rancher-monitoring-prometheus-0 -> rancher/mirrored-library-nginx:1.24.0-alpine
• Pod rancher-monitoring-grafana-8cc69646c-bvfx2 -> rancher/mirrored-library-nginx:1.24.0-alpine

I also get Page not found in the GUI: URL link is :https://192.168.2.106:30443/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/d/rancher-cluster-nodes-1/rancher-cluster-nodes?orgId=1&from=now-5m&to=now&refresh=30s&theme=light, seems missing k8s/clusters/local/ ?
Not sure if this is caused by the change in 03ad687

[w13915984028]

@bk201

rancher-monitoring has changes in this file, it removes the /k8s/cluster/local prefix for local cluster, I will figure out the proper patch for Harvester's case. (acting as both local cluster and rancher-managed-multi-cluster)

charts\rancher-monitoring\102.0.2+up40.1.2\charts\grafana\templates\nginx-config.yaml

[w13915984028]

With further test, the v1.3.0 UI code removes k8s/clusters/local from certain link, which exists in v1.2.1:
e.g., when open grafana:

v1.2.1:
https://192.168.122.141/k8s/clusters/local/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/d/rancher-cluster-nodes-1/rancher-cluster-nodes?orgId=1&from=now-5m&to=now&refresh=30s&theme=light

v1.3.0
https://192.168.122.141/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/d/rancher-cluster-nodes-1/rancher-cluster-nodes?orgId=1&from=now-5m&to=now&refresh=30s&theme=light

The backend grafana-nginx config needs to be updated accordingly.

[w13915984028]

The 1.18, 1.19, 1.21 are all in the running cluster, need to keep 1.18

# crictl image ls | grep shell
docker.io/rancher/shell                                                     v0.1.18                                    2dca1f9139423       117MB
docker.io/rancher/shell                                                     v0.1.19                                    0d3d2da4b3086       352MB
docker.io/rancher/shell                                                     v0.1.21                                    4cf698201012e       399MB

[w13915984028]

With latest commit, the grafana works as expected. (make sure not hitting issue harvester/harvester#4962)

vm metrics in muliti cluster:

https://192.168.122.159/dashboard/harvester/c/c-m-9md8fhm4/kubevirt.io.virtualmachine/default/vm1#vm-metrics

https://192.168.122.159/dashboard/harvester/c/c-m-9md8fhm4/harvesterhci.io.dashboard#vm

login:

https://192.168.122.159/k8s/clusters/c-m-9md8fhm4/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/login

local cluster:

https://192.168.122.141/dashboard/harvester/c/local/harvesterhci.io.dashboard#vm

[Vicente-Cheng]

LGTM, verified with following

cattle-monitoring-system         rancher-monitoring         1        deployed  rancher-monitoring-102.0.2+up40.1.2        0.59.1
cattle-logging-system            rancher-logging            2        deployed  rancher-logging-102.0.1+up3.17.10          3.17.10

event-tailer  ●  rancher/harvester-eventrouter:v0.1.2  true  Running

[bk201]

LGTM, thanks!

[bk201]

@w13915984028 is this in the upgrade path? It seems only valid for the new deployment.

[w13915984028]

@bk201

The monitoring and logging addons (from v1.2.1) are processed as below, the addon will be set with new chart version packed in v1.3.0 ISO, it should work as expected, unless the configmap is not updated during the underlayer helm upgrade or some other bugs.

https://github.com/harvester/harvester/blob/53a1eaa6cf1da355205ab5c272ecd74bba8545fe/package/upgrade/upgrade_manifests.sh#L1203

[bk201]

@w13915984028 Thanks. Then we are all good. Is it OK to remove logging_addon.yaml and monitoring_addon.yaml?

[w13915984028]

The related files under package/upgrade/addons looks to be redundant. Should be removed.