When deploying a three node cluster with each node running all k8 components (API, schedule, kubelet, proxy) scheduling is buggy
When starting a deployment or replication controller of 1 replica, instantly 3 pods are started before two are instantly terminated. This can lead to unexpected application behavior especially when clustering applications like elastic search or couchbase. Currently a workaround is to fail over the master scheduler instead of relying on the leader election -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
