Chris Seto

@voutilad what did you expect to happen OOC? I would expect something to go wrong but I write the software. If you expected that the operator would "take over" the...

Makes sense! I propose that we make the operator fail to deploy the cluster if there's an existing helm release with a conflicting name as that's the most straightforward and...

Scaling here would be changing the number of active brokers in the redpanda cluster. IMO we shouldn't need to keep track of the original. We can always measure the active...

We could also experiment with the merge queue feature that GitHub has and run E2E tests on batches of PRs after quick checks have finished. 🤔

Yep! It's still pretty slow (~40m) but we're trending towards the right direction.

Closing this in favor of the internal [ENG-114](https://redpandadata.atlassian.net/browse/ENG-114) [ENG-114]: https://redpandadata.atlassian.net/browse/ENG-114?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

Ah, looks like we need to get you into the @redpanda-data/k8s group. Would you also mind removing Alejandro from the list as he's no longer with redpanda?

Thanks for the ping :)

Huh... So it seems that this might just be general flakiness in/of the kuttl suite? The most recent run passed and a quick glance at the history indicates that it's...

Some additional context: This issue pops up most frequently with users of (older?) versions of ArgoCD. It's happened enough that we should try to implement a workaround within `gotohelm`. We'll...