-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Elastic Agent] Adjust installation path in container #27396
Conversation
… the need to rename across filesystem boundaries.
/package |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
Pinging @elastic/agent (Team:Agent) |
This pull request is now in conflicts. Could you fix it? 🙏
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
* Adjust atomic installer to extract in the install directory, removing the need to rename across filesystem boundaries. * Add comment. * Add changelog. * Fix install path on k8s. * Fix issue with paths. * Cleanup temps. * Add changelog. (cherry picked from commit 9ce228f)
* Adjust atomic installer to extract in the install directory, removing the need to rename across filesystem boundaries. * Add comment. * Add changelog. * Fix install path on k8s. * Fix issue with paths. * Cleanup temps. * Add changelog. (cherry picked from commit 9ce228f) Co-authored-by: Blake Rouse <blake.rouse@elastic.co>
What does this PR do?
Adjusts the installation path inside the Elastic Agent container so the extraction path is inside the original container and not in the
STATE_PATH
.Why is it important?
The
STATE_PATH
is normally a bind mount and when it is ahostPath
bind mount it is set withnoexec
in Kubernetes. This change allows thathostPath
to be used as the installation path will now stay in the original container path.Checklist
[x] 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.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues