838 B
838 B
Architecture Update: Multi-Node Hub/Worker Split
Context from User (Hendrik): "Even from the very beginning on the installer must be able to install multiple worker nodes that can form a cluster. I also wonder, if we should seperate the roles more: worker nodes that host apache camel workloads, and control plane nodes that host the persistence (loki, the time series database, etc)... architect and developer need to know about this and update their spec. they should also critically think about that change and add to the conversation where required."
Directives:
- We are moving from a single-node appliance to a multi-node cluster (embedded k3s).
- Role 1: "Appliance Hub" (runs local k3s control plane, VictoriaMetrics, Loki, SaaS tunnel).
- Role 2: "Appliance Worker" (runs Apache Camel workloads, OTEL forwarders).