From 40e5bb34cf933f9ab0a388a0dcb9993adfe0771b Mon Sep 17 00:00:00 2001 From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> Date: Fri, 20 Sep 2024 11:34:15 -0400 Subject: [PATCH] Remove technical preview markers for 'unprivileged' mode (#1341) (cherry picked from commit 19c268989035d42687a843c21568d48d4ee55001) --- docs/en/ingest-management/commands.asciidoc | 4 ---- .../elastic-agent/elastic-agent-unprivileged-mode.asciidoc | 2 -- 2 files changed, 6 deletions(-) diff --git a/docs/en/ingest-management/commands.asciidoc b/docs/en/ingest-management/commands.asciidoc index b8ff95146..a2818f3d6 100644 --- a/docs/en/ingest-management/commands.asciidoc +++ b/docs/en/ingest-management/commands.asciidoc @@ -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. @@ -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]. diff --git a/docs/en/ingest-management/elastic-agent/elastic-agent-unprivileged-mode.asciidoc b/docs/en/ingest-management/elastic-agent/elastic-agent-unprivileged-mode.asciidoc index ee35d6973..3c47aaca7 100644 --- a/docs/en/ingest-management/elastic-agent/elastic-agent-unprivileged-mode.asciidoc +++ b/docs/en/ingest-management/elastic-agent/elastic-agent-unprivileged-mode.asciidoc @@ -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 <>.