Signed-off-by: njuettner <nick@zalando.de>

docs/designate: add snippet for rbac env

* extend the external-dns deployment to work within a RBAC enabled
environment
* add short hint how to mount/use/trust self-sign certificates

docs: fix log-level param in tutorials

* arg --debug is now --log-level=debug
* flag --log-level was merged 2017 with
  PR https://github.com/kubernetes-sigs/external-dns/pull/339

* Move into kubernetes-sigs organization

* Disable labeler action for forks

Adding labels on PR

Update labeler.yml

added support for using nodes as source

Group equal DNS names into same endpoint

Propose a few doc changes to make the use of namespace more clear

Change ApplyChanges in RFC2136 to batch update

#582: Unknown Serviceaccount error

Add RBAC manifest, update wording around IAM policy

Seems like there was attempts to fix it but change didn't make it to master

Run go mod tidy with go 1.13

v0.5.17

Signed-off-by: njuettner <nick@zalando.de>

Support Cloudflare API Token Auth

upgrade go version to 1.13 in external-dns

exoscale: add context support

Signed-off-by: Yoan Blanc <yoan@dosimple.ch>

Fix AWS IAM Roles for Service Accounts permission problem.

Amazon EKS supports IAM Roles for Service Accounts. It mounts tokens
files to `/var/run/secrets/eks.amazonaws.com/serviceaccount/token`.
Unfortunately, external-dns runs as 'nobody' so it cannot access this
file. External DNS is then unable to make any AWS API calls to work:

```
time="2019-09-11T07:31:53Z" level=error msg="WebIdentityErr: unable to read file at /var/run/secrets/eks.amazonaws.com/serviceaccount/token\ncaused by: open /var/run/secrets/eks.amazonaws.com/serviceaccount/token: permission denied"
```

See: https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts-technical-overview.html

Below are the file permissions mounted on External DNS pod:

```
~ $ ls -al /var/run/secrets/eks.amazonaws.com/serviceaccount/
total 0
drwxrwxrwt    3 root     root           100 Sep 11 06:40 .
drwxr-xr-x    3 root     root            28 Sep 11 06:40 ..
drwxr-xr-x    2 root     root            60 Sep 11 06:40 ..2019_09_11_06_40_49.865776187
lrwxrwxrwx    1 root     root            31 Sep 11 06:40 ..data -> ..2019_09_11_06_40_49.865776187
lrwxrwxrwx    1 root     root            12 Sep 11 06:40 token -> ..data/token
~ $ ls -al /var/run/secrets/eks.amazonaws.com/serviceaccount/..data/token
-rw-------    1 root     root          1028 Sep 11 06:40 /var/run/secrets/eks.amazonaws.com/serviceaccount/..data/token
```

This commit fixes this problem by specifying securityContext to make
mounted volumes with 65534 (nobody) group ownership.