In the last couple of weeks, we have replaced[0] the previous software responsible for routing HTTP requests to individual Toolforge tools (ingress-nginx[1], which is now end-of-life) with a new one (Istio[2]). The primary visible change is that error pages in cases where a tool has a configured web service that is not working for one reason or another are now significantly more bare-bones, those might be improved in the future.

[0]: https://phabricator.wikimedia.org/T392356 [1]: https://github.com/kubernetes/ingress-nginx/ [2]: https://istio.io/

If you are using the Kubernetes API directly[3] to configure tool routing, you will need to migrate from old Ingress objects to new Gateway API[4] -provided HTTPRoute[5] objects.

[3]: https://wikitech.wikimedia.org/wiki/Help:Toolforge/Kubernetes [4]: https://gateway-api.sigs.k8s.io/ [5]: https://gateway-api.sigs.k8s.io/api-types/httproute/

taavi