Thank you Marko, I found out that v 1.5 probably doesn't support taints.
2017-12-06 13:02 GMT+01:00 Marko Lukša <[email protected]>: > You can verify by using oc get nodes/node-dev1 -o yaml > > You can also try seeing if something is overriding the taint by running: > > oc adm taint nodes node-dev1 mode=testing:NoSchedule && oc get > nodes/node-dev1 -o yaml > > It's likely you'll see the taint, but it will get removed later. > > M. > > On 06. 12. 2017 11:29, Daniel Kučera wrote: >> >> Hi, >> >> I'm trying to set taint on node: >> >> $ oc adm taint nodes node-dev1 mode=testing:NoSchedule >> node "node-dev1" tainted >> >> However if I run describe, it shows no taints: >> >> $ oc describe nodes/node-dev1 >> Name: node-dev1 >> Role: >> Labels: beta.kubernetes.io/arch=amd64 >> beta.kubernetes.io/os=linux >> kubernetes.io/hostname=node-dev1 >> Annotations: <none> >> Taints: <none> >> CreationTimestamp: Wed, 06 Dec 2017 11:01:41 +0100 >> Phase: >> >> $ oc get nodes/node-dev1 >> NAME STATUS AGE VERSION >> node-dev1 Ready 27m v1.5.2+43a9be4 >> >> Bug again? How can I know if it's not set or only not displayed in >> describe? >> > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users -- S pozdravom / Best regards Daniel Kucera. _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
