T.J. Telan

The problem is that while we check for `FORCE_RELEASE`, we do not actually perform the push on L144, unlike what we report. https://github.com/infinyon/fluvio/blob/aa30e7eab255d995509be4b6fa0f8465120ba578/.github/workflows/release.yml#L143-L151

Short answer: yes. Without `--proxy-addr` the cluster start will not complete ``` $ fluvio cluster start Current channel: stable 📝 Running pre-flight checks ✅ Kubectl active cluster microk8s at: https://172.31.42.67:16443...

I have a rough idea about how I would tackle this issue. First, I'll characterize what I'm seeing: ## Current status ### Fluvio needs kubernetes, and assumes that there's a...

I vote for adding this in `fluvio`, and adding a `fluvio-test` test to externally verify the throughput based on client configuration. Users would want this, and it would be nice...

Just adding a note: I'm occasionally able to repro this while doing scale testing after a few days of constant traffic. When it occurs I usually cannot recover the cluster...

Made an attempt to fix this, but it turned out that the upgrade process relies on this mismatch failure not exit early. It can potentially take a a minute for...

> I think that `master` branch is a protected branch so not sure if that push will work without changing the protection rules I think you might be right. I...

https://github.com/infinyon/fluvio/pull/2526 also needs a personal access token created to push to master, so this PR will be unblocked once that occurs

The topic configure and create functionality should be written with a Builder pattern

@0xkelvin Yes, please go ahead an take this if you are interested