Configuration Examplesedit

This section contains manifests that illustrate common use cases, and can be your starting point in exploring Elastic Agent deployed with ECK. These manifests are self-contained and work out-of-the-box on any non-secured Kubernetes cluster. They all contain a three-node Elasticsearch cluster, a single Kibana instance and a single Fleet Server instance.

The examples in this section are for illustration purposes only and should not be considered to be production-ready. Some of these examples use the false setting which has performance implications and should be tuned for production workloads, as described in Virtual memory.

System and Kubernetes integrationsedit

kubectl apply -f

Deploys Elastic Agent as a DaemonSet in Fleet mode with System and Kubernetes integrations enabled. System integration collects syslog logs, auth logs and system metrics (for CPU, I/O, filesystem, memory, network, process and others). Kubernetes integrations collects API server, Container, Event, Node, Pod, Volume and system metrics.

System and Kubernetes integrations running as non-rootedit

kubectl apply -f

The provided example is functionally identical to the previous section but runs the Elastic Agent processes (both the Elastic Agent running as the Fleet server and the Elastic Agent connected to Fleet) as a non-root user by utilizing a DaemonSet to ensure directory and file permissions.

The DaemonSet itself must run as root to set up permissions and ECK >= 2.10.0 is required.

Custom logs integration with autodiscoveredit

kubectl apply -f

Deploys Elastic Agent as a DaemonSet in Fleet mode with Custom Logs integration enabled. Collects logs from all Pods in the default namespace using autodiscover feature.

APM integrationedit

kubectl apply -f

Deploys single instance Elastic Agent Deployment in Fleet mode with APM integration enabled.