bump rancher-monitoring to 103.1.1+up45.1.1 rancher-logging to 103.1.0+up4.4.0 (backport #766) #782
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
Bump the rancher-monitoring chart to 103.1.1+up45.1.1 and fix CVEs.
Bump rancher-logging to 103.1.0+up4.4.0
Solution:
Bump rancher-monitoring charts
Bump rancher-logging charts
Bump shell image (0.1.26) to reduce CVE
Bump eventrouter image (not available yet)
Upstream has fixed the rancher-monitoring-crd RBAC issue, the local patch is removed.
The image
docker.io/rancher/shell:v0.1.23
is used by Rancher. Therancher-monitoring
andrancher-logging
is verified not using the v0.1.23 but v0.1.26.Depends on PR
Related Issue:
harvester/harvester#6166
Test plan:
(1) Install a new cluster
(2) Enable rancher-monitoring addon, it should work
(3) Enable rancher-logging addon, it should work
The upgrade processing will be in another PR
local test:
pods:
build pulling log: