7 Commits

Author	SHA1	Message	Date
John Gardiner Myers	06227c1fbf	Make unit tests more strict about record type	2023-03-30 17:47:59 -07:00
Andy Bursavich	74ffff6c26	gofumpt	2022-09-20 20:48:57 -07:00
Andrey Lebedev	a53498735b	openshift route source: better use of route status	2022-02-21 13:26:50 +01:00
Andrey Lebedev	4f41229820	Pass stop channel to informer factory instances	2022-01-22 21:31:29 +01:00
Miheer Salunke	ab8a62045e	In OCP when you have multiple ingress controllers the route's status Ingress object get populated with multiple router canonical names. So in this case, the external dns tries to add multiple CNAME records for same host in the same hosted zone which is a violation of RFC 1912  and therefore is rejected by standards-compliant DNS services. ... This feature adds a router field to the OCP Route Source so that a user can add an ingress controller name in flag --ocp-router-name which will be used to pick up the respective routerCanonicalHostname from Route's Status Ingress Object. Signed-off-by: Miheer Salunke <miheer.salunke@gmail.com>	2021-11-03 12:52:57 +10:00
Arjun Naik	d91b7e6b8f	Label filtering for Ingress, Service, Openshift Route sources ... Currently the `--label-filter` flag can only be used to filter CRDs which match the label selector passed through that flag. This change extends the functionality to the Ingress, Service and Openshift Route type objects. When the flag is not specified the default value is `labels.Everything()` which is an empty string, the same as before. Annotation based filter is inefficient because the filtering has to be done in the controller instead of the API server like with label filtering.	2021-10-14 11:06:55 +02:00
Andy Bursavich	5069c3f0fb	source: name files consistently with their source name	2021-07-28 07:46:35 -07:00