Ansible Role: CoreDNS
Description
Deploy CoreDNS using ansible.
Requirements
- Ansible >= 2.7 (It might work on previous versions, but we cannot guarantee it)
Role Variables
All variables which can be overridden are stored in defaults/main.yml file as well as in table below.
| Name | Default Value | Description |
|---|---|---|
coredns_version |
1.8.3 | CoreDNS package version |
coredns_binary_local_dir |
"" | Allows to use local packages instead of ones distributed on github. As parameter it takes a directory where coredns binary is stored on host on which ansible is ran. This overrides coredns_version parameter |
coredns_dns_port |
53 | Port on which CoreDNS will listen for DNS requests |
coredns_config_file |
This should contain path to file with coredns configuration Corefile | |
coredns_key_files_paths |
["coredns/keys/*"] |
List containing paths to dnssec key files |
coredns_zone_files_paths |
["coredns/zones/*"] |
List containing paths to zone files |
Example
Playbook
Use it in a playbook as follows:
- hosts: all
roles:
- cloudalchemy.corednsZone files
The role will search in the paths defined in coredns_zone_files_paths in the Ansible templates paths for files to deploy. These can be used with the file plugin.
Local Testing
The preferred way of locally testing the role is to use Docker and molecule (v3.x). You will have to install Docker on your system. See "Get started" for a Docker package suitable to for your system. Running your tests is as simple as executing molecule test.
Continuous Integration
Combining molecule and circle CI allows us to test how new PRs will behave when used with multiple ansible versions and multiple operating systems. This also allows use to create test scenarios for different role configurations. As a result we have a quite large test matrix which can take more time than local testing, so please be patient.
Contributing
Troubleshooting
See troubleshooting.
License
This project is licensed under MIT License. See LICENSE for more details.