Description of problem: When running below command we need the label is empty : oc describe node ip-10-0-175-124.us-east-2.compute.internal Name: ip-10-0-175-124.us-east-2.compute.internal Roles: worker Labels: beta.kubernetes.io/arch=amd64 beta.kubernetes.io/instance-type=m4.large beta.kubernetes.io/os=linux failure-domain.beta.kubernetes.io/region=us-east-2 failure-domain.beta.kubernetes.io/zone=us-east-2c kubernetes.io/hostname=ip-10-0-175-124 node-role.kubernetes.io/worker= oc describe node ip-10-0-13-2.us-east-2.compute.internal Name: ip-10-0-13-2.us-east-2.compute.internal Roles: master Labels: beta.kubernetes.io/arch=amd64 beta.kubernetes.io/instance-type=m4.large beta.kubernetes.io/os=linux failure-domain.beta.kubernetes.io/region=us-east-2 failure-domain.beta.kubernetes.io/zone=us-east-2a kubernetes.io/hostname=ip-10-0-13-2 node-role.kubernetes.io/master= Notice: node-role.kubernetes.io/master= node-role.kubernetes.io/worker= It should signify some value like true or false. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Empty result or the label has no value Expected results: The label should have a value associated with key similar to Openshift 3.10 and 3.11 Additional info:
Is the empty label causing label-selection issues / other issues? I ask because I've seen the `nodeSelector` in some deployments, for example, also have an empty string as a value, yet it still works as expected. Is the label value also empty in the output for: `oc get node ip-10-0-13-2.us-east-2.compute.internal -o yaml` ? Do you know what is supposed to set this label originally?
I think this is working as designed. I think you want to look at https://github.com/openshift/training/blob/master/docs/05-infrastructure-nodes.md and see how this might change the assumptions you have on how to properly label nodes/machines.
Closing per previous comment.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days