Advanced Architecture Configuration
The Advanced Architecture Configuration section explains how to configure cluster nodes with dedicated responsibilities, enabling independent scaling and targeted update strategies for specific pod sets in Kubernetes worker nodes. This approach offers cost benefits through selective resource allocation, though it requires additional configuration steps, as demonstrated through a detailed YAML configuration example for setting up an advanced Humio cluster deployment.
We can split out responsibilities for cluster nodes, such that each responsibility has their own dedicated set of cluster pods. This makes it possible to define update strategies for sets of cluster pods that serve a single purpose, or affinity rules that schedules the pods on a specific set of Kubernetes worker nodes.
Pros:
Easy to scale individual logical components independently
Cost benefits of scaling individual logical components independently, e.g. scaling nodes handling only ingest on cheap Kubernetes workers.
Cons:
Requires additional configuration
![]() |
Figure 8. Kubernetes Deployment Advanced Cluster Definition