Jake Cahill

@jakubcech Yes 😄 In that article, the link on 'Merkle tree' goes here: https://docs.iota.org/docs/the-tangle/0.1/concepts/the-coordinator#milestones

This data is now available in the CSV

There’s a Secret with the super user credentials

Tested this again. Can someone confirm if this config should be valid? ``` helm repo update helm install redpanda redpanda/redpanda \ --version 5.9.0 \ --namespace jake \ --create-namespace \ --set...

redpanda configmap: ``` Name: redpanda Namespace: jake Labels: app.kubernetes.io/component=redpanda app.kubernetes.io/instance=redpanda app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=redpanda helm.sh/chart=redpanda-5.9.0 Annotations: meta.helm.sh/release-name: redpanda meta.helm.sh/release-namespace: jake Data ==== bootstrap.yaml: ---- audit_enabled: false compacted_log_segment_size: 67108864 default_topic_replications: 3 enable_rack_awareness: false...

Thanks for the detailed response. I can get this to happen consistently (tried three times). Here's the admin config for Console ``` redpanda: adminApi: enabled: true urls: ["http://redpanda-0:9644","http://redpanda-1:9644","http://redpanda-2:9644"] username: superuser...

> Can you confirm that everything works correct when all brokers are up? > Then once 1 or more brokers are brought down, Console UX starts misbehaving and transforms sometimes...

I think logging the branch name would also help.

Ideally, yes. If it’s not currently possible, it’d be great to add this as a feature request

No worries, thanks! Maybe you could parse for comments such as: ```yaml # @include # --description of the commented value # some-commented-key: value ```