Closed divyenpatel closed 7 years ago
Discussed this offline with @divyenpatel. The way kops makes sure that unwanted pods are not scheduled on master node it through taints and toleration. So a pod spec that doesn't bear appropriate toleration will not be scheduled on master.
Closing this issue, it's not a bug.
found scheduling is enabled on the Master node after cluster deployment. expecting
SchedulingDisabled
status on master node. pods are getting created on the master node.