Cherry-pick #24220 to 7.x: [Elastic Agent] Add support for Fleet Server inside Docker#24291
Merged
blakerouse merged 1 commit intoelastic:7.xfrom Mar 2, 2021
Merged
Conversation
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
Contributor
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
Contributor
Author
|
/package |
simitt
approved these changes
Mar 2, 2021
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
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 #24220 to 7.x branch. Original message:
What does this PR do?
First it refactors the entrypoint for the Elastic Agent docker container to use a new subcommand
container. This subcommand is designed specifically to be executed by the container runtime. Based on the defined environment variables it prepares the Elastic Agent to run in that environment. Due to the large number of environment variables that Elastic Agent needed and the complexity of the order of operations based it was best to move this from a bash script to golang.With the refactor comes the ability to bootstrap the Elastic Agent inside of a docker container. Using the
FLEET_SERVER_ENABLEflag the docker container will bootstrap the Fleet Server and enroll the Elastic Agent all inside the container on startup.Why is it important?
To allow Fleet Server to be spawned under Elastic Agent while being executed under Docker.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.