diff --git a/docs/faq.md b/docs/faq.md index db309b385..9c9173bb6 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -254,8 +254,8 @@ one to expose DNS to the internet. To do this with ExternalDNS you can use the `--annotation-filter` to specifically tie an instance of ExternalDNS to an instance of a ingress controller. Let's assume you have two ingress controllers `nginx-internal` and `nginx-external` -then you can start two ExternalDNS providers one with `--annotation-filter=kubernetes.io/ingress.class=nginx-internal` -and one with `--annotation-filter=kubernetes.io/ingress.class=nginx-external`. +then you can start two ExternalDNS providers one with `--annotation-filter=kubernetes.io/ingress.class in (nginx-internal)` +and one with `--annotation-filter=kubernetes.io/ingress.class in (nginx-external)`. Beware when using multiple sources, e.g. `--source=service --source=ingress`, `--annotation-filter` will filter every given source objects. If you need to filter only one specific source you have to run a separated external dns service containing only the wanted `--source` and `--annotation-filter`. diff --git a/docs/tutorials/public-private-route53.md b/docs/tutorials/public-private-route53.md index 5a6bc65ca..764a7e747 100644 --- a/docs/tutorials/public-private-route53.md +++ b/docs/tutorials/public-private-route53.md @@ -241,7 +241,7 @@ spec: - --provider=aws - --registry=txt - --txt-owner-id=external-dns - - --annotation-filter=kubernetes.io/ingress.class=external-ingress + - --annotation-filter=kubernetes.io/ingress.class in (external-ingress) - --aws-zone-type=public image: k8s.gcr.io/external-dns/external-dns:v0.7.6 name: external-dns-public @@ -279,7 +279,7 @@ spec: - --provider=aws - --registry=txt - --txt-owner-id=dev.k8s.nexus - - --annotation-filter=kubernetes.io/ingress.class=internal-ingress + - --annotation-filter=kubernetes.io/ingress.class in (internal-ingress) - --aws-zone-type=private image: k8s.gcr.io/external-dns/external-dns:v0.7.6 name: external-dns-private