-
Feature Request
-
Resolution: Done
-
Major
-
openshift-4.12.z
-
None
-
False
-
None
-
False
-
Not Selected
-
-
1. Proposed title of this feature request
- External DNS Operator should support kubernetes ingress type
2. What is the nature and description of the request?
External DNS Operator only works with Service and OpenShift Route, but not generic ingress.
3. Why does the customer need this? (List the business requirements here)
- AWS/ROSA customer wants to use AWS Application Load Balancer as the target for the DNS records created by External DNS Operator. Currently only the OpenShift router's hostname is supported as the target for the DNS records.
- AWS/ROSA customer wants to use Ingress + [AWS Application Load Balancer Operator](https://docs.openshift.com/container-platform/4.11/networking/aws_load_balancer_operator/install-aws-load-balancer-operator.html)
- AWS/ROSA customer wants to use OpenShift External DNS Operator to add Ingress DNS records automatically
4. List any affected packages or components.
- [aws load balancer controller](https://docs.openshift.com/container-platform/4.11/networking/aws_load_balancer_operator/install-aws-load-balancer-operator.html)
- [external DNS Operator](https://docs.openshift.com/container-platform/4.12/networking/external_dns_operator/understanding-external-dns-operator.html)
- relates to
-
NE-1299 External DNS support for preexisting Route53 for Shared VPC clusters
- Closed