Kismatic should use a standard policy of labels/taints to avoid scheduling on master

[truncj]

Other configuration tools such as kubeadm use a label node-role.kubernetes.io/master= to identify the master so that pods can be specified using node-selectors. Pods with these node-selectors will not be scheduled by default on Kismatic clusters due to the master being cordoned.

A more straightforward way of avoiding scheduling would be the use of standardized taints/tolerations so the user can see why this behavior is occurring.

An example of such an app is Contiv

[alexbrand]

Discussion around this (including that specific label) has been ongoing for some time now: https://github.com/kubernetes/kubernetes/pull/39112. I think we can implement this once there's consensus, but from what I can see it doesn't look like we there's a "standard" set of labels or taints/tolerations quite yet.

[truncj]

Fair enough, thanks! Just running into these issues while trying to setup Contiv on a non-kubeadm setup.

[swade1987]

As kubernetes/kubernetes#39112 has closed we should probably align to what was agreed.