Skip to content
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

Backport changes following bump to Monitoring chart / components #11592

Closed
richard-cox opened this issue Aug 6, 2024 · 8 comments
Closed

Backport changes following bump to Monitoring chart / components #11592

richard-cox opened this issue Aug 6, 2024 · 8 comments
Assignees
Labels
kind/enhancement QA/manual-test Indicates issue requires manually testing size/1 Size Estimate 1
Milestone

Comments

@richard-cox
Copy link
Member

richard-cox commented Aug 6, 2024

@richard-cox richard-cox added this to the v2.8.next2 milestone Aug 6, 2024
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Aug 6, 2024
@rak-phillip rak-phillip added the size/1 Size Estimate 1 label Aug 7, 2024
@gaktive gaktive modified the milestones: v2.8.next1, v2.8.next2 Sep 3, 2024
@gaktive
Copy link
Member

gaktive commented Sep 4, 2024

@richard-cox how easy is this backport for 2.8.x? Upon discussion with Frameworks, this will help address issues for customers who haven't gone up to 2.9.x yet and I think this avoids some of our current Vue3 efforts. I'm wondering if this can still get back into next1 rather than next2.

@richard-cox
Copy link
Member Author

Backports should be straight forward. We need to make sure these UI changes happen in the same release as the chart changes, otherwise we'll just break things. @joshmeranda can you confirm the chart bumps are going into 2.8.next1?

@joshmeranda
Copy link

Sorry just getting back from holiday. Seeing the we are releasing tomorow, so probably 2.8.next2 since 1 day is definitely too quick for QA.

Once that is released it will be easy to get this rebase backported

@richard-cox
Copy link
Member Author

richard-cox commented Sep 17, 2024

Grand. @joshmeranda just let us know when everything is merged and ready (is there an issue?)

Edit: Ah i see rancher/rancher#46269, which is blocked on this one. Given we're both committed to a release that should be unblocked now, which will allow us to then implement and test changes UI side

@richard-cox
Copy link
Member Author

Once rancher/charts#4311 (comment) merges we're good to go

@richard-cox richard-cox self-assigned this Sep 25, 2024
@mallardduck
Copy link
Member

@richard-cox - the chart PR is merged and ready to proceed here.

@richard-cox
Copy link
Member Author

Note: required monitoring version is 103.2.0-rc.1+up57.0.3. Visible only after updating the rancher chart repo to dev-v2.8 and enabling prerelease versions from user preferences

@richard-cox richard-cox added QA/manual-test Indicates issue requires manually testing and removed QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this labels Sep 27, 2024
@rancher-max rancher-max self-assigned this Oct 16, 2024
@rancher-max
Copy link

Validated using rancher v2.8-head

Version Information

image
  • Rancher : v2.8-head
  • cluster : v1.28.13+rke2r1
  • rancher-monitoring : 103.2.0-rc.1+up57.0.3

Validation Information

  • Alerts tab is correctly showing and is not empty
image
  • Cluster Metrics, Kubernetes Component Metrics, and ETCD Metrics are all showing with graphs displayed
image image image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement QA/manual-test Indicates issue requires manually testing size/1 Size Estimate 1
Projects
None yet
Development

No branches or pull requests

6 participants