DO NOT MERGE: Updates Services for Port Names

[danehans]

Updates the Contour and Envoy service to use named target ports. Names provide greater flexibility for supporting different container networking use cases According to k8s docs:

Port definitions in Pods have names, and you can reference these names in the targetPort attribute of a Service. This works even if there is a mixture of Pods in the Service using a single configured name, with the same network protocol available via different port numbers. This offers a lot of flexibility for deploying and evolving your Services. For example, you can change the port numbers that Pods expose in the next version of your backend software, without breaking clients.

Signed-off-by: Daneyon Hansen daneyonhansen@gmail.com

[Miciah]

/lgtm

[stevesloka]

I've never been a fan of port names, to me the actual port numbers are more straight forward to understand what is actually in use. Just my 2 cents.

[danehans]

I've never been a fan of port names, to me the actual port numbers are more straight forward to understand what is actually in use. Just my 2 cents.

@stevesloka My thinking is that using port name references will make easier to implement #151. I'll put a hold on this PR and reopen if this ends up being the case.

[danehans]

#152 does not use port names, so I'm closing this PR.