Cherry-pick #19628 to 7.x: [Elastic Agent] Add support for multiple hosts in connection to kibana#19794
Merged
blakerouse merged 1 commit intoelastic:7.xfrom Jul 9, 2020
Merged
Conversation
elastic#19628) * Add ability for multiple hosts to be defined for agents connection to kibana. * Fix reference. * Add changelog. (cherry picked from commit 57c4280)
Contributor
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
|
ph
approved these changes
Jul 9, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Cherry-pick of PR #19628 to 7.x branch. Original message:
What does this PR do?
Adds the ability for
hostskey on Kibana configuration, without removing support for thehostkey to not break current configurations. When multiple hosts are defined for Kibana the agents connection to Kibana is load balanced across the hosts.Why is it important?
To allow redundancy across multiple Kibana instances without the need for round robin DNS and/or load balancers.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues