You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
proposed operator install for etcd, just for supporting coredns as an external dns backend.
also, we need to provide optional changes to expose correct ports in istio as well as load balancer and security groups in order to allow for dns traffic from external networks.
in summary, we need a flag for turning off exposing core dns as public service which would also enable the etcd operator as well as the underlying network access rules.
there would need to be a proof of concept work to show how to setup a zone in route53 that would automatically point to the exposed coredns service and then additionally, setup external dns to point to the local coredns/etcd installation.
The text was updated successfully, but these errors were encountered:
The refactored design involves leveraging this coredns install with some additional pieces:
GitHub - aenix-io/etcd-operator: New generation community-driven etcd-operator!
proposed operator install for etcd, just for supporting coredns as an external dns backend.
also, we need to provide optional changes to expose correct ports in istio as well as load balancer and security groups in order to allow for dns traffic from external networks.
in summary, we need a flag for turning off exposing core dns as public service which would also enable the etcd operator as well as the underlying network access rules.
there would need to be a proof of concept work to show how to setup a zone in route53 that would automatically point to the exposed coredns service and then additionally, setup external dns to point to the local coredns/etcd installation.
The text was updated successfully, but these errors were encountered: