ExternalDNS

The source code and default configuration of the Building Block is available in our code.sysEleven.de. Infos on release notes and new features please follow the link Release notes external-dns.

See the Github issue for more information if you like to use your own DNS Solution or an established Deployment ( as one of the Provider mentioned in the github.com link) there is no restrictions to do so. Please refer to the appropriate documentation from your provider.

Adding the Building Block

Add the directory syseleven-external-dns to your control repository. Add a .gitlab-ci.yml to the directory with the following content:

include:
  - project: syseleven/building-blocks/helmfiles/external-dns
    file: JobDevelopment.yaml
    ref: 5.16.3
  - project: syseleven/building-blocks/helmfiles/external-dns
    file: JobStaging.yaml
    ref: 5.16.3
  - project: syseleven/building-blocks/helmfiles/external-dns
    file: JobProduction.yaml
    ref: 5.16.3

Remove environments you are not using by removing their include.

Known Issues

  • When using designate as DNS provider, e.g. with SysEleven DNSaaS, cert-manager will not correctly sync records when there is a external-dns.alpha.kubernetes.io/ttl annotation. The record will get created in one run and be deleted in the next run.

Required configuration

No confguration is required.

Monitoring

Additional alertrules

  • None

Additional Grafana dashboards

  • None

Scaling Setup

No scaling needed :

  • Usually it is not needed to scale replicas unless you have an excessive amount of ingress/service creation requests
  • Requests/limits for CPU/memory can be adjusted

Release-Notes

Please find more infos on release notes and new features Release notes External-DNS