mirror of https://github.com/kemko/nomad.git synced 2026-01-08 19:35:41 +03:00

Files

Tim Gross 1bef639166 e2e: give containers access to dnsmasq DNS (#8536 )

By default, Docker containers get /etc/resolv.conf bound into the container
with the localhost entry stripped out. In order to resolve using the host's
dnsmasq, we need to make sure the container uses the docker0 IP as its
nameserver and that dnsmasq is listening on that port and forwarding to either
the AWS VPC DNS (so that we can query private resources like EFS) or to the
Consul DNS.

2020-07-24 14:09:18 -04:00

config

e2e: give containers access to dnsmasq DNS (#8536 )

2020-07-24 14:09:18 -04:00

consul

base podman e2e test and provisioning updates (#8104 )

2020-06-03 14:06:58 -04:00

nomad

base podman e2e test and provisioning updates (#8104 )

2020-06-03 14:06:58 -04:00

vault

e2e: refactor Vault configuration (#6561 )

2019-10-25 15:29:01 -04:00

README.md

e2e: split Packer build scripts from TF provisioning (#6542 )

2019-10-25 08:08:24 -04:00

README.md

Terraform Provisioning

These scripts are copied up to instances via Terraform provisioning and executed after launch. This allows us to update the Nomad configurations for features that land on master without having to re-bake AMIs.

What goes here?

steps that are specific to a given Nomad build: ex. all Nomad configuration files.
steps that are specific to a given EC2 instance: configuring IP addresses.

These scripts should be idempotent: copy configurations from /ops/shared to their destinations where the services expect them to be, rather than moving them.