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
Copy file name to clipboardExpand all lines: docs/proposal/dual_engine_dns.md
+7-19Lines changed: 7 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,6 +77,8 @@ What is out of scope for this KEP? Listing non-goals helps to focus discussion
77
77
and make progress.
78
78
-->
79
79
80
+
This KEP does not aim to implement or provide a DNS proxy or DNS server functionality. Specifically, we do not support resolving DNS names on behalf of client workloads. As a result, if a `ServiceEntry` uses a non-resolvable or fake DNS domain, client workloads may fail to resolve and access the intended service. Handling such DNS resolution scenarios is explicitly out of scope for this proposal.
81
+
80
82
### Proposal
81
83
82
84
<!--
@@ -107,8 +109,10 @@ type dnsController struct {
107
109
cache cache.WorkloadCache
108
110
dnsResolver *dns.DNSResolver
109
111
// store the copy of pendingResolveWorkload.
112
+
// key is the domain name, value is the pendingResolveDomain which contains workloads and refresh rate
110
113
workloadCache map[string]*pendingResolveDomain
111
114
// store all pending hostnames in the workloads
115
+
// key is the workload name, value is the list of related hostnames
0 commit comments