Skip to content
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.

Sign up for GitHub

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

Document Fleet isAirGapped setting #813

Merged
merged 1 commit into from
Jan 16, 2024
+11 −0
Merged

Document Fleet isAirGapped setting #813

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Document Fleet isAirGapped flag
@kilfoyle
kilfoyle committed Jan 15, 2024
commit 3ea660077d3243283cd006e27c8de63bfa2e30cc
11 changes: 11 additions & 0 deletions docs/en/ingest-management/fleet/air-gapped.asciidoc
View file
Original file line number Diff line number Diff line change
@@ -21,6 +21,17 @@ When upgrading all the components in an air-gapped environment, it is recommende
. Upgrade the on-premise {fleet-server}.
. In {fleet}, issue an upgrade for all the {agent}s.

[discrete]
[[air-gapped-mode-flag]]
== Enable air-gapped mode for {fleet}

Set the following property in {kib} to enable air-gapped mode in {fleet}. This allows {fleet} to intelligently skip certain requests or operations that shouldn't be attempted in air-gapped environments.

[source,yaml]
----
xpack.fleet.isAirGapped: true
----

[discrete]
[[air-gapped-proxy-server]]
== Use a proxy server to access the {package-registry}