Back to Charts

dmarc2logstash Helm Chart

stable/dmarc2logstash/README.md

latest4.5 KB
Original Source

dmarc2logstash Helm Chart

NOTICE: This chart has moved!

Due to the deprecation and obsoletion plan of the Helm charts repository this chart has been moved to a new repository. Refer to the dmarc2logstash GitHub project for information on installing this chart from the new repository.

Overview

dmarc2logstash: A POP3 polling service that converts Domain-based Message Authentication, Reporting, and Complicane (DMARC) reports into a logstash feed. More information about the DMARC organization and RFC 7489 standards can be found at https://dmarc.org. An accompanying dashboard is available for import into Grafana.

Installing the Chart

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

console
helm install --name my-release stable/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 my-release deployment:

console
helm delete my-release --purge

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

Configuration

settingdescriptiondefault
dmarc2logstash.image.repositorydmarc2logstash Docker image repositoryjertel/dmarc2logstash
dmarc2logstash.image.tagdmarc2logstash image tag, typically the version, of the Docker image1.0.3
dmarc2logstash.image.pullPolicydmarc2logstash Kubernetes image pull policyIfNotPresent
delete_messagesSet to 1 to delete messages or 0 to preserve messages (useful for debugging)1
filebeat.image.repositoryElastic filebeat Docker image repositorydocker.elastic.co/beats/filebeat
filebeat.image.tagElastic filebeat tag, typically the version, of the Docker image6.6.0
filebeat.image.pullPolicyElastic filebeat Kubernetes image pull policyIfNotPresent
filebeat.logstash.hostLogstash service host; ex: logstash (this value must be provided)""
filebeat.logstash.portLogstash service port5000
filebeat.logstash.sourceTypeLogstash source type will allow custom filtering via the Logstash configurationjson-logs
filebeat.logstash.indexElasticsearch index that will contain the new DMARC data (index will be created on-the-fly if doesn't exist)dmarc
filebeat.logstash.timeoutSeconds to wait before timing out the connection to logstash15

Secrets

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

variablerequireddescription
pop3_servertrueThe POP3 server hostname or IP address (must support TLS)
pop3_usernametruePOP3 account username
pop3_passwordtruePOP3 account password

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

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

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

console
kubectl apply -f secrets.yaml