Somewhat of a middle ground solution might be to create "sub-clusters" using taints and tolerations -- that is, have dedicated nodes for dedicated application classes or workloads inside a given cluster. It may reduce the general overhead inherent to managing separate clusters while still being able to leverage a lot of the built-in Kubernetes tooling.
-- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
