Vinicius D. Cerutti

There are no tests for this yet, and I would like to have this tested to help us avoid this situation in the future. I hope we get #2780 merged...

I will be testing this during the afternoon

It was tested on a local deployment, moving from `2024.7.1` directly to `2024.9.2` (will need to test again since this now changed to `2024.11.1`): - Group created on the previous...

This needs to be re-tested to ensure the upgrade will run now that we moved it to 2024.11.1

Re-tested with the recent changes:  

These tests are failing only for DO, and it might be related to its decommissioning process. So, we can disregard it for now, I've created a separated issue for this...

Good catch @krassowski ! I know what might be happening... Keycloak has a setting for automatically binding new users to a default group (which in this case is `Analyst`), and...

Thanks, @kenafoster, for the fantastic attention to detail in this issue. That's awesome. It looks like the upgrade path for the role assumes the role's presence already to proceed with...

increasing the kernel timeout limit to 30min would lead the pod overall timeout limit went to 45min instead of the current 30min. I also think that's a good re-arrangement. I...

That makes sense; the original idea of keeping a somewhat larger instance type than the group itself was that we could balance more user pods in the same node without...