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

Add Fleet Server install steps on K8s and Docker #1184

Merged
merged 4 commits into from
Sep 18, 2024
Merged

Add Fleet Server install steps on K8s and Docker #1184

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a3de0b8
Add Fleet Server install steps on K8s and Docker
kilfoyle Jul 17, 2024
1633852
fixup
kilfoyle Jul 17, 2024
dfe6358
Update docs/en/ingest-management/elastic-agent/running-on-kubernetes-…
kilfoyle Sep 18, 2024
b0daaa8
Update docs/en/ingest-management/elastic-agent/elastic-agent-containe…
kilfoyle Sep 18, 2024
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
12 changes: 12 additions & 0 deletions docs/en/ingest-management/elastic-agent/elastic-agent-container.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,18 @@ docker run --rm docker.elastic.co/beats/elastic-agent:{version} elastic-agent co

include::{ingest-docs-root}/docs/en/ingest-management/tab-widgets/run-agent-image/widget.asciidoc[]

If you need to run {fleet-server} as well, adjust the `docker run` command above by adding these environment variables:

[source,yaml]
----
--env FLEET_SERVER_ENABLE=true \ <1>
--env FLEET_SERVER_ELASTICSEARCH_HOST=<elasticsearch-host> \ <2>
--env FLEET_SERVER_SERVICE_TOKEN=<service-token> <3>
----
<1> Set to `true` to bootstrap {fleet-server} on this {agent}. This automatically forces {fleet} enrollment as well.
<2> The Elasticsearch host for Fleet Server to communicate with, for example `http://elasticsearch:9200`.
<3> Service token to use for communication with {es} and {kib}.

[TIP]
.Running {agent} on a read-only file system
====
Expand Down
16 changes: 15 additions & 1 deletion ...ingest-management/elastic-agent/running-on-kubernetes-managed-by-fleet.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,8 +67,22 @@ To specify different destination/credentials, change the following parameters in
<5> The basic authentication username used to connect to {kib} and retrieve a `service_token` to enable {fleet}.
<6> The basic authentication password used to connect to {kib} and retrieve a `service_token` to enable {fleet}.

Refer to <<agent-environment-variables>> for all available options.
If you need to run {fleet-server} as well, adjust the `docker run` command above by adding these environment variables:

[source,yaml]
------------------------------------------------
- name: FLEET_SERVER_ENABLE
value: "true" <1>
- name: FLEET_SERVER_ELASTICSEARCH_HOST
value: "<elasticsearch-host>" <2>
- name: FLEET_SERVER_SERVICE_TOKEN
value: "<service-token>" <3>
------------------------------------------------
<1> Set to `true` to bootstrap {fleet-server} on this {agent}. This automatically forces {fleet} enrollment as well.
<2> The Elasticsearch host for Fleet Server to communicate with, for example `http://elasticsearch:9200`.
<3> Service token to use for communication with {es} and {kib}.

Refer to <<agent-environment-variables>> for all available options.

[discrete]
== Step 4: Configure tolerations
Expand Down