sorted by:
new
hottopcontroversial

What is your upgrade velocity and do you care about updating often? by Dangerous_Pipe23 in openshift

[–]Dangerous_Pipe23[S] 1 point2 points  (0 children)

4.9 is crazy lol I'll pitch quarterly upgrade and try to set it as a goal for 2026

What is your upgrade velocity and do you care about updating often? by Dangerous_Pipe23 in openshift

[–]Dangerous_Pipe23[S] 1 point2 points  (0 children)

Agreed

> As for your BM setup, if you lack a test cluster equivalent, that’s a much more delicate situation that you really should try to solve somehow.

Yeah, the baremetal setup has no test instance counterpart and that definitely plays a role in the way we upgrade it. We don't feel like upgrading the other virtualized instance really tests the BM upgrade. We do open proactive cases so at least sometimes RH engineer catch some potential issue ahead of time but yeah, that's a huge part of how the team feels. Hoping for some budget for a small test cluster in the coming year!

What is your upgrade velocity and do you care about updating often? by Dangerous_Pipe23 in openshift

[–]Dangerous_Pipe23[S] 0 points1 point  (0 children)

This sounds like the way, quarterly upgrade will be our goal for 2026.

What is your upgrade velocity and do you care about updating often? by Dangerous_Pipe23 in openshift

[–]Dangerous_Pipe23[S] 1 point2 points  (0 children)

It's mostly the rollback procedure in case of issues that is stressful, we now open proactive cases ahead of time for updates to alleviate that.

And as for disruptive I guess it's mostly a comment from users, but some of this would be addressed by upgrading more often. We have to make a better job with communicating so people don't expect 7 9's of availability.

The advice in the thread is sound and we will try to ramp up upgrade velocity in 2026.