We are currently using a lot of static and inline variable declarations to manage test data and state in the Cypress integration test package, which is really difficult to maintain and not a good practice. We should explore better strategies for this and create some stories to improve it.

At a high level, almost all of our e2e tests involve manipulating some state on the cluster and then ensuring the UI behaves as expected. There should be a single source of truth for applied and expected states, and it should be easily maintainable.