Issue 572: Enable external option to client service #576
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.
Change log description
Adds the option to use external ZooKeeper in
ClientService
Purpose of the change
Fixes #572
What the code does
The code uses the same logic as AdminServerService boolean external field. in ClientService, to expose client-service outside
the cluster, using LoadBalancer service type.
How to verify it
System tests must pass, when clientService.external is true, client service in kubernetes type needs to be LoadBalancer (this test added).