feat: introduced LoadBalancer
for service
#27
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to introduce the
LoadBalancer
service type to close #15.Implementation
For the deployment, if the service type is detected as the
LoadBalancer
, it follows the same process asNodePort
, where it loops through the list of ports defined in the.spec.ports
, but the difference is thehostBinding.HostPort
becomes the service port, so the low-end port is published at the host level.Example YAML
For the
GET
part, it sets theexternal-ip
to match the server IP address wherek2d
runs. An example run below:Example Run
Also, as part of this PR, I have added an exclusion of the
ExternalName
service type we do not support yet.