Hi,
I have a proposal.
The new k8s haproxy is in front of the api-server and the ingress [0]. In toolsbeta we have been using the following:
toolsbeta-k8s-master.toolsbeta.wmflabs.org:6443 (api-server) toolsbeta-k8s-master.toolsbeta.wmflabs.org:30000 (ingress)
This haproxy knows which k8s nodes/controllers are UP and proxy the queries for them. Right now, this FQDN is not using a floating IP, is a simple A record pointing to the haproxy VM. This record is in the 'toolsbeta' CloudVPS project.
I've been wondering which FQDN would be nice to have in the final deployment. We have 'toolforge.org', but `whatever.toolforge.org` is intended to be a tool webservice, so I've been re-reading our DNS domains plans [1] and my proposal is to introduce a new FQDN like this:
k8s.toolforge.wmcloud.org
Then we can use it this way:
k8s.toolforge.wmcloud.org:6443 (api-server) k8s.toolforge.wmcloud.org:30000 (ingress)
This is because 'wmcloud.org' is set to become the replacement for 'wmflabs.org' which is what we are currently using for 'toolsbeta-k8s-master.toolsbeta.wmflabs.org'. We could also create k8s.toolsbeta.wmcloud.org (or whatever) in case we want to retain the toolsbeta setup online.
I hope this proposal is not increasing our naming confusion and complexity. Ideally we would use something like `k8s.toolforge.org` but that seems even more confusing in the long term.
I already requested the wmcloud.org domains to be pointed to designate [2].
Let me know!
[0] https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Networking_and_in... [1] https://wikitech.wikimedia.org/wiki/Wikimedia_Cloud_Services_team/Enhancemen... [2] https://phabricator.wikimedia.org/T235630