Robin Kearney
9047424a62
* initial commit * Moving to stable * Some review fixes * Typo * More review comments * Reflecting the change to a list * Minor changes to version and description. * This needs to be set to something. * reflecting the change in values.yaml from the previous commit. * Reflecting the move to `stable/`. * Preventing global namespace collisions. * Adding service account support. * Renaming to avoid confusion * Removing the this because it can cause problems. * This was unintended, removing lets K8s use the default. * Review fixes. * Moving the majority of these into `extraArgs`. I've picked the set of command line options we use in our rig, i.e. the ones where we don't use the defaults. I /think/ this is a sane set. * Minor tweaks * Conform to standard RBAC pattern * Update NOTES.txt * Update README * Make domainFilters a list
external-dns
Chart Details
This chart will do the following:
- Create a deployment of external-dns within your Kubernetes Cluster.
Currently this uses the Zalando hosted container, if this is a concern follow the steps in the external-dns documentation to compile the binary and make a container. Where the chart pulls the image from is fully configurable.
Notes
You probably want to make sure the nodes have IAM permissions to modify the R53 entries. More on this later.
Installing the Chart
To install the chart with the release name my-release:
$ helm install --name my-release stable/external-dns
Configuration
The following tables lists the configurable parameters of the external-dns chart and their default values.
| Parameter | Description | Default |
|---|---|---|
domainFilters |
Limit possible target zones by domain suffixes (optional). | [] |
extraArgs |
Optional object of extra args, as name: value pairs. Where the name is the command line arg to external-dns. |
{} |
image.name |
Container image name (Including repository name if not hub.docker.com). |
registry.opensource.zalan.do/teapot/external-dns |
image.pullPolicy |
Container pull policy. | IfNotPresent |
image.tag |
Container image tag. | v0.4.2 |
podAnnotations |
Additional annotations to apply to the pod. | {} |
policy |
Modify how DNS records are sychronized between sources and providers (options: sync, upsert-only ). | upsert-only |
provider |
The DNS provider where the DNS records will be created (options: aws, google, azure, cloudflare, digitalocean, inmemory ). | aws |
rbac.create |
If true, create & use RBAC resources | false |
rbac.serviceAccountName |
existing ServiceAccount to use (ignored if rbac.create=true) | default |
resources |
CPU/Memory resource requests/limits. | {} |
sources |
List of resource types to monitor, possible values are fake, service or ingress. | [service, ingress] |
Specify each parameter using the --set key=value[,key=value] argument to helm install.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
$ helm install --name my-release -f values.yaml stable/external-dns
Tip
: You can use the default values.yaml