LogScale Kubernetes Pod Scaling
LogScale pods in this architecture are designed to have a one-to-one relationship with the underlying GKE nodes. However, the Humio Operator does not currently support autoscaling operations while the underlying Kubernetes nodes do. In most cluster sizes, the desired count of pods is less than the maximum number of Kubernetes nodes for that tier.
For example, in a small:dedicated-ui architecture:
Desired digest pod count: 9
Maximum GKE digest node count: 6 (distributed across 3 zones)
In this situation, you can expand Kubernetes by updating the node count in
cluster_size.tpl to a new target count that should not
exceed the maximum GKE node count.
After saving cluster_size.tpl, run:
terraform apply -target module.logscale