etcd: remove etcd entries from mdns#1556
etcd: remove etcd entries from mdns#1556openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
There was a problem hiding this comment.
I think we should stop using the etcd discovery domain all together...
There was a problem hiding this comment.
I couldn't find where to get the base domain from. Any suggestion?
There was a problem hiding this comment.
I think the baremetal-runtime-cfg has a way to provide the cluster domain at runtime.. that might be an option?
There was a problem hiding this comment.
I can change it here to {{ .Cluster.Domain }} but many of the templates are not rendered via baremetal-runtimecfg, so I'd rather leave {{ .EtcdDiscoveryDomain }} alone until we decide to effectively get rid of it globally.
There was a problem hiding this comment.
I can change it here to {{ .Cluster.Domain }} but many of the templates are not rendered via baremetal-runtimecfg, so I'd rather leave {{ .EtcdDiscoveryDomain }} alone until we decide to effectively get rid of it globally.
api-int. is plain wrong imo, it works because that's the equal today. so i don't see why we would continue to use it..?
There was a problem hiding this comment.
OK, I misunderstood your first comment - I'll make the change.
There was a problem hiding this comment.
This is just checking that the DNS server is responding. It doesn't matter what record we look up. api-int happens to be a known name that should always be there.
There was a problem hiding this comment.
This is just checking that the DNS server is responding. It doesn't matter what record we look up. api-int happens to be a known name that should always be there.
api-int.<cluster domain> is a known DNS name that should always be there, and not api-int.<etcd discovery domain>
There was a problem hiding this comment.
Ah, Github ate the domain part of your comment. I thought you were objecting to the use of api-int in general. :-)
|
@mandre I'd be very happy to see this and backported to 4.4. It will reduce the risk of people accidentally depending on "naughty" things |
|
/retest |
|
/test e2e-openstack /cc rgolangh celebdor cybertron jcpowermac Could you have a look? This PR touches the BM, openStack, ovirt and vsphere mDNS config. |
|
I've tested this on baremetal, and while the deployment works, it appears to be breaking our loadbalancing. This is because we repurposed the SRV record for getting the haproxy backends, and if we remove it we end up with no backends and thus no load balancing. I'm looking into whether there is another way we can handle that, but because baremetal-runtimecfg runs so early in the deployment I'm not sure whether we can use the same methods that etcd is to get the node addresses. If any other platforms are also using haproxy for loadbalancing they should probably verify that this doesn't result in an invalid haproxy config too. |
|
For vSphere IPI (starting with 4.5) we were following baremetal. So if baremetal works most likely vsphere will as well. The current test is for UPI only. |
|
@celebdor oVirt should fail on the same thing. |
Indeed, I hadn't notice the broken haproxy config. Putting this on hold for now since it breaks on all platforms. |
|
SRV records should no longer be a dependency for haproxy config thanks to openshift/baremetal-runtimecfg#52. |
|
I verified that this works on baremetal now so should be good to go from our end. |
|
I've also checked that it worked for OpenStack. I was waiting for #1666 to merge to avoid merge conflicts but could push the rebased patch so everyone can try with their platform. |
|
/retest |
|
/test e2e-openstack |
|
/lgtm ovirt Thanks @mandre ! |
|
/test e2e-aws |
There was a problem hiding this comment.
should we use the https://github.com/openshift/api/blob/95abe2d2f4223d5931e418bf8e4d3773d16b42c0/config/v1/types_infrastructure.go#L74-L78
So that we are not assuming the api-int subdomain exists on EtcdDiscoveryDomain. Because that is technically not true or part of the API.
There was a problem hiding this comment.
Similar to openshift/installer#3265, this removes the etcd entries from mdns config because etcd no longer uses DNS.
|
/test e2e-openstack |
|
/hold cancel |
|
/test e2e-openstack |
|
/test e2e-aws-scaleup-rhel7 |
|
/test e2e-aws-scaleup-rhel7 |
|
/lgtm |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cybertron, dougsland, ericavonb, mandre, rgolangh, sdodson The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/cherry-pick release-4.5 |
|
@cybertron: new pull request created: #1917 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Similar to openshift/installer#3265, this
removes the etcd entries from mdns config because etcd no longer uses
DNS.