We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 docker images are available under two different namespaces:
elastic-agent
beats
Our document almost always use the beats and we should update it to rather talk exclusively about the elastic-agent one. Example: https://www.elastic.co/guide/en/fleet/current/elastic-agent-container.html
From 9.0 onwards, we plan to remove Elastic Agent images from the beats namespace.
This change can be performed in 8.15.x without issue.
Example: https://www.elastic.co/guide/en/fleet/current/elastic-agent-container.html
The documentation team will investigate the issue and create the initial content.
Main contact: @jlind23
Stakeholders: @ycombinator @cmacknz @pierrehilbert @nimarezainia
The text was updated successfully, but these errors were encountered:
Here are a couple of PRs to get the docs fixed up:
Sorry, something went wrong.
kilfoyle
Successfully merging a pull request may close this issue.
Description
Elastic Agent docker images are available under two different namespaces:
elastic-agent
beats
Our document almost always use the
beats
and we should update it to rather talk exclusively about theelastic-agent
one.Example: https://www.elastic.co/guide/en/fleet/current/elastic-agent-container.html
From 9.0 onwards, we plan to remove Elastic Agent images from the
beats
namespace.This change can be performed in 8.15.x without issue.
Resources
Example: https://www.elastic.co/guide/en/fleet/current/elastic-agent-container.html
Collaboration
The documentation team will investigate the issue and create the initial content.
Point of contact.
Main contact: @jlind23
Stakeholders: @ycombinator @cmacknz @pierrehilbert @nimarezainia
The text was updated successfully, but these errors were encountered: