IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Configuring Kubernetes metadata enrichment on Elastic Agent Run Elastic Agent on Amazon EKS managed by Fleet »
Elastic Docs ›Fleet and Elastic Agent Guide [8.15] ›Install Elastic Agents ›Install Elastic Agents in a containerized environment

Run Elastic Agent on GKE managed by Fleet

edit

Run Elastic Agent on GKE managed by Fleet

edit

Please follow the steps to run the Elastic Agent on Run Elastic Agent on Kubernetes managed by Fleet page.

Important notes:
edit

On managed Kubernetes solutions like GKE, Elastic Agent has no access to several data sources. Find below the list of the non-available data:

  1. Metrics from Kubernetes control plane components are not available. Consequently, metrics are not available for kube-scheduler and kube-controller-manager components. In this regard, the respective dashboards will not be populated with data.
  2. Audit logs are available only on Kubernetes master nodes as well, hence cannot be collected by Elastic Agent.

Autopilot GKE

edit

Although autopilot removes many administration challenges (like workload management, deployment automation etc. of kubernetes clusters), additionally restricts access to specific namespaces (i.e. kube-system) and host paths which is the reason that default Elastic Agent manifests would not work.

Specific manifests are provided to cover Autopilot environments.

kube-state-metrics also must be installed to another namespace rather than the default as access to kube-system is not allowed.

Additonal Resources:

edit
« Configuring Kubernetes metadata enrichment on Elastic Agent Run Elastic Agent on Amazon EKS managed by Fleet »