Skip to content

Commit

Permalink
Remove technical preview markers for 'unprivileged' mode (#1341)
Browse files Browse the repository at this point in the history
  • Loading branch information
kilfoyle authored Sep 20, 2024
1 parent b50aa87 commit 19c2689
Show file tree
Hide file tree
Showing 2 changed files with 0 additions and 6 deletions.
4 changes: 0 additions & 4 deletions docs/en/ingest-management/commands.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -521,8 +521,6 @@ elastic-agent inspect components log-default
[[elastic-agent-privileged-command]]
== elastic-agent privileged

preview::[]

Run {agent} with full superuser privileges.
This is the usual, default running mode for {agent}.
The `privileged` command allows you to switch back to running an agent with full administrative privileges when you have been running it in `unprivileged` mode.
Expand Down Expand Up @@ -1151,8 +1149,6 @@ elastic-agent uninstall
[[elastic-agent-unprivileged-command]]
== elastic-agent unprivileged

preview::[]

Run {agent} without full superuser privileges.
This is useful in organizations that limit `root` access on Linux or macOS systems, or `admin` access on Windows systems.
For details and limitations for running {agent} in this mode, refer to {fleet-guide}/elastic-agent-unprivileged.html[Run {agent} without administrative privileges].
Expand Down
Original file line number Diff line number Diff line change
@@ -1,8 +1,6 @@
[[elastic-agent-unprivileged]]
= Run {agent} without administrative privileges

preview::[]

Beginning with {stack} version 8.15, {agent} is no longer required to be run by a user with superuser privileges. You can now run agents in an `unprivileged` mode that does not require `root` access on Linux or macOS, or `admin` access on Windows. Being able to run agents without full administrative privileges is often a requirement in organizations where this kind of access is often very limited.

In general, agents running without full administrative privileges will perform and behave exactly as those run by a superuser. There are certain integrations and datastreams that are not available, however. If an integration requires root access, this is <<unprivileged-integrations,indicated on the integration main page>>.
Expand Down

0 comments on commit 19c2689

Please sign in to comment.