bitnamicharts/kubernetes-event-exporter
Bitnami Helm chart for Kubernetes Event Exporter
1M+
Kubernetes Event Exporter makes it easy to export Kubernetes events to other tools, thereby enabling better event observability, custom alerts and aggregation.
Overview of Kubernetes Event Exporter
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
helm install my-release oci://registry-1.docker.io/bitnamicharts/kubernetes-event-exporter
Looking to use Kubernetes Event Exporter in production? Try VMware Tanzu Application Catalog, the commercial edition of the Bitnami catalog.
This chart bootstraps a Kubernetes Event Exporter deployment on a Kubernetes cluster using the Helm package manager.
Bitnami charts can be used with Kubeapps for deployment and management of Helm Charts in clusters.
To install the chart with the release name my-release
:
helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/kubernetes-event-exporter
Note: You need to substitute the placeholders
REGISTRY_NAME
andREPOSITORY_NAME
with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to useREGISTRY_NAME=registry-1.docker.io
andREPOSITORY_NAME=bitnamicharts
.
These commands deploy Kubernetes Event Exporter on the Kubernetes cluster in the default configuration. The Parameters section lists the parameters that can be configured during installation.
Tip: List all releases using
helm list
orhelm ls --all-namespaces
Bitnami charts allow setting resource requests and limits for all containers inside the chart deployment. These are inside the resources
value (check parameter table). Setting requests is essential for production workloads and these should be adapted to your specific use case.
To make this process easier, the chart contains the resourcesPreset
values, which automatically sets the resources
section according to different presets. Check these presets in the bitnami/common chart. However, in production workloads using resourcesPreset
is discouraged as it may not fully adapt to your specific needs. Find more information on container resource management in the official Kubernetes documentation.
This chart can be integrated with Prometheus by setting metrics.enabled
to true
. This enable the kubernetes-event-exporter native Prometheus endpoint in all pods and a metrics
service, which can be configured under the metrics.service
section. This metrics
service will have the necessary annotations to be automatically scraped by Prometheus.
Prometheus requirements
It is necessary to have a working installation of Prometheus or Prometheus Operator for the integration to work. Install the Bitnami Prometheus helm chart or the Bitnami Kube Prometheus helm chart to easily have a working Prometheus in your cluster.
Integration with Prometheus Operator
The chart can deploy ServiceMonitor
objects for integration with Prometheus Operator installations. To do so, set the value metrics.serviceMonitor.enabled=true
. Ensure that the Prometheus Operator CustomResourceDefinitions
are installed in the cluster or it will fail with the following error:
no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
Install the Bitnami Kube Prometheus helm chart for having the necessary CRDs and the Prometheus Operator.
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
To modify the application version used in this chart, specify a different version of the image using the image.tag
parameter and/or a different repository using the image.repository
parameter.
This chart allows you to set custom Pod affinity using the affinity
parameter. Find more information about Pod's affinity in the Kubernetes documentation.
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the bitnami/common chart. To do so, set the podAffinityPreset
, podAntiAffinityPreset
, or nodeAffinityPreset
parameters.
To back up and restore Helm chart deployments on Kubernetes, you need to back up the persistent volumes from the source deployment and attach them to a new deployment using Velero, a Kubernetes backup/restore tool. Find the instructions for using Velero in this guide.
Name | Description | Value |
---|---|---|
global.imageRegistry | Global Docker image registry | "" |
global.imagePullSecrets | Global Docker registry secret names as an array | [] |
global.security.allowInsecureImages | Allows skipping image verification | false |
global.compatibility.openshift.adaptSecurityContext | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | auto |
Name | Description | Value |
---|---|---|
kubeVersion | Override Kubernetes version | "" |
nameOverride | String to partially override kubernetes-event-exporter.fullname include (will maintain the release name) | "" |
fullnameOverride | String to fully override kubernetes-event-exporter.fullname template | "" |
commonAnnotations | Annotations to add to all deployed objects | {} |
commonLabels | Labels to add to all deployed objects | {} |
diagnosticMode.enabled | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | false |
diagnosticMode.command | Command to override all containers in the deployment | ["sleep"] |
diagnosticMode.args | Args to override all containers in the deployment | ["infinity"] |
extraDeploy | Array of extra objects to deploy with the release (evaluated as a template) | [] |
Name | Description | Value |
---|---|---|
replicaCount | Desired number of pod replicas | 1 |
revisionHistoryLimit | Desired number of old ReplicaSets to retain | 10 |
containerPorts.http | HTTP container port | 2112 |
extraContainerPorts | Optionally specify extra list of additional port-mappings for the container | [] |
image.registry | Container image registry | REGISTRY_NAME |
image.repository | Container image name | REPOSITORY_NAME/kubernetes-event-exporter |
image.digest | Container image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | "" |
image.pullPolicy | Container image pull policy | IfNotPresent |
image.pullSecrets | Specify docker-registry secret names as an array | [] |
automountServiceAccountToken | Mount Service Account token in pod | true |
hostAliases | Add deployment host aliases | [] |
config.logLevel | Verbosity of the logs (options: fatal , error , warn , info or debug ) | debug |
config.logFormat | How the logs are formatted. Allowed values: pretty or json | pretty |
config.receivers | Array containing event receivers | [] |
config.route.routes | Array containing event route configuration | [] |
rbac.create | Create the RBAC roles for API accessibility | true |
rbac.rules | List of rules for the cluster role | [] |
serviceAccount.create | Specifies whether a ServiceAccount should be created | true |
serviceAccount.name | Name of the service account to use. If not set and create is true, a name is generated using the fullname template. | "" |
serviceAccount.automountServiceAccountToken | Automount service account token for the server service account | false |
serviceAccount.annotations | Annotations for service account. Evaluated as a template. Only used if create is true . | {} |
podAnnotations | Pod annotations | {} |
podLabels | Pod labels | {} |
podSecurityContext.enabled | Enable security context | true |
podSecurityContext.fsGroupChangePolicy | Set filesystem group change policy | Always |
podSecurityContext.sysctls | Set kernel settings using the sysctl interface | [] |
podSecurityContext.supplementalGroups | Set filesystem extra groups | [] |
podSecurityContext.fsGroup | Group ID for the container | 1001 |
pdb.create | Create a pdb | true |
pdb.minAvailable | Minimum number / percentage of pods that should remain scheduled | "" |
pdb.maxUnavailable | Maximum number / percentage of pods that may be made unavailable | "" |
containerSecurityContext.enabled | Enabled containers' Security Context | true |
containerSecurityContext.seLinuxOptions | Set SELinux options in container | {} |
containerSecurityContext.runAsUser | Set containers' Security Context runAsUser | 1001 |
containerSecurityContext.runAsGroup | Set containers' Security Context runAsGroup | 1001 |
containerSecurityContext.runAsNonRoot | Set container's Security Context runAsNonRoot | true |
containerSecurityContext.privileged | Set container's Security Context privileged | false |
containerSecurityContext.readOnlyRootFilesystem | Set container's Security Context readOnlyRootFilesystem | true |
containerSecurityContext.allowPrivilegeEscalation | Set container's Security Context allowPrivilegeEscalation | false |
containerSecurityContext.capabilities.drop | List of capabilities to be dropped | ["ALL"] |
containerSecurityContext.seccompProfile.type | Set container's Security Context seccomp profile | RuntimeDefault |
command | Override default container command (useful when using custom images) | [] |
args | Override default container args (useful when using custom images) | [] |
lifecycleHooks |
Note: the README for this chart is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://github.com/bitnami/charts/blob/main/bitnami/kubernetes-event-exporter/README.md