You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[9.0](backport #7393) [Helm] Allow providing CA certificate of the Fleet Server when running the agent in fleet mode (#7492)
* [Helm] Allow providing CA certificate of the Fleet Server when running the agent in fleet mode (#7393)
* feat: introduce support for defining fleet-related certificates
* doc: add example with fleet-related certificates
(cherry picked from commit 1595be9)
# Conflicts:
# deploy/helm/elastic-agent/examples/fleet-managed-ksm-sharding/rendered/manifest.yaml
# deploy/helm/elastic-agent/examples/fleet-managed/rendered/manifest.yaml
* fix: resolve conflicts
---------
Co-authored-by: Panos Koutsovasilis <[email protected]>
# Example: Managed by Fleet Elastic Agent with self-signed certificates
2
+
3
+
This example demonstrates deploying an Elastic Agent that is managed by Fleet with custom fleet-related certificates, including CA certificates and client certificates for mutual TLS (mTLS).
4
+
5
+
## Prerequisites:
6
+
## Prerequisites
7
+
8
+
Before deploying, you should:
9
+
10
+
1. Set up an [Agent policy](https://www.elastic.co/guide/en/fleet/current/install-fleet-managed-elastic-agent.html#elastic-agent-installation-steps) in Fleet.
11
+
2. Follow [this guide](https://www.elastic.co/guide/en/fleet/8.17/add-fleet-server-kubernetes.html#add-fleet-server-kubernetes-cert-prereq) to set up an agent policy and enroll an agent to it. Do not download any binary, from the proposed enrollment command just extract the Fleet URL (`--url=$FLEET_URL`) and Enrollment token (`--enrollment-token=$FLEET_TOKEN`).
12
+
3. Create Kubernetes secrets holding the necessary certificates (CA certificate, client certificate, and client private key) or have the certificate files available locally to use with the `--set-file` Helm CLI argument.
0 commit comments