Skip to content
Branch: master
Find file History
ChiefAlexander and k8s-ci-robot Add custom security capabilities to the daemonset (#14942)
Signed-off-by: ChiefAlexander <alex.harder@fishtech.group>
Latest commit 5be1dd3 Jun 20, 2019
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
templates Add custom security capabilities to the daemonset (#14942) Jun 20, 2019
.helmignore [stable/metricbeat] metricbeat chart (#7347) Sep 23, 2018
Chart.yaml
OWNERS
README.md Add custom security capabilities to the daemonset (#14942) Jun 20, 2019
values.yaml [stable/metricbeat] Template dnsPolicy and hostNetwork (#14675) Jun 11, 2019

README.md

Metricbeat

metricbeat is used to ship Kubernetes and host metrics to multiple outputs.

Prerequisites

  • Kubernetes 1.9+

Installing the Chart

To install the chart with the release name my-release:

$ helm install --name my-release stable/metricbeat

Tip: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

The following table lists the configurable parameters of the metricbeat chart and their default values.

Parameter Description Default
image.repository The image repository to pull from docker.elastic.co/beats/metricbeat
image.tag The image tag to pull 6.7.0
image.pullPolicy Image pull policy IfNotPresent
rbac.create If true, create & use RBAC resources true
rbac.pspEnabled If true, create & use PSP resources false
serviceAccount.create If true, create & use ServiceAccount true
serviceAccount.name The name of the ServiceAccount to use. If not set and create is true, a name is generated using the fullname template
config The content of the configuration file consumed by metricbeat. See the metricbeat.reference.yml for full details
plugins List of beat plugins
extraEnv Additional environment
extraVolumes, extraVolumeMounts Additional volumes and mounts, for example to provide other configuration files
extraSecrets Additional secrets for save private data
resources.requests.cpu CPU resource requests
resources.limits.cpu CPU resource limits
resources.requests.memory Memory resource requests
resources.limits.memory Memory resource limits
daemonset.enabled If true, enable daemonset
daemonset.args Custom arguments for the docker command
daemonset.overrideConfig If overrideConfig is not empty, metricbeat chart's default config won't be used at all. {}
daemonset.modules.<name>.config The content of the modules configuration file consumed by metricbeat deployed as daemonset, which is assumed to collect metrics in each nodes. See the metricbeat.reference.yml for full details
daemonset.modules.<name>.enabled If true, enable configuration
daemonset.overrideModules If overrideModules is not empty, metricbeat chart's default modules won't be used at all. {}
daemonset.podAnnotations Pod annotations for daemonset
daemonset.priorityClassName Pod priority class name for daemonset (e.g system-node-critical) ""
daemonset.nodeSelector Pod node selector for daemonset {}
daemonset.tolerations Pod taint tolerations for daemonset [{"key": "node-role.kubernetes.io/master", "operator": "Exists", "effect": "NoSchedule"}]
daemonset.resources.requests.cpu CPU resource requests for daemonset
daemonset.resources.limits.cpu CPU resource limits for daemonset
daemonset.hostNetwork Leverage host network interfaces true
daemonset.capabilities Add security capabilities to the daemonset []
daemonset.dnsPolicy Pod DNS Policy ClusterFirstWithHostNet
deployment.enabled If true, enable deployment
deployment.args Custom arguments for the docker command
deployment.overrideConfig If overrideConfig is not empty, metricbeat chart's default config won't be used at all. {}
deployment.modules.<name>.config The content of the modules configuration file consumed by metricbeat deployed as deployment, which is assumed to collect cluster-level metrics. See the metricbeat.reference.yml for full details
deployment.modules.<name>.enabled If true, enable configuration
deployment.overrideModules If overrideModules is not empty, metricbeat chart's default modules won't be used at all. {}
deployment.podAnnotations Pod annotations for deployment
deployment.priorityClassName Pod priority class name for deployment (e.g system-cluster-critical) ""
deployment.nodeSelector Pod node selector for deployment {}
deployment.tolerations Pod taint tolerations for deployment []
deployment.resources.requests.cpu CPU resource requests for daemonset
deployment.resources.limits.cpu CPU resource limits for daemonset

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

$ helm install --name my-release \
    --set rbac.create=true \
    stable/metricbeat

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

$ helm install --name my-release -f values.yaml stable/metricbeat

Tip: You can use the default values.yaml

You can’t perform that action at this time.