Dinar Valeev
Dinar Valeev
@nlamirault I run netshoot pod in the same namespace and I'm able to access metrics: ```shell curl http://external-dns-nonprod-external-dns:7979/metrics # HELP external_dns_controller_last_reconcile_timestamp_seconds Timestamp of last attempted sync with the DNS provider...
I don't think we need to keep backward compatibility here, as Endpoint api is long time deprecated and it is not something exposed to users to interact with
@abaguas This is cool. It just an upstream chart never worked with ServiceType=LoadBalancer. It has a conflict due to [this](https://kubernetes.io/docs/concepts/services-networking/service/#load-balancers-with-mixed-protocol-types) wasn't there. I never tested this FeatureGate
LGTM. Running this in my dev environment. So far no further issues.
Nice I'm not alone with this use case. My use case is similar but we use github releases as storage backend. Once provider is built GH [action](https://github.com/AbsaOSS/ghpages-to-tf-provider-registry) triggers Provider registry...
I think we've faced that as well when migrating from ingress-nginx into providerIngressNGINX. What we noticed that [this](https://github.com/traefik/traefik/blob/34b91218f4c89b26fb9da644ae2cf16b6de47245/pkg/provider/kubernetes/ingress-nginx/kubernetes.go#L943-L946) code makes it always ignore TLS Option. As workaround we had to...
If `nginx.ingress.kubernetes.io/ssl-redirect` is not set, we getting noop@internal route for https
Although Colima on MacOS can't forward UDP traffic, so we setup TCP there
@abaguas any blockers with this?