discovery.service-labels not works with spring-cloud-starter-kubernetes-client v2.0.1

Describe the bug spring.cloud.kubernetes.discovery.service-labels is ignored with spring-cloud-starter-kubernetes-client v2.0.1, and ServiceInstance metadata contains null key(null=8080) if the k8s service/deployment doesn’t have named ports, which causes NPE from downstream like spring boot admin Tags.

[andrein]

I’ve attached a somewhat-minimal example using spring-boot-admin

There are two (separate?) issues here:

1. spring.cloud.kubernetes.discovery.service-labels seems to be ignored, spring-boot-admin detects every service in the namespace
2. if one of the detected services doesn’t have named ports, discovery crashes with with a NPE (this looks like a bug in spring-boot-admin):

If I switch from spring-cloud-starter-kubernetes-client to spring-cloud-starter-kubernetes-fabric8, the app works correctly. Does that mean that both issues might be bugs in spring-cloud-starter-kubernetes-client?

[edwardzjl]

I think I’m running into the same issue with spring-cloud-starter-kubernetes-client v2.0.3

I have 3 services, and only 1 of them is labeled as “openapi-service”:

when I set service-labels to only select service with “openapi-service” label: ( or openapi-service=true, same effect )

The pod cannot start, with no ERROR information container log shows it’s applying a service without “openapi-service” label, twice:

And that’s the end of log, the container exists after that.