DkronDkron Pro
Quick start
Getting started Dkron Pro provides a clustering backend store out of the box based on etcd. To configure the storage a sample etcd.conf.yaml file is provided in /etc/dkron path. Editing the file, allows to configure several options for the embedded store. The location of the store configuration can be set in the command line or in the dkron config file /etc/dkron/dkron.yml using etcd-config-file-path parameter. Starting a single node Works out of the box, good for non HA installations.
AWS ECS Executor
The ECS exeutor is capable of launching tasks in ECS clusters, then listen to a stream of CloudWatch Logs and return the output. To configure a job to be run in ECS, the executor needs a JSON Task definition template or an already defined task in ECS. To allow the ECS Task runner to run tasks, the machine running Dkron needs to have the appropriate permissions configured in AWS IAM:
Authorization
Dkron Pro has the ability to be configured to use HTTP basic auth. Authentication can be set using these parameters in the dkron config file: # dkron.yml username: foo password: bar This will enable auth on the WebUI and for the API.
Clustering
Configure a cluster First follow the Dkron clustering guide then you can continue with this guide. The embedded store also needs to know its peers, it needs its own configuration as in the following example: # etcd.conf.yaml # Initial cluster configuration for bootstrapping. initial-cluster: dkron1=https://10.19.3.9:2380,dkron2=https://10.19.4.64:2380,dkron3=https://10.19.7.215:2380 With this configuration Dkron Pro should start in cluster mode with embedded storage. For a more in detail guide of clustering with etcd follow this guide: https://github.
Commercial FAQ
What is Dkron Pro? Dkron Pro is a flavor of Dkron which add more functionality and provide additional support options for customers. Is there a trial version? There’s no free trial but we do offer a 14 day period with full refund if it does not work for you. Can I get a discount? I’m sure you’re very nice but no. Everyone pays the same price. What is the license?
Commercial Support
Dkron offers only community support. Dkro Pro offers priority support via email. Priority Support Covers 1 incident per quarter, with a max response time of 2 working days. Scope is limited to Dkron and Dkron Pro features and APIs, not the application or infrastructure. For support, email support AT distrib.works. Please email using the same domain as the original license email or explain your connection to the licensed company.
Configuration
Configuration Dkron Pro uses the same parameters as Dkron OSS and add some extra parameters. Command line options --etcd-config-file-path - Etcd node config --username - Authentication username --password - Authentication password --cert-file - Path to the client server TLS cert file --key-file - Path to the client server TLS key file --client-crl-file - Path to the client certificate revocation list file --trusted-ca-file - Path to the client server TLS trusted CA cert file --client-cert-auth - Enable client cert authentication --auto-tls - Client TLS using generated certificates
Docker executor
Docker executor can launch docker based cron jobs using the docker command of the target node. This executor needs a recent version of docker to be available and configured in the target node. Configuration To run a docker job create a job config with the docker executor as in this example: { "executor": "docker", "executor_config": { "image": "alpine", //docker image to use "volumes": "/logs:/var/log/", //comma separated list of volume mappings "command": "echo \"Hello from dkron\"", //command to pass to run on container "env": "ENVIRONMENT=variable" //environment variables to pass to the container } }
Elasticsearch processor
The Elasticsearch processor can fordward execution logs to an ES cluster. It need an already available Elasticsearch installation that is visible in the same network of the target node. The output logs of the job execution will be stored in the indicated ES instace. Configuration { "processors": { "elasticsearch": { "url": "http://localhost:9200", //comma separated list of Elasticsearch hosts urls (default: http://localhost:9200) "index": "dkron_logs", //desired index name (default: dkron_logs) "forward": "false" //forward logs to the next processor (default: false) } } }
Email processor
The Email processor provides flexibility to job email notifications. Configuration of the email processor is stored in a file named dkron-processor-email.yml in the same locations as dkron.yml, and should include a list of providers, it can include any number of providers. Example: provider1: host: smtp.myprovider.com port: 25 username: myusername password: mypassword from: [email protected] subjectPrefix: '[Staging] ' Then configure each job with the following options: Example: { "processors": { "email": { "provider": "provider1", "emails": "[email protected]
Embedded storage
Dkron Pro has an embedded distributed KV store engine based on etcd. This works out of the box on each node dkron server is started. This ensures a dead easy install and setup, basically run dkron and you will have a full working node and at the same time provides you with a fully tested well supported store for its use with dkron.
Encryption
SSL encryption is used for communicating dkron pro and the embedded store, and between storage nodes itself. Also if client auth is enabled, only dkron pro clients can talk to the embedded store. This means that no other software running on your local network will be able to talk to dkron’s etcd server. This ensures that no unexpected usage of the Dkron’s store will happen, unless it is another Dkron pro instance.