Ivan Ka
The proposed enhancement directly impacts several security domains within the Adobe Common Controls Framework CCF: It actually improves, no objections - Secure Communication (SC): - SC-8 (Transmission Confidentiality and Integrity):...
Not sure why is required. HTTP probably not as secure, but secure enough for our use cases, and it provide common interfaces like openapi and other cool stuf. @mloiseleur is...
/reopen /lifecycle frozen
There is no point to add/support a new flag for something that is already supported. For advanced use, try to understand how to FQDN templating per your requirement. https://github.com/kubernetes-sigs/external-dns/blob/master/docs/advanced/fqdn-templating.md. You...
You are missing concrete Kubernetes manifests and examples of what you have already tried with the existing `--fqdn-template` flag and|or externa-dns annotations. Without manifests and expected/actual DNS records, it is...
Share kubernetes manifests with `spec.status` and all external-dns flags (not helm)
Without spec.status is just guessing. Have you tried staging docker image?
When a manifest is applied, a controller (like the AWS Load Balancer Controller) modifies the spec.status https://stackoverflow.com/questions/48134304/what-is-the-meaning-of-status-value-in-kubernetes-manifest-file. This is where ExternalDNS reads annotations and spec.status values to make its decisions....
It's not feasible to tie ingress to a specific implementation like the AWS Load Balancer controller, given the large number of ingress controllers available.