Exam CKA topic 1 question 9 discussion

kubectl get nodes -o=custom-columns=NodeName:.metadata.name,TaintKey:.spec.taints[*].key,TaintValue:.spec.taints[*].value,TaintEffect:.spec.taints[*].effect Reference: https://kubernetes.io/docs/reference/kubectl/cheatsheet/#interacting-with-nodes-and-cluster

are you drunk or on drugs? It says "NOT INCLUDING" but every answer is like getting those

kc get node --no-headers | grep -w Ready | wc -l > /opt/KUSC00401/kusc00402.txt

First get help to find out what are the syntax to use with custom-columns option: # kubectl get nodes --help | grep -i custom-columns Then # mkdir -p /opt/KUSC00402 # kubectl get nodes -o custom-columns=:.metadata.name,:.spec.taints --no-headers | grep -v "NoSchedule" | wc -l > /opt/KUSC00402/kusc00402.txt

kubectl get nodes --no-headers | grep -w "Ready" | grep -v "NoSchedule" | wc -l > /opt/KUSC00402/kusc00402.txt

killer_sh_lab: k get no k describe no node01 | g taint # keep it simple, check each node, there’s only a few nodes. # count number of nodes accordingly not including nodes tainted NoSchedule, sample below: echo “2” > /opt/KUSC00402/kusc00402.txt

k describe nodes | grep Taint | grep -v NoSchedule| wc -l > filename.txt

echo $(k get nodes --no-headers | grep 'Ready' | grep -v 'NoSchedule' | wc -l) > opt/KUSC00402/kusc00402.txt

kubectl get nodes --no-headers | grep -v 'NoSchedule' | grep -c ' Ready ' > /opt/KUSC00402/kusc00402.txt

k8s jsonpath doesn't support multiple filter conditions like: ...conditions[?(@.type=="Ready" && @.status=="True")].type ...conditions[?(@.type=="Ready" AND @.status=="True")].type So have to play around with extra grep as below. This shall handle node status Ready. k get no --no-headers -o='custom-columns=NodeName:.metadata.name,TaintKey:.spec.taints[*].key,TaintValue:.spec.taints[*].value,TaintEffect:.spec.taints[*].effect,Status:.status.conditions[?(@.type=="Ready")].status' | grep -v NoSchedule | grep True > /opt/KUSC00402/kusc00402.txt

The easiest solution and smart solution is : k describe nodes | grep -i taint | grep none -c > /opt/KUSC00402/kusc00402.txt

step 1: kubectl get nodes - o yaml | grep taint step 2: check the tainted and export to the file

kubectl get nodes –no-headers -o='custom-columns=NodeName:.metadata.name,TaintKey:.spec.taints[*].key,TaintValue:.spec.taints[*].value,TaintEffect:.spec.taints[*].effect' | grep -v NoSchedule | wc -l > /opt/KUSC00402/kusc00402.txt

k get nodes -o jsonpath='{range.items[*]}{.metadata.name}{"\t"}{.spec.taints[?(.effect == "NoSchedule")]}{"\n"}{end}'

k get nodes -o yaml --no-headers | grep -i taint | wc -l #this will show the tainted nodes

From my understanding of the question: -c command will count the occurrence, for example of 2 node with 1 tainted node kubectl get nodes -o=custom-columns=NodeName:.metadata.name,TaintKey:.spec.taints[*].key,TaintValue:.spec.taints[*].value,TaintEffect:.spec.taints[*].effect| grep -c NoSchedule > to1.txt cat to1.txt. # 1

I was able to accomplish this with the following command: k get nodes --no-headers -o custom-columns=Name:.metadata.name,Taint:.spec.taints[*].effect,Ready:'{.status.conditions[?(@.reason == "KubeletReady")].status}' | grep -v NoSchedule | wc -l you can remove the | wc -l to see the output