-
Notifications
You must be signed in to change notification settings - Fork 39k
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
Federation: allow specification of dns zone by ID #36336
Federation: allow specification of dns zone by ID #36336
Conversation
@quinton-hoole @madhusudancs this is the second part of #34901. I think we can leave the third part (optimizing changeset application) to 1.6 unless we actually hit it in production... |
dfe53a4
to
22fe985
Compare
22fe985
to
39cd6cd
Compare
Jenkins GCI GCE e2e failed for commit 22fe9853defc63e4b24b39a318d87f8d335e8736. Full PR test history. The magic incantation to run this job again is |
Jenkins GCE e2e failed for commit 22fe9853defc63e4b24b39a318d87f8d335e8736. Full PR test history. The magic incantation to run this job again is |
Jenkins GCI GKE smoke e2e failed for commit 22fe9853defc63e4b24b39a318d87f8d335e8736. Full PR test history. The magic incantation to run this job again is |
Jenkins Kubemark GCE e2e failed for commit 22fe9853defc63e4b24b39a318d87f8d335e8736. Full PR test history. The magic incantation to run this job again is |
Jenkins GCE etcd3 e2e failed for commit 22fe9853defc63e4b24b39a318d87f8d335e8736. Full PR test history. The magic incantation to run this job again is |
Jenkins GKE smoke e2e failed for commit 22fe9853defc63e4b24b39a318d87f8d335e8736. Full PR test history. The magic incantation to run this job again is |
Jenkins unit/integration failed for commit 22fe9853defc63e4b24b39a318d87f8d335e8736. Full PR test history. The magic incantation to run this job again is |
Jenkins verification failed for commit 39cd6cdc80fc8305136c44a90db50057607fd86d. Full PR test history. The magic incantation to run this job again is |
If we have a public & private zone with the same name (which is common on AWS), this means we can still create records. Also tighten up some of the logic to allow for zones with duplicate names.
39cd6cd
to
df42806
Compare
@quinton-hoole can we squeeze this in before feature-freeze :-) ? |
LGTM. Thanks @justinsb |
Removing do-not-merge; I think it's the same bug where mergebot doesn't remove the release-note label once a release-note is applied. |
Fix #33898 |
hmm, there are two builds which succeeded but did not get marked as green |
@k8s-bot test this [guess broken during the github outage this morning?] |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
If we have a public & private zone with the same name (which is common
on AWS), this means we can still create records. Also tighten up some
of the logic to allow for zones with duplicate names.
This change is