Based on T246431: PyBal healthchecks should specify User-Agent instead of using "Twisted PageGetter", I'm guessing the UA of Twisted PageGetter is indeed Pybal here too...
In a 24H period, it does result in ~2.1M https-expected deprecation warnings being emitted from the MW API...
Is there anything we can do to reduce thiis?
The only solution here is to either silence the https expected warnings or disable the http load-balancer completely. I'm going with that latter option as we wanted to do it in the first place.
Change 766571 had a related patch set uploaded (by Giuseppe Lavagetto; author: Giuseppe Lavagetto):
[operations/puppet@production] mx: use https when connecting to the mw api
Change 766573 had a related patch set uploaded (by Giuseppe Lavagetto; author: Giuseppe Lavagetto):
[operations/puppet@production] api: remove http endpoint from pybal
Change 766571 merged by Giuseppe Lavagetto:
[operations/puppet@production] mx: use https when connecting to the mw api
Change 766573 merged by Giuseppe Lavagetto:
[operations/puppet@production] api: remove http endpoint from pybal
Mentioned in SAL (#wikimedia-operations) [2022-03-01T09:22:14Z] <_joe_> restarted pybal on lvs2009, the mw api is now effectively https-only in codfw T287820
As of now all of the API is https-only at the lvs layer and pybal is not checking http anymore.