On 10/16/19 7:01 PM, Brooke Storm wrote:
The k8s haproxy being the replacement for the current k8s control plane, I think it should follow the same pattern. The current one is k8s-master.tools.wmflabs.org http://k8s-master.tools.wmflabs.org in tools. That suggests the next one would be k8s-control.tools.wmflabs.org http://k8s-control.tools.wmflabs.org or wmcloud.org http://wmcloud.org In toolsbeta it would be the same pattern, which is what we were doing, but we haven’t changed master to control yet. That seems to follow the rest of our tooling fine?
So we have several options:
* decide the prefix: either "k8s", or "k8s-control". * decide subdomain: either ".tools.eqiad1." or ".tools." * decide on the domain: "wikimedia.cloud" or "wmcloud.org"
Complete FQDNs options would be:
* k8s.eqiad1.tools.wikimedia.cloud * k8s-control.tools.eqiad1.wikimedia.cloud * k8s.tools.wikimedia.cloud * k8s-control.tools.wikimedia.cloud
* k8s.eqiad1.tools.wmcloud.org * k8s-control.tools.eqiad1.wmcloud.org * k8s.tools.wmcloud.org * k8s-control.tools.wmcloud.org
Is not clear to me if this should be wmcloud.org or wikimedia.cloud. Since this was previously wmflabs.org I would bet for wmcloud.org. But on the other hand, this is not a public IP, and from that point of view "wikimedia.cloud" seems to be a better fit. Other thinking is that "wikimedia.cloud" is only for instances (like we do with eqiad.wmflabs) and <project>.wmcloud.org something we can create/delegate per-project.
At first, I don't see any special value in having "eqiad1" in the wmcloud.org domain. So I guess I'm voting for any of these options:
* k8s.tools.wmcloud.org * k8s-control.tools.wmcloud.org
@bstorm, the only reason I don't like about having "k8s-control" is that we serve other stuff, not just the API (ingress too). So my final +1 is for:
* k8s.tools.wmcloud.org
thoughts?
I think we should update our DNS document to mention whatever pattern we decide.