-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added DNS Reverse Record logic for service IPs #26226
Conversation
kd.cacheLock.Lock() | ||
defer kd.cacheLock.Unlock() | ||
kd.cache.setSubCache(service.Name, subCache, subCachePath...) | ||
kd.reverseRecordMap[service.Spec.ClusterIP] = reverseRecord |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we add reverse records for petset pods (with hostname and subdomain set AND a governing headless service? Maybe that's yet another followup. Can you just file an issue on that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Filed issue #26752 to track this.
LGTM please build and push the image and get green on tests. |
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
CLAs look good, thanks! |
status on this? It's marked "do not merge"... |
will rebase today and track the merge. |
I marked it as do-not-merge since I wanted the dnsmasq PR to go in first. |
dnsmasq is in |
@k8s-bot test this issue: #IGNORE |
blocked by #26335 @girishkalele |
the test for the PR fails because #26335 is not yet merged. |
I think test failure may be related... |
rebased. waiting for test run. |
@girishkalele can you look into this. |
@girishkalele you might want to do a new kube-dns image with the code of the PR and then try.. hopefully, it is a simple case of pushing a new kube-dns image. |
If I understand correctly, I checkout your PR, build a new kube-dns from your code and push to Google Containers. Will do. |
@k8s-bot test this issue: #IGNORE |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 4224dbd. |
Automatic merge from submit-queue |
No description provided.