Itamar Arjuan

Hi @aphyr , I recorded a smaller running, and staggered the requests a bit less dense and wound up with 2 such history assertion fails. but here's the thing, the...

For example, this is what the `history.edn` file includes at the complaint-about index: `{:type :invoke, :f :read, :value [1 nil], :process 1, :time 47689039400, :index 622} {:type :ok, :f :read,...

it appears that the expected history value is `1` while `0` was returned and that is what bothers `knossos` rather than the `:invoke` missing... or am I missing something ?...

Indeed my client `invoke!` method returns the register's value as is after casting to int of course (I based my test on your etcd example from scratch) I wasn't aware...

Just saw now that you replied - of course! Let's start by the secret , so I'm creating a TLS type secret using the method supplied in the documentation like...

My yaml for creating the cluster is the following: ``` apiVersion: cluster.redpanda.com/v1alpha2 kind: Redpanda metadata: name: redpanda spec: chartRef: chartVersion: 5.9.9 clusterSpec: nodeSelector: purpose: "red-panda-cluster" external: enabled: true domain: redpanda-data.k8s.staging.mycompanydomain.com...

``` INFO 2024-11-10 12:46:40,982 [shard 0:main] cluster - Using index based node ID {2} INFO 2024-11-10 12:46:40,983 [shard 0:main] main - application.cc:2611 - Starting Redpanda with node_id 2, cluster UUID...