Multi-Port Services: Named Port Environment Variables

[Strayfe]

Kubernetes used to have an environment variable of {serviceName}_SERVICE_PORT_{protocol}, however, this has since been replaced with a better mechanism for tracking services that contain multiple port mappings using name metadata to keep the ports unambiguous.

When using multiple ports for a Service, you must give all of your ports names so that these are unambiguous.
https://kubernetes.io/docs/concepts/services-networking/service/#multi-port-services

Issue: #165

[elenavillamil]

Hi @Strayfe thank you for your PR! It looks good, I just left some minor comments. Thank you for keeping UTs up to date as well!

Regarding end to end, did you test this locally yourself? It is okay if you didn't, i can do the basic test for you. I just want to have some end to end testing done before sending to our testing team.

[Strayfe]

Hi @elenavillamil,

Hi @Strayfe thank you for your PR! It looks good, I just left some minor comments. Thank you for keeping UTs up to date as well!

You are very welcome, I actually found this to be quite a fun challenge, the code is clean and easy to understand and I enjoyed working on the UTs!

Regarding end to end, did you test this locally yourself? It is okay if you didn't, i can do the basic test for you. I just want to have some end to end testing done before sending to our testing team.

Sadly, I was not able to figure out how to test this locally, however, I must admit I did not try very hard to look for resources to figure out how, past looking at the readme in the library project 😆, if you wouldn't mind pointing me in the direction of some materials to test this e2e I would be happy to give it a go, else I would appreciate it if you could see if it works!

P.S. I have pushed the requested changes.

[elenavillamil]

Thanks @Strayfe! Since this does not have changes to the docker images, just the CLI (what code structure has it as dsc folder), it should be pretty straight forward if you want to give it a try. I have also tested locally myself and sent it off to our testing team since it worked well for the regular cases. Below steps as FYI in case you want to give it a try :)

• build and publish the dsc folder. This readme has the details under building section
• Then you set environment variable BRIDGE_BUILD_PATH to the path of the publish output.
• Then open VSCode from that window where you set the environment variable and you will be running bridge using your code.

Let me know if you run into any issues. If it doesnt work and you need to debug, you can follow steps on Developing/Debugging on that section, you will be able to step through the code (you may need to update launch.json per your cluster namespace and service and computer architecture).

[elenavillamil]

LGMT! Code looks good and testing team approved.