Waleed Malik

@csengerszabo maybe after KKP 2.26 release we can get this prioritized somehow. It's not something urgent but would be great if we can get rid of the flakes/failures.

https://github.com/kubermatic/dashboard/pull/6629 takes care of migrations but we still need to refactor, fix the components a bit. Let's do that one by one. The unit tests need to be fixed against...

This is still relevant and important for our customers.

I did try removing `node_modules` and `.angular` directory as well but the issue is persistent for me. Still trying to figure out how exactly to reproduce this on another machine...

Just for the sake of clarification/documentation: ``` dashboard/modules/web  v1.20.7  main [±?⇡] ✗ node --version v18.14.2 dashboard/modules/web  v1.20.7  main [±?⇡] ▶ npm --version 9.5.0 dashboard/modules/web  v1.20.7...

Just a note: this needs planning and re-evaluation of components/areas that require E2E tests.

/retitle [release/v2.25] Applications: discover if a release is stuck and rollback if necessary

/milestone KKP 2.26

/cc @kron4eg /assign

> I am not sure how I feel about allowing all of them while enabling support in these components seems to be non-breaking, fiddling with configuration files, for instance providing...