Re: [kubernetes/kubernetes] clear up confusion between labels and taints (#44335)
Michail Kargakis
@kubernetes/sig-cli-misc for the missing taints from kubectl describe
@jeroenjacobs1205 taints is an actual field in the node spec as opposed to label which is included in the metadata of every Kube object. Read more about taints in https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#taints-and-tolerations-beta-feature
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Jeroen Jacobs
@kargakis : My confusion originates from the fact that the kubeadm mentions it's a taint, while "describe" lists it as a label. Does that mean the kubeadm documentation is incorrect?
Michail Kargakis
@jeroenjacobs1205 the node has probably both, a label and a taint with the same key. You can confirm by inspecting the output of kubectl get no NAME -o yaml
TonyAdo
/assign @adohe
TonyAdo
this would be not correct, taint != labels.
xiaoping
kubectl get node <your_node_name> -o template --template={{.spec.taints}}
show the taints filed
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale
fejta-bot
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale
k8s-ci-robot
Closed #44335.
fejta-bot
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
DelDennis
/reopen
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Kubernetes Prow Robot
@DelDennis: You can't reopen an issue/PR unless you authored it or you are a collaborator.
In response to this:
/reopen
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.