support .spec.providerID as a field-selector for Nodes

[cskinfill]

What would you like to be added?

I would like to be able to select nodes based on the .spec.providerID field.

something like kubectl get node --field-selector spec.providerID=aws://us-east-1a/someId

Why is this needed?

This would be useful in the case that I have a cloud provider ID for the node's host (EC2 instance for example), but I don't have a clear way to map that to the Node's name.

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[aojea]

AFAIK the id is not well specified and provider specific

kubernetes/staging/src/k8s.io/api/core/v1/types.go

Lines 5687 to 5689 in d831b13

	// ID of the node assigned by the cloud provider in the format: <ProviderName>://<ProviderSpecificNodeID>
	// +optional
	ProviderID string `json:"providerID,omitempty" protobuf:"bytes,3,opt,name=providerID"`

Also, what will be the case that is easier to get the providerID than the node name?

[neolit123]

/sig cloud-provider node

[Sheikh-Abubaker]

AFAIK the id is not well specified and provider specific

kubernetes/staging/src/k8s.io/api/core/v1/types.go

Lines 5687 to 5689 in d831b13

	// ID of the node assigned by the cloud provider in the format: <ProviderName>://<ProviderSpecificNodeID>
	// +optional
	ProviderID string `json:"providerID,omitempty" protobuf:"bytes,3,opt,name=providerID"`

Also, what will be the case that is easier to get the providerID than the node name?

@aojea since the providerID is already there is this issue still relevant ?

[aojea]

@aojea since the providerID is already there is this issue still relevant ?

it needs to create an index in memory in the apiserver and this has a cost, but let's summon @wojtek-t that is the expert