-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bump rancher-monitoring to 103.1.1+up45.1.1 rancher-logging to 103.1.0+up4.4.0 #766
Conversation
@mergify backport v1.4 |
✅ Backports have been created
|
About image
helm-operation tasks which uses shell v0.1.23
|
4dd33d5
to
c92c922
Compare
…up4.4.0 Signed-off-by: Jian Wang <jian.wang@suse.com>
@ibrokethecloud @tserong Below are some pods listed from the newly installed cluster:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. thanks.
From my understanding Harvester considers the last 2 minors as the maintained versions; so currently 1.3 and 1.2 - but when 1.4.0 releases it will be 1.3 and 1.4. If this is correct I am wondering if we can backport (at least just the shell changes) to Harvester 1.3 as well for security benefits? This same version of Shell can be used in both Rancher 2.7 and 2.8 versions, so if the Harvester 1.3 branch uses similar k8s/rancher versions, then this can be safe there too. Additionally, if the version of shell that Harvester embedded Rancher uses could be updated too that would be good. Not sure if there's a mechanism on the installer to do that, but changing the shell version that rancher uses can be done via:
|
@w13915984028 Please help backport to v1.3. Do we need to handle the upgrade path? |
@bk201 The upgrade PR was also ready harvester/harvester#6187 . I will check whether to bump the whole chart or only the shell version to v1.3. thanks. |
Logged issue harvester/harvester#6283 and PR #790 (maybe more) for v1.3.2 The PR #790 is to bump shell version to v0.1.26. How to patch Rancher shell, I will check
|
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: