Incorrect generation of unique service key when building service and endpoint maps #3
Description
Network service controller in Kube-router need to generate a unique service key ( combination of namespace, service name, and spec.ports.name) that will be used to index service info map, and end points info map.
Current key generation is flawed, where it fails if there is mismatch in port opened by the service and port opened by endpoint.
Correct way is to use spec.ports.name, which is internally copied by the API server into endpoint API object as well. This is what Kube-proxy uses as well.