You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previous context needed:
The issue: link
This Pull Request: link
Current behavior:
User has 3 hosted zones in AWS:
Public: mydomain.com
Private: internal.mydomain.com
Private: us-west-2.internal.mydomain.com
User creates an ingress with host: testdeploy.us-west-2.internal.mydomain.com
One A record to the AWS Load Balancer is created on each of the 3 Hosted Zones to k8s-ingress-1234abcd.us-west-2.elb.amazonaws.com with the corresponding 2 TXT records.
Desired behavior:
The external-dns controller should detect that the record is only wanted on the us-west-2.internal.mydomain.com Hosted Zone in this case.
Discussion:
This will be done modifying the current function suitableZones on the aws.go provider. With the addition of rolling back the fix for overlapping zones and a regression to check that:
Users that update to the new version of external-dns will plan to delete the unused Route53 Records
Users that start using external-dns on the new version won't be affected at all
Try to detect use cases where a feature flag is needed to keep the original behavior (We really don't want to do this but if there are use cases for this we'll need to think about a solution for this)
Previous context needed:
The issue: link
This Pull Request: link
Current behavior:
User has 3 hosted zones in AWS:
Public: mydomain.com
Private: internal.mydomain.com
Private: us-west-2.internal.mydomain.com
User creates an ingress with host: testdeploy.us-west-2.internal.mydomain.com
One A record to the AWS Load Balancer is created on each of the 3 Hosted Zones to k8s-ingress-1234abcd.us-west-2.elb.amazonaws.com with the corresponding 2 TXT records.
Desired behavior:
The external-dns controller should detect that the record is only wanted on the
us-west-2.internal.mydomain.com
Hosted Zone in this case.Discussion:
This will be done modifying the current function
suitableZones
on the aws.go provider. With the addition of rolling back the fix for overlapping zones and a regression to check that:cc: @Raffo @mloiseleur
The text was updated successfully, but these errors were encountered: