Radish alpha
h
Radicle Heartwood Protocol & Stack
Radicle
Git (anonymous pull)
Log in to clone via SSH
REVIEW: "cloud"
Lorenz Leutgeb committed 1 month ago
commit de275108f01ac3332727a4cedab494de8c9004b1
parent a875657f2e497b03765f473e42cc255662996787
1 file changed +1 -1
modified simulation/README.md
@@ -32,7 +32,7 @@ These pods can act as different kinds of `radicle-node`'s e.g. peer, seed or boo
Each of these 'sets of pods' configuration will be considered a network topology, and defined in [CUE](https://cuelang.org/).
It allows us to write type safe configuration definitions instead of YAML.
We will then use [Timoni](https://timoni.sh/) to transpile these CUE defined network topologies into [K8s object definition files](https://kubernetes.io/docs/concepts/overview/working-with-objects/) and deploy them.
-
[Talos](https://talos.dev) will be used to run the K8s pods on; so we can easily switch between locally deployed, via QEMU or Docker, to baremetal on SBC's like Raspberry Pi's, or remotely in Cloud environments.
+
[Talos](https://talos.dev) will be used to run the K8s pods on; so we can easily switch between locally deployed, via QEMU or Docker, to baremetal on SBC's like Raspberry Pi's, or remotely in cloud environments.
Then with some glue and orchestration code we can utilise the `cargo test` runner to provision a network topology, run tests over it and tear it down again.
Finally we can insert observability systems into K8s so we can inspect and compare metrics and logs from different test runs.