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.

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

[8.15] Add missing environment variables for container setup (backport #1354) #1372

Merged
merged 2 commits into from
Oct 8, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 7, 2024

This updates the Elastic Agent environment variables page to add/remove variables as described here.

For easier reviewing, I've copied the output into this google doc.

Removed variables:

Added variables:

  • FLEET_FORCE - same as the --force flag
  • ELASTIC_AGENT_CERT & ELASTIC_AGENT_CERT_KEY - paths to mtls cert and key the agent will use to connect to fleet-server. (corresponding var for passphrase is missing)
  • FLEET_SERVER_CLIENT_AUTH - set fleet-server mtls settings, one of: none (default), optional, required
  • FLEET_SERVER_ES_CERT & FLEET_SERVER_ES_CERT_KEY - fleet-server -> es mTLS cert paths. (corresponding var for passphrase is missing)
  • FLEET_SERVER_INSECURE_HTTP - expose fleet-server as an http server
  • FLEET_HEADER - I think this one is headers the agent will send to fleet-server (internal setting according to Craig)
  • FLEET_KIBANA_HEADER - headers used when contacting Kibana (internal setting according to Craig)
  • FLEET_SERVER_TIMEOUT - how long elastic-agent will wait for fleet-server to checkin as healthy
  • FLEET_DAEMON_TIMEOUT - how long fleet-server will wait during the bootstrap process for elastic-agent

Closes: #1355
Rel: #1075


This is an automatic backport of pull request #1354 done by Mergify.

* Add missing environment variables for container setup

* Add more missing settings

* fixup

* fixup

* fixup

* fixup

* Remove FLEET_HEADER & FLEET_KIBANA_HEADER

(cherry picked from commit 98d9db9)
@mergify mergify bot requested a review from a team as a code owner October 7, 2024 20:13
@mergify mergify bot added the backport label Oct 7, 2024
Copy link

github-actions bot commented Oct 7, 2024

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@kilfoyle kilfoyle merged commit d226c26 into 8.15 Oct 8, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant