Chart version: 1.5.2
Api version: v1
App version: 1.5.2
Provides a POP3-polled DMARC XML report injector into Elasticse...
Chart Type
Set me up:
helm repo add center
Install Chart:
helm install dmarc2logstash center/codesim/dmarc2logstash
Versions (0)

Helm Chart for Kubernetes

A dmarc2logstash chart is available in the Codesim LLC Helm repository, and can be installed into an existing Kubernetes cluster by following the instructions below.

Installing the Chart

Add the Codesim repository to your Helm configuration:

helm repo add codesim

Next, install the chart with a release name, such as dmarc2logstash:

helm install dmarc2logstash codesim/dmarc2logstash

The command deploys dmarc2logstash on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation. The secrets section lists the required Kubernetes secrets.

Uninstalling the Chart

To uninstall/delete the dmarc2logstash deployment:

helm delete dmarc2logstash --purge

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


setting description default
dmarc2logstash.image.repository dmarc2logstash Docker image repository jertel/dmarc2logstash
dmarc2logstash.image.tag dmarc2logstash image tag, typically the version, of the Docker image 1.5.2
dmarc2logstash.image.pullPolicy dmarc2logstash Kubernetes image pull policy IfNotPresent
delete_messages Set to 1 to delete messages or 0 to preserve messages (useful for debugging) 1
filebeat.image.repository Elastic filebeat Docker image repository
filebeat.image.tag Elastic filebeat tag, typically the version, of the Docker image 7.9.0
filebeat.image.pullPolicy Elastic filebeat Kubernetes image pull policy IfNotPresent Logstash service host; ex: logstash (this value must be provided) ””
filebeat.logstash.port Logstash service port 5000
filebeat.logstash.sourceType Logstash source type will allow custom filtering via the Logstash configuration json-logs
filebeat.logstash.index Elasticsearch index that will contain the new DMARC data (index will be created on-the-fly if doesn’t exist) dmarc
filebeat.logstash.timeout Seconds to wait before timing out the connection to logstash 15


The following dmarc2logstash-secrets are required to be present in order for this chart to deploy:

variable required description
pop3_server true The POP3 server hostname or IP address (must support TLS)
pop3_username true POP3 account username
pop3_password true POP3 account password

Below is a sample secrets.yaml file that can be used as a template. Remember that all secrets must be base64-encoded.

apiVersion: v1
kind: Secret
  name: dmarc2logstash-secrets
type: Opaque
  pop3_server: ""
  pop3_username: ""
  pop3_password: ""

Once you have provided the base64-encoded secret values, apply the file to your Kubernetes cluster as follows:

kubectl apply -f secrets.yaml