0.10.0-debian-10-r130 release

bitnami/kubernetes-event-exporter/0/debian-10/Dockerfile

@@ -16,7 +16,7 @@ RUN wget -nc -P /tmp/bitnami/pkg/cache/ https://downloads.bitnami.com/files/stac
 RUN chmod g+rwX /opt/bitnami
 
 ENV BITNAMI_APP_NAME="kubernetes-event-exporter" \
-    BITNAMI_IMAGE_VERSION="0.10.0-debian-10-r129" \
+    BITNAMI_IMAGE_VERSION="0.10.0-debian-10-r130" \
     PATH="/opt/bitnami/kubernetes-event-exporter/bin:$PATH"
 
 USER 1001

bitnami/kubernetes-event-exporter/README.md

@@ -1,23 +1,25 @@
-# What is Kubernetes Event Exporter?
+# Kubernetes Event Exporter packaged by Bitnami
 
-> kubernetes-event-exporter is a tool that allows exporting the often missed Kubernetes events to various outputs so that they can be used for observability or alerting purposes.
+## What is Kubernetes Event Exporter?
 
-[https://github.com/opsgenie/kubernetes-event-exporter](https://github.com/opsgenie/kubernetes-event-exporter)
+> Kubernetes Event Exporter makes it easy to export Kubernetes events to other tools, thereby enabling better event observability, custom alerts and aggregation.
 
-# TL;DR
+[Overview of Kubernetes Event Exporter](https://github.com/opsgenie/kubernetes-event-exporter)
+
+## TL;DR
 
 ```console
 $ docker run --name kubernetes-event-exporter bitnami/kubernetes-event-exporter:latest
 ```
 
-## Docker Compose
+### Docker Compose
 
 ```console
 $ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-kubernetes-event-exporter/master/docker-compose.yml > docker-compose.yml
 $ docker-compose up -d
 ```
 
-# Why use Bitnami Images?
+## Why use Bitnami Images?
 
 * Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
 * With Bitnami images the latest bug fixes and features are available as soon as possible.
@@ -25,28 +27,28 @@ $ docker-compose up -d
 
 > This [CVE scan report](https://quay.io/repository/bitnami/kubernetes-event-exporter?tab=tags) contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.
 
-# How to deploy Kubernetes Event Exporter in Kubernetes?
+## How to deploy Kubernetes Event Exporter in Kubernetes?
 
 Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami Kubernetes Event Exporter Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/kubernetes-event-exporter).
 
-# Why use a non-root container?
+## Why use a non-root container?
 
 Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://docs.bitnami.com/tutorials/work-with-non-root-containers/).
 
-# Supported tags and respective `Dockerfile` links
+## Supported tags and respective `Dockerfile` links
 
 Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
 
 
-* [`0`, `0-debian-10`, `0.10.0`, `0.10.0-debian-10-r129`, `latest` (0/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-kubernetes-event-exporter/blob/0.10.0-debian-10-r129/0/debian-10/Dockerfile)
+* [`0`, `0-debian-10`, `0.10.0`, `0.10.0-debian-10-r130`, `latest` (0/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-kubernetes-event-exporter/blob/0.10.0-debian-10-r130/0/debian-10/Dockerfile)
 
-# Connecting to other containers
+## Connecting to other containers
 
 Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a different server running inside a container can easily be accessed by your application containers and vice-versa.
 
 Containers attached to the same network can communicate with each other using the container name as the hostname.
 
-# Configuration
+## Configuration
 
 Kubernetes Event Exporter is a tool created to be run inside a pod running on Kubernetes and as such, it will not work if used as a standalone container.
 
@@ -54,7 +56,7 @@ Configuration is done via a YAML file, when run in Kubernetes, it's in ConfigMap
 
 For further documentation, please check [Kubernetes Event Exporter documentation](https://github.com/opsgenie/kubernetes-event-exporter#configuration).
 
-# Logging
+## Logging
 
 The Bitnami Kubernetes Event Exporter Docker image sends the container logs to the `stdout`. To view the logs:
 
@@ -64,11 +66,11 @@ $ docker logs kubernetes-event-exporter
 
 You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
 
-# Contributing
+## Contributing
 
 We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/bitnami-docker-kubernetes-event-exporter/issues), or submit a [pull request](https://github.com/bitnami/bitnami-docker-kubernetes-event-exporter/pulls) with your contribution.
 
-# Issues
+## Issues
 
 If you encountered a problem running this container, you can file an [issue](https://github.com/bitnami/bitnami-docker-kubernetes-event-exporter/issues/new). For us to provide better support, be sure to include the following information in your issue:
 
@@ -78,7 +80,7 @@ If you encountered a problem running this container, you can file an [issue](htt
 - Version of this container (`echo $BITNAMI_IMAGE_VERSION` inside the container)
 - The command you used to run the container, and any relevant output you saw (masking any sensitive information)
 
-# License
+## License
 
 Copyright (c) 2021 Bitnami