TrueCloudLab/coredns
16
0
Fork 2
Code Issues Pull requests 4 Projects Releases Packages Wiki Activity Actions

[fix:documentation] Clarify autopath README (#6750)

Browse source 
Signed-off-by: Robbie Ostrow <ostrowr@users.noreply.github.com>
This commit is contained in:
Robbie Ostrow 2024-07-01 08:18:35 -07:00 • committed by GitHub
parent db17037a25
commit 771d64dbea
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
plugin/autopath/README.md
View file

@ -57,7 +57,7 @@ path) in the following case. To properly build the search path of a client *auto
the namespace of the a Pod making a DNS request. To do this, it relies on the *kubernetes* plugin's the namespace of the a Pod making a DNS request. To do this, it relies on the *kubernetes* plugin's
Pod cache to resolve the client's IP address to a Pod. The Pod cache is maintained by an API watch Pod cache to resolve the client's IP address to a Pod. The Pod cache is maintained by an API watch
on Pods. When Pod IP assignments change, the Kubernetes API notifies CoreDNS via the API watch. on Pods. When Pod IP assignments change, the Kubernetes API notifies CoreDNS via the API watch.
However, that notification is not instantaneous. In the case that a Pod is deleted, and it's IP is However, that notification is not instantaneous. In the case that a Pod is deleted, and its IP is
immediately provisioned to a Pod in another namespace, and that new Pod make a DNS lookup *before* immediately provisioned to a Pod in another namespace, and that new Pod make a DNS lookup *before*
the API watch can notify CoreDNS of the change, *autopath* will resolve the IP to the previous Pod's the API watch can notify CoreDNS of the change, *autopath* will resolve the IP to the previous Pod's
namespace. namespace.