EKS Node Group Topology — DR Modes
Node Groups by DR Mode:
| Node Group |
Primary (dr="active")
|
Secondary (dr="standby")
|
Non-DR (dr="")
| Purpose |
|---|---|---|---|---|
| Digest | Deployed | Deployed | Deployed | Core LogScale processing (queries, indexing) |
| Kafka | Deployed | Deployed | Deployed | Kafka broker nodes for message queue |
| Ingress | Deployed | Deployed | Deployed | Load balancer and ingress controller |
| UI |
Deployed (when cluster_type allows)
| Not created | Deployed | Web UI serving |
| Ingest |
Deployed (when cluster_type = "advanced")
| Not created | Deployed | High-volume data ingestion |
Additional cluster-level settings by DR mode:
| Component |
Active (dr="active")
|
Standby (dr="standby")
|
Non-DR (dr="")
|
|---|---|---|---|
| Humio operator | 1 replica | 0 replicas | 1 replica |
HumioCluster nodeCount
|
cluster_size value
| 1 (declared, not running) |
cluster_size value
|
| Replication factor | Production value | 1 (overridden) | Production value |
| Auto rebalance | Enabled | Disabled | Enabled |
Why UI and Ingest Are Not Created on Standby:
Cost optimization: Eliminates idle EC2 compute. The single digest pod handles all functions during initial failover.
Automatic scale-up: Node groups are created during promotion via terraform apply.