-
Notifications
You must be signed in to change notification settings - Fork 258
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
Comments
@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. |
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? |
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 |
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 |
Once rancher/charts#4311 (comment) merges we're good to go |
@richard-cox - the chart PR is merged and ready to proceed here. |
Note: required monitoring version is |
Fix two e2e tests given chart changes #11529The text was updated successfully, but these errors were encountered: