Releases: goci-io/aws-external-cluster-dns
Releases · goci-io/aws-external-cluster-dns
0.4.1
Changes
- filter empty domain names (#24) @etwillbefine
0.4.0
Changes
See previous Release Candidate https://github.com/goci-io/aws-external-cluster-dns/releases/tag/0.4.0-rc1
🚧 Maintenance
- use official bitnami release again (#23) @etwillbefine
0.4.0-rc1
Changes
- temporarily use release with non clusterrole (#21) @etwillbefine
- deploy cluster role when not namespace bound (#22) @etwillbefine
- allow to restrict external dns to a single namespace (#20) @etwillbefine
- psp enabled defaults to false, configureable (#19) @etwillbefine
🐛 Bug Fixes
- set assume role config when kiam is not enabled (#18) @etwillbefine
Release Candidate only
This Release references a Chart from a Fork of bitnami/charts.
There is no guarantee about the Availability of this temporary Chart-Release. Complete Release depends on bitnami/charts#3412
0.3.0
Changes
- optionally load overwrite values file (#15) @etwillbefine
- correctly trim leading and trailing dots (#14) @etwillbefine
🚀 Features
- making replicas configureable, create pdb only when using 1 replica (#17) @etwillbefine
🚧 Maintenance
- use newer k8s_pod_disruption_budge resource (#16) @etwillbefine
0.2.0
Changes
- external dns requires list hosted zones permissions (#13) @etwillbefine
- feat: use full iam role arn for kiam annotation (#4) @etwillbefine
- ci: update validate action (#5) @etwillbefine
- ci: update github actions (#3, #6, #7) @goci-bot
🚀 Features
- allow attaching required permissions to existing role (#12) @etwillbefine
- external id support using assumable-iam-role module (#10) @etwillbefine
🚧 Maintenance
- chore: set repository url and remove deprecated data source (#8) @etwillbefine
‼️ Breaking changes
- external id support using assumable-iam-role module (#10) @etwillbefine
- do not configure provider within module (#9) @etwillbefine
💬 Documentation
- clarify on how to use IAM role (#11) @etwillbefine
0.1.0
Initial release. Contains:
- Helm deployment of external-dns
- IAM role to use for changing DNS records in Route53
- Discovery of DNS records based on ingress hosts only (default)
- Pod disruption budget as there is no need for HA
- Domain/Hosted zone filters based on dns names
- Assume role or kiam pod annotation configuration
- Support leading dots to prevent changes to the root domain (4cca293)