Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/arillso/ansible.traefik
Setup Traefik Proxy (https://docs.traefik.io/v2.0) using Docker
https://github.com/arillso/ansible.traefik
Last synced: 6 days ago
JSON representation
Setup Traefik Proxy (https://docs.traefik.io/v2.0) using Docker
- Host: GitHub
- URL: https://github.com/arillso/ansible.traefik
- Owner: arillso
- License: mit
- Created: 2020-05-20T07:46:25.000Z (over 4 years ago)
- Default Branch: develop
- Last Pushed: 2024-06-29T13:08:34.000Z (6 months ago)
- Last Synced: 2024-11-06T21:30:20.507Z (about 2 months ago)
- Homepage:
- Size: 48.8 KB
- Stars: 11
- Watchers: 7
- Forks: 9
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# Ansible Role: traefik
[](https://travis-ci.org/arillso/ansible.traefik)
[](https://galaxy.ansible.com/arillso/traefik)
[](https://galaxy.ansible.com/arillso/traefik)
- [Description](#description)
- [Installation](#installation)
- [Requirements](#requirements)
- [Role Variables](#role-variables)
- [In-Depth Configuration](#in-depth-configuration)
- [Compatibility with sbaerlocher/ansible.traefik](#compatibility-with-sbaerlocheransibletraefik)
- [Variables which need manual action](#variables-which-need-manual-action)
- [`traefik_configuration_file`](#traefikconfigurationfile)
- [`traefik_api`](#traefikapi)
- [`traefik_ping`](#traefikping)
## Description
[Traefik](https://docs.traefik.io/v2.0) is a reverse proxy written in Go.
It can be used in multiple situations with many providers (Kubernetes, Swarm,
...). Version 2 is also capable of TCP routing.
This role sets up traefik on a host as reverse proxy and load balancer. This
allows you, to use one server as a host for multiple dockerized applications.
> **Note:** This role allows you to use one (1) server as a host for many
> applications. Depending on your usecase, this might not be what you are
> looking for. For services that need to be highly-available, consider using
> Kubernetes or other systems and setup traefik there.
## Installation
```bash
ansible-galaxy install arillso.traefik
```
## Requirements
- Docker
## Role Variables
Traefik v2.0 onwards supports yaml configuration. This role uses this to generate
the configuration directly from the given ansible variables.
There are certain quick-setup variables, which allow you to setup a simple
instance, but there is also the option to fully configure every key yourself.
The quick-setup allows you to:
- Setup a lets-encrypt based certificate resolver
- Setup standard entrypoints
- Setup standard Docker provider
The quick-setup variables are prefixed with `traefik_qs_`.
| Name | Default | Description |
| :-------------------------------- | :--------------------------- | :--------------------------------------------------------------- |
| `traefik_dir` | `/etc/traefik` | where to store traefik data |
| `traefik_hostname` | `"{{ inventory_hostname }}"` | the hostname of this instance |
| `traefik_network` | `traefik_proxy` | the name of the generated network |
| `traefik_qs_send_anonymous_usage` | `false` | wether to send anonymous usage |
| `traefik_qs_https` | `false` | wether to setup a https endpoint |
| `traefik_qs_https_redirect` | `false` | wether to setup a redirection to https |
| `traefik_qs_https_le` | `false` | wether to setup letsencrypt using tls (only if https is enabled) |
| `traefik_qs_https_le_mail` | undefined | the email to use for letsencrypt (**Required**) |
| `traefik_qs_log_level` | `ERROR` | the loglevel to apply |
| `traefik_container_name` | `'traefik'` | the container name |
| `traefik_network_name` | `'traefik_proxy'` | the network name |
| `traefik_network_ipam_subnet` | `'172.16.1.0/24'` | subnet |
| `traefik_network_ipam_gateway` | `'172.16.1.1'` | gateway |
| `traefik_network_ipam_iprange` | `'172.16.1.0/24'` | iprange |
| `traefik_image` | `'traefik'` | the image used |
| `traefik_add_volumes` | `[]` | additional volumes to mount |
| `traefik_ports` | `['80:80', '443:443']` | the ports shared |
| `traefik_labels` | `{}` | labels to set on the traefik container. |
The default names of the generated configs are:
- Entrypoints:
- `http`
- `https`
- Providers:
- `docker`
- Certificate Resolvers:
- `letsencrypt`
### In-Depth Configuration
As stated before, this role also allows you to configure traefik in-depth by
using the traefik yaml config. The following variables can be used:
| Name | Default | Description |
| :-------------------------------------- | :-------- | ------------------------------------------------------------------------------ |
| `traefik_confkey_global` | undefined | [see Docs 📑](https://docs.traefik.io/reference/static-configuration/file/) |
| `traefik_confkey_serversTransport` | undefined | [see Docs 📑](https://docs.traefik.io/reference/static-configuration/cli-ref/) |
| `traefik_confkey_entryPoints` | undefined | [see Docs 📑](https://docs.traefik.io/routing/entrypoints/#entrypoints) |
| `traefik_confkey_providers` | undefined | [see Docs 📑](https://docs.traefik.io/routing/providers/docker/) |
| `traefik_confkey_api` | undefined | [see Docs 📑](https://docs.traefik.io/operations/api/) |
| `traefik_confkey_metrics` | undefined | [see Docs 📑](https://docs.traefik.io/observability/metrics/overview/) |
| `traefik_confkey_ping` | undefined | [see Docs 📑](https://docs.traefik.io/operations/ping/) |
| `traefik_confkey_log` | undefined | [see Docs 📑](https://docs.traefik.io/observability/logs/) |
| `traefik_confkey_accessLog` | undefined | [see Docs 📑](https://docs.traefik.io/observability/access-logs/) |
| `traefik_confkey_tracing` | undefined | [see Docs 📑](https://docs.traefik.io/observability/tracing/overview/) |
| `traefik_confkey_hostResolver` | undefined | [see Docs 📑](https://docs.traefik.io/reference/static-configuration/file/) |
| `traefik_confkey_certificatesResolvers` | undefined | [see Docs 📑](https://docs.traefik.io/https/acme/#certificate-resolvers) |
These keys are merged into the configuration **after** the quick-setup config using
the [`combine()`](https://docs.ansible.com/ansible/latest/user_guide/playbooks_filters.html#combining-hashes-dictionaries)
filter in non recursive mode. This allows you to add configuration options as
you need them. If you want to overwrite the quick-setup items, use their key
(as specified above).
## Compatibility with sbaerlocher/ansible.traefik
This role is intended as a continuation of the
[sbaerlocher/ansible.traefik](https://github.com/sbaerlocher/ansible.traefik)
role for traefik v2. Most of the variables set for said role will continue
to work in this role, except for three special cases, where you **must**
recreate a custom configuration using the `_confkey_` variables.
These are explained in the following sections.
### Variables which need manual action
#### `traefik_configuration_file`
Using the `traefik_configuration_file` has no influence on your installation.
The configuration of Traefik has changed with the introduction of v2 and is not
backwards compatible. Use the [Traefik docs](https://docs.traefik.io/reference/static-configuration/file/)
to recreate your custom configuration using the `_confkey_` variables.
#### `traefik_api`
The way API is defined in Traefik v2 allows you, to use [several diffrent
configurations](https://docs.traefik.io/operations/api/). For the sake of
simplicity, we dropped the automatic generation of an api config, as it not
simply mergeable with a custom config and could lead to unforseen side effects.
To setup a simple, insecure api on container port `8080`, use the following
config (**Note**: this example is insecure, please consider securing your api
for use in production):
```yaml
traefik_confkey_api:
insecure: true
dashboard: true # use this for enabling the dashboard
traefik_ports:
- '80:80'
- '443:443'
- '8080:8080'
```
This will automatically configure an [entrypoint on port `8080`](https://docs.traefik.io/operations/api/).
#### `traefik_ping`
Similar to the api definition, the ping definition allows custom configuration
over multiple diffrent configuration keys, making an automatically generated
config unfeasable.
Follow the [Traefik config docs about ping](https://docs.traefik.io/operations/ping/)
to find the configuration you want to apply. As an Example, take a look at this
config, which will expose the ping endpoint on port `8082`:
```yaml
traefik_confkey_entryPoints:
ping:
address: ':8082'
traefik_confkey_ping:
entryPoint: 'ping'
traefik_ports:
- '80:80'
- '443:443'
- '8082:8082'
```