Skip to content
Branch: master
Find file History
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
examples
templates Merge pull request #420 from jmlrt/override-probe Dec 27, 2019
tests
.helmignore Initial commit of Filebeat chart Apr 26, 2019
Chart.yaml [7.5.1] bump versions Dec 18, 2019
Makefile Initial commit of Filebeat chart Apr 26, 2019
README.md [doc] switch relative URLs to absolute URLs Jan 10, 2020
values.yaml Merge pull request #420 from jmlrt/override-probe Dec 27, 2019

README.md

Filebeat Helm Chart

This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.

This helm chart is a lightweight way to configure and run our official Filebeat docker image.

Requirements

  • Helm >=2.8.0 and <3.0.0 (see parent README for more details)
  • Kubernetes >=1.9

Usage notes and getting started

  • The default Filebeat configuration file for this chart is configured to use an Elasticsearch endpoint. Without any additional changes, Filebeat will send documents to the service URL that the Elasticsearch helm chart sets up by default. You may either set the ELASTICSEARCH_HOSTS environment variable in extraEnvs to override this endpoint or modify the default filebeatConfig to change this behavior.
  • The default Filebeat configuration file is also configured to capture container logs and enrich them with Kubernetes metadata by default. This will capture all container logs in the cluster.
  • This chart disables the HostNetwork setting by default for compatibility reasons with the majority of kubernetes providers and scenarios. Some kubernetes providers may not allow enabling hostNetwork and deploying multiple Filebeat pods on the same node isn't possible with hostNetwork. However Filebeat does recommend activating it. If your kubernetes provider is compatible with hostNetwork and you don't need to run multiple Filebeat daemonsets, you can activate it by setting hostNetworking: true in values.yaml.

Installing

Using Helm repository

  • Add the elastic helm charts repo
    helm repo add elastic https://helm.elastic.co
    
  • Install it
    helm install --name filebeat elastic/filebeat
    

Using master branch

  • Clone the git repo
    git clone git@github.com:elastic/helm-charts.git
    
  • Install it
    helm install --name filebeat ./helm-charts/filebeat
    

Compatibility

This chart is tested with the latest supported versions. The currently tested versions are:

6.x 7.x
6.8.6 7.5.1

Examples of installing older major versions can be found in the examples directory.

While only the latest releases are tested, it is possible to easily install old or new releases by overriding the imageTag. To install version 7.5.1 of Filebeat it would look like this:

helm install --name filebeat elastic/filebeat --set imageTag=7.5.1

Configuration

Parameter Description Default
filebeatConfig Allows you to add any config files in /usr/share/filebeat such as filebeat.yml. See values.yaml for an example of the formatting with the default configuration. see values.yaml
extraEnvs Extra environment variables which will be appended to the env: definition for the container []
extraVolumeMounts List of additional volumeMounts to be mounted on the Daemonset []
extraVolumes List of additional volumes to be mounted on the Daemonset []
envFrom Templatable string of envFrom to be passed to the environment from variables which will be appended to the envFrom: definition for the container []
hostPathRoot Fully-qualified hostPath that will be used to persist Filebeat registry data /var/lib
hostNetworking Use host networking in the daemonset so that hostname is reported correctly false
image The Filebeat docker image docker.elastic.co/beats/filebeat
imageTag The Filebeat docker image tag 7.5.1
imagePullPolicy The Kubernetes imagePullPolicy value IfNotPresent
imagePullSecrets Configuration for imagePullSecrets so that you can use a private registry for your image []
managedServiceAccount Whether the serviceAccount should be managed by this helm chart. Set this to false in order to manage your own service account and related roles. true
podAnnotations Configurable annotations applied to all Filebeat pods {}
labels Configurable label applied to all Filebeat pods {}
podSecurityContext Configurable podSecurityContext for Filebeat pod execution environment runAsUser: 0
privileged: false
livenessProbe Parameters to pass to liveness probe checks for values such as timeouts and thresholds. failureThreshold: 3
initialDelaySeconds: 10
periodSeconds: 10
successThreshold: 3
timeoutSeconds: 5
readinessProbe Parameters to pass to readiness probe checks for values such as timeouts and thresholds. failureThreshold: 3
initialDelaySeconds: 10
periodSeconds: 10
successThreshold: 3
timeoutSeconds: 5
resources Allows you to set the resources for the DaemonSet requests.cpu: 100m
requests.memory: 100Mi
limits.cpu: 1000m
limits.memory: 200Mi
serviceAccount Custom serviceAccount that Filebeat will use during execution. By default will use the service account created by this chart. ""
secretMounts Allows you easily mount a secret as a file inside the DaemonSet. Useful for mounting certificates and other secrets. See values.yaml for an example []
terminationGracePeriod Termination period (in seconds) to wait before killing Filebeat pod process on pod shutdown 30
tolerations Configurable tolerations []
nodeSelector Configurable nodeSelector {}
affinity Configurable affinity {}
priorityClassName The name of the PriorityClass. No default is supplied as the PriorityClass must be created first. ""
updateStrategy The updateStrategy for the DaemonSet. By default Kubernetes will kill and recreate pods on updates. Setting this to OnDelete will require that pods be deleted manually. RollingUpdate
fullnameOverride Overrides the full name of the resources. If not set the name will default to ".Release.Name-.Values.nameOverride or .Chart.Name" ""

Examples

In examples/ you will find some example configurations. These examples are used for the automated testing of this helm chart.

Default

  • Deploy the default Elasticsearch helm chart
  • Deploy Filebeat with the default values
    cd examples/default
    make
    
  • You can now setup a port forward for Elasticsearch to observe Filebeat indices
    kubectl port-forward svc/elasticsearch-master 9200
    curl localhost:9200/_cat/indices
    

Testing

This chart uses pytest to test the templating logic. The dependencies for testing can be installed from the requirements.txt in the parent directory.

pip install -r ../requirements.txt
make pytest

You can also use helm template to look at the YAML being generated

make template

It is possible to run all of the tests and linting inside of a docker container

make test

Integration Testing

Integration tests are run using goss which is a serverspec like tool written in golang. See goss.yaml for an example of what the tests look like.

To run the goss tests against the default example:

cd examples/default
make goss
You can’t perform that action at this time.