chokosabe

I reran the install ```yaml Filter Connected helm upgrade --history-max=5 --install=true --namespace=cockroachdb --timeout=10m0s --values=/home/shell/helm/values-cockroachdb-11.1.5.yaml --version=11.1.5 --wait=true cockroachdb /home/shell/helm/cockroachdb-11.1.5.tgz 2023-09-07T10:24:18.006129300Z creating 1 resource(s) 2023-09-07T10:24:18.071822585Z creating 1 resource(s) 2023-09-07T10:24:18.132963998Z creating 1 resource(s)...

Nodes pretty much cant find each other - Not sure how one would go about extracting the logs on the pvc mount. Can confirm that they are created ```yaml W230907...

Can go over this quickly on Slack as well if that helps - just really surprised no one else really reporting this for one of the major infrastructure providers out...

Seeing this as well while trying to run this in a docker container

Doing this via the RuntimeClass feels a lot like an anti pattern. Its basically saying the user would be editing the RuntimeClass to set this. For anything else they are...

Reading from ENV variables really should be the way to go on this. The arguments against (above) seem a bit contrived. Its a small change that simplifies deployment and there...

values.yaml file looks like this - being deployed using rancher. I went back and disabled stream in values.yaml and the error changed to: ``` Container: benthos Filter Connected level=info msg="Running...

Thanks that helped. Can I confirm that the streams feature actually works? Added a ConfigMap that seems to be totally ignored. Thanks in advance.

Forgot to add that on the Frontend, I get this error: "failed to tear down existing cluster" This is after the check "which passes fine". The error is generated on...

This got resolved by clearing out the artifacts and checkpoints on aws and also by deleting all the replicasets for the exsiting workers. I don't know which of these fixed...