Advanced Architecture Configuration
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 4. Kubernetes Deployment Advanced Cluster Definition