tl;dr: Minor change to DNS resolution[0] for toolforge and cloud-vps services are coming on Monday. Should have no effect but please yell if you see things break.
The whole story:
Back in 2020[1] we stopped associated new VMs with the .wmflabs top-level domain; since then all VMs have been accessed via .wikimedia.cloud instead. As of a few weeks ago, the last remaining .wmflabs VM was deleted, so we're now cleaning up code and config that supported that domain.
Right now if you try to resolve a stand-alone hostname (e.g. by typing "ping mycoolserver") the resolver will try three different fqdns: first 'mycoolserver.<projectname>.eqiad1.wikimedia.cloud.' and, failing that, 'mycoolserver.<projectname>.eqiad.wmflabs.' and, failing that, the simple name 'mycoolserver.'.
After Monday, that second fallback won't happen, so it'll either be 'mycoolserver.<projectname>.eqiad1.wikimedia.cloud.' or 'mycoolserver.'.
Most people don't use simple hostnames anyway; for those users this change will have no effect. Some toolforge applications still use the old-fashioned 'tools-redis' or 'tools-db' hostnames; we already have changes in place to resolve those correctly after the change. If there are single hostname edge cases that I don't know about and can't find, their behavior may change or break in surprising ways.
Note that fully qualified service names (for example gurwiki.analytics.db.svc.eqiad.wmflabs) are unaffected by this update. I would love to eliminate them too, but it's unclear how to identify and remove all uses so that cleanup will be left for another day.
[0] https://gerrit.wikimedia.org/r/c/operations/puppet/+/1118151
[1] https://wikitech.wikimedia.org/wiki/News/2020_Phasing_out_the_.wmflabs_domai...
_______________________________________________ Cloud-announce mailing list -- cloud-announce@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.o...