Skip to content

Latest commit

 

History

History
195 lines (158 loc) · 24.1 KB

README.md

File metadata and controls

195 lines (158 loc) · 24.1 KB

Metricbeat 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 Metricbeat docker image.

Breaking Changes

7.5.1 release is introducing a breaking change for Metricbeat users upgrading from a previous chart version. The breaking change tracked in #395 is failing helm upgrade command with the following error:

UPGRADE FAILED
Error: Deployment.apps "metricbeat-kube-state-metrics" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/name":"kube-state-metrics"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable && Deployment.apps "metricbeat-metricbeat-metrics" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app":"metricbeat-metricbeat-metrics", "chart":"metricbeat-7.5.1", "heritage":"Tiller", "release":"metricbeat"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable
Error: UPGRADE FAILED: Deployment.apps "metricbeat-kube-state-metrics" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/name":"kube-state-metrics"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable && Deployment.apps "metricbeat-metricbeat-metrics" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app":"metricbeat-metricbeat-metrics", "chart":"metricbeat-7.5.1", "heritage":"Tiller", "release":"metricbeat"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable

This is caused by the update of kube-state-metrics chart dependency which is renaming some labels in helm/charts#15261.

The workaround is to use --force argument for helm upgrade command which will force Metricbeat resources update through delete/recreate.

Requirements

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

Installing

Using Helm repository

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

Using master branch

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

Compatibility

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

6.x 7.x
6.8.8 7.6.2

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.6.2 of metricbeat it would look like this:

helm install --name metricbeat elastic/metricbeat --set imageTag=7.6.2

Configuration

Parameter Description Default
daemonset.affinity Configurable affinity for Metricbeat DaemonSet. {}
daemonset.envFrom Templatable string of envFrom to be passed to the environment from variables which will be appended to Metricbeat container for DaemonSet. []
daemonset.extraEnvs Extra environment variables which will be appended to Metricbeat container for DaemonSet. []
daemonset.extraVolumes Templatable string of additional volumes to be passed to the tpl function or DaemonSet. []
daemonset.extraVolumeMounts Templatable string of additional volumeMounts to be passed to the tpl function or DaemonSet. []
daemonset.hostNetworking Enable Metricbeat DaemonSet to use host network false
daemonset.metricbeatConfig Allows you to add any config files in /usr/share/metricbeat such as metricbeat.yml for Metricbeat DaemonSet. see values.yaml
daemonset.nodeSelector Configurable nodeSelector for Metricbeat DaemonSet. {}
daemonset.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 []
daemonset.securityContext Configurable securityContext for Metricbeat DaemonSet pod execution environment. runAsUser: 0
privileged: false
daemonset.resources Allows you to set the resources for Metricbeat DaemonSet. requests.cpu: 100m
requests.memory: 100Mi
limits.cpu: 1000m
limits.memory: 200Mi
daemonset.tolerations Configurable tolerations for Metricbeat DaemonSet. []
deployment.affinity Configurable affinity for Metricbeat Deployment. {}
deployment.envFrom Templatable string of envFrom to be passed to the environment from variables which will be appended to Metricbeat container for Deployment. []
deployment.extraEnvs Extra environment variables which will be appended to Metricbeat container for Deployment. []
deployment.extraVolumes Templatable string of additional volumes to be passed to the tpl function or Deployment. []
deployment.extraVolumeMounts Templatable string of additional volumeMounts to be passed to the tpl function or DaemonSet. []
deployment.metricbeatConfig Allows you to add any config files in /usr/share/metricbeat such as metricbeat.yml for Metricbeat Deployment. see values.yaml
deployment.nodeSelector Configurable nodeSelector for Metricbeat Deployment. {}
deployment.secretMounts Allows you easily mount a secret as a file inside the Deployment. Useful for mounting certificates and other secrets. See values.yaml for an example []
deployment.securityContext Configurable securityContext for Metricbeat Deployment pod execution environment. runAsUser: 0
privileged: false
deployment.resources Allows you to set the resources for Metricbeat Deployment. requests.cpu: 100m
requests.memory: 100Mi
limits.cpu: 1000m
limits.memory: 200Mi
deployment.tolerations Configurable tolerations for Metricbeat Deployment. []
extraContainers Templatable string of additional containers to be passed to the tpl function ""
extraInitContainers Templatable string of additional containers to be passed to the tpl function ""
hostPathRoot Fully-qualified hostPath that will be used to persist Metricbeat registry data /var/lib
image The Metricbeat docker image docker.elastic.co/beats/metricbeat
imageTag The Metricbeat docker image tag 7.6.2
imagePullPolicy The Kubernetes imagePullPolicy value IfNotPresent
imagePullSecrets Configuration for imagePullSecrets so that you can use a private registry for your image []
labels Configurable label applied to all Metricbeat pods {}
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
clusterRoleRules Configurable cluster role rules that Metricbeat uses to access Kubernetes resources. see values.yaml
podAnnotations Configurable annotations applied to all Metricbeat pods {}
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
serviceAccount Custom serviceAccount that Metricbeat will use during execution. By default will use the service account created by this chart. ""
terminationGracePeriod Termination period (in seconds) to wait before killing Metricbeat pod process on pod shutdown 30
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
priorityClassName The name of the PriorityClass. No default is supplied as the PriorityClass must be created first. ""
replicas The replica count for the metricbeat deployment talking to kube-state-metrics 1
fullnameOverride Overrides the full name of the resources. If not set the name will default to ".Release.Name-.Values.nameOverride or .Chart.Name" ""

Deprecated

Parameter Description Default
affinity Configurable affinity for Metricbeat DaemonSet. {}
extraEnvs Extra environment variables which will be appended to Metricbeat container for both DaemonSet and Deployment. []
extraVolumes Templatable string of additional volumes to be passed to the tpl function for both DaemonSet and Deployment. []
extraVolumeMounts Templatable string of additional volumeMounts to be passed to the tpl function for both DaemonSet and Deployment. []
deployment.envFrom Templatable string to be passed to the environment from variables which will be appended to Metricbeat container for both DaemonSet and Deployment. []
metricbeatConfig Allows you to add any config files in /usr/share/metricbeat such as metricbeat.yml for both Metricbeat DaemonSet and Deployment. {}
nodeSelector Configurable nodeSelector for Metricbeat DaemonSet. {}
podSecurityContext Configurable securityContext for Metricbeat DaemonSet and Deployment pod execution environment. {}
resources Allows you to set the resources for both Metricbeat DaemonSet and Deployment. {}
secretMounts Allows you easily mount a secret as a file inside DaemonSet and Deployment. Useful for mounting certificates and other secrets. []
tolerations Configurable tolerations for both Metricbeat DaemonSet and Deployment. []

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 Metricbeat with the default values
    cd examples/default
    make
    
  • You can now setup a port forward for Elasticsearch to observe Metricbeat 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