[bugfix] - handle LoadBalancer deletion if service type changes to no longer be a LoadBalancer #211
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.
There's currently a bug that leaves an orphaned NodeBalancer if a Service's type changes to no longer be
LoadBalancer. If the type is changed back, a new NodeBalancer is created.This PR detects a change in Service type and deletes the NodeBalancer if necessary.
e.g. when doing a
kubectl editon a Service to instead be a NodePort type:General:
Pull Request Guidelines: