Ask Your Question
0

magnum kubernetes NoSchedule taint

asked 2019-03-08 15:10:10 -0500

stef97 gravatar image

Hi,

My kubernetes clusters have to be manually modified ( taint removed) in order to allow pods to be created Is this expected ?

Here is the command I had to use to remove taint from minion kubectl taint nodes k8tls-29-ggwvjhvnerad-minion-0 node.cloudprovider.kubernetes.io/uninitialized:NoSchedule-

I created a cluster with 1 node, 1 master using latest Fedora-atomic 29

here is described node for the minion

Name: k8tls-29-ggwvjhvnerad-minion-0 Roles: <none> Labels: beta.kubernetes.io/arch=amd64 beta.kubernetes.io/os=linux kubernetes.io/hostname=k8tls-29-ggwvjhvnerad-minion-0 Annotations: node.alpha.kubernetes.io/ttl: 0 volumes.kubernetes.io/controller-managed-attach-detach: true CreationTimestamp: Fri, 08 Mar 2019 14:27:20 -0500 Taints: node.cloudprovider.kubernetes.io/uninitialized=true:NoSchedule Unschedulable: false Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- OutOfDisk False Fri, 08 Mar 2019 15:44:36 -0500 Fri, 08 Mar 2019 14:27:19 -0500 KubeletHasSufficientDisk kubelet has sufficient disk space available MemoryPressure False Fri, 08 Mar 2019 15:44:36 -0500 Fri, 08 Mar 2019 14:27:19 -0500 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Fri, 08 Mar 2019 15:44:36 -0500 Fri, 08 Mar 2019 14:27:19 -0500 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Fri, 08 Mar 2019 15:44:36 -0500 Fri, 08 Mar 2019 14:27:19 -0500 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Fri, 08 Mar 2019 15:44:36 -0500 Fri, 08 Mar 2019 14:27:19 -0500 KubeletReady kubelet is posting ready status Addresses: Capacity: cpu: 1 ephemeral-storage: 6130Mi hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 2038528Ki pods: 110 Allocatable: cpu: 1 ephemeral-storage: 5784993783 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 1936128Ki pods: 110 System Info: Machine ID: 6db739bb62eb47698add665127cb335a System UUID: 6db739bb-62eb-4769-8add-665127cb335a Boot ID: 4dbcee13-4378-4918-85c6-85d4a74a414a Kernel Version: 4.20.8-200.fc29.x86_64 OS Image: Debian GNU/Linux 9 (stretch) Operating System: linux Architecture: amd64 Container Runtime Version: docker://1.13.1 Kubelet Version: v1.11.1 Kube-Proxy Version: v1.11.1 Non-terminated Pods: (0 in total) Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits AGE --------- ---- ------------ ---------- --------------- ------------- --- Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 0 (0%) 0 (0%) memory 0 (0%) 0 (0%) ephemeral-storage 0 (0%) 0 (0%) Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Starting 53s kubelet, k8tls-29-ggwvjhvnerad-minion-0 Starting kubelet. Normal NodeHasSufficientDisk 52s (x2 over 52s) kubelet, k8tls-29-ggwvjhvnerad-minion-0 Node k8tls-29-ggwvjhvnerad-minion-0 status is now: NodeHasSufficientDisk Normal NodeHasSufficientMemory 52s (x2 over 52s) kubelet, k8tls-29-ggwvjhvnerad-minion-0 Node k8tls-29-ggwvjhvnerad-minion-0 status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 52s (x2 over 52s) kubelet, k8tls-29-ggwvjhvnerad-minion-0 Node k8tls-29-ggwvjhvnerad-minion-0 status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 52s (x2 over 52s) kubelet, k8tls-29-ggwvjhvnerad-minion-0 Node k8tls-29-ggwvjhvnerad-minion-0 status is now: NodeHasSufficientPID

edit retag flag offensive close merge delete

Comments

No magnum should initialize the kubernetes cluster for you, and untaint the nodes. Check the setting user_trust in [trust]

jsm gravatar imagejsm ( 2019-03-09 09:01:41 -0500 )edit

yes, many thanks Adding cluster_user_trust = true under [trust] in magnum.conf took care of tainting

stef97 gravatar imagestef97 ( 2019-03-10 09:07:43 -0500 )edit

1 answer

Sort by » oldest newest most voted
0

answered 2019-05-08 10:09:10 -0500

panticz.de gravatar image

If the error still occurs you can check if the containers in the kube-system namespace has been deployed successfully:

kubectl get pods --all-namespaces -o wide

or debug journal on master node:

journalctl -u kubelet -f -l

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2019-03-08 15:10:10 -0500

Seen: 133 times

Last updated: May 08