[08:20:20] <elukey>	 o/
[08:20:26] <elukey>	 back to the citoid migration :)
[08:20:30] <elukey>	 my idea is the following:
[08:20:57] <elukey>	 1) create citoid-ingress.discovery.wmnet and add it as allowed san/domain to the Istio gateway config
[08:21:07] <elukey>	 2) test etc..
[08:21:23] <elukey>	 3) point rest-gateway to citoid-ingress.discovery.wmnet
[08:22:21] <elukey>	 4) finally change citoid.discovery.wmnet to be a CNAME of k8s-ingress, move rest-gateway to it and remove the citoid-ingress CNAME
[08:22:45] <elukey>	 4) is really optional, we could also just remove citoid.discovery.wmnet
[08:42:16] <elukey>	 curl https://citoid-ingress.discovery.wmnet:30443/mediawiki/10.1038%2Fs41586-021-03470-x -k works nicely
[09:32:17] <elukey>	 hnowlan: o/ are you available if we move rest-gateway to citoid now?
[09:35:53] <hnowlan>	 elukey: o/ sgtm! 
[09:37:33] <elukey>	 ack thanks! proceeding with staging
[09:46:50] <elukey>	 hnowlan: I am trying to hit staging with `curl https://staging.svc.eqiad.wmnet:4113/en.wikipedia.org/v1/data/citation/mediawiki/10.1038%2Fs41586-021-03470-x -k -i` but I get a 404, am I missing headers or something else?
[09:47:13] <hnowlan>	 yeah, doesn't look right - looking into that atm, I might be wrong about it having parity with the prod gateway 
[09:47:18] <hnowlan>	 I see the routes defined 
[09:48:03] <hnowlan>	 and envoy is matching the route 
[09:49:16] <hnowlan>	 the 404 is coming from the service, so something weird is going on with the SNI or header mangling
[09:52:17] <elukey>	 ok so it lands to citoid in staging, but the mesh/nodejs returns 404
[09:54:08] <hnowlan>	 let me try to hack something in place for a second
[09:55:54] <hnowlan>	 okay, found the problem - give me a few minutes to write a patch to fix some bad behaviour in the `ingress` option 
[09:57:40] <elukey>	 Alex mentioned also https://gerrit.wikimedia.org/r/c/operations/deployment-charts/+/1133966/1/helmfile.d/services/wikifunctions/values-main-orchestrator.yaml
[09:58:02] <elukey>	 we'll see if it is needed
[09:58:16] <elukey>	 anyway, thanks a lot, sorry for the extra hassle
[10:07:23] <hnowlan>	 no hassle, this is a gateway/envoy mess. For now I'm going with the quick solution but this exposes an uncomfortable edge of the config that kinda relates to envoy's config
[10:13:09] <elukey>	 ah snap didn't know it
[10:13:11] <elukey>	 +1ed
[10:18:23] <hnowlan>	 staging is responding as expected now I think
[10:19:25] <elukey>	 yeppp!
[10:19:42] <elukey>	 shall I do codfw?
[10:20:16] <hnowlan>	 go for it
[10:22:44] <elukey>	 I am trying
[10:22:45] <elukey>	 curl https://rest-gateway.svc.codfw.wmnet:4113/en.wikipedia.org/v1/data/citation/mediawiki/10.1038%2Fs41586-021-03470-x -k -i
[10:22:49] <elukey>	 but I get 404
[10:25:13] <hnowlan>	 if you add -H "Host: rest-gateway.discovery.wmnet" it'll work
[10:25:31] <elukey>	 I was about to say, same for eqiad :D
[10:26:03] <elukey>	 niceee
[10:29:28] <elukey>	 thanks lot hnowlan!
[10:30:17] <hnowlan>	 np, sorry for the bump! 
[10:30:34] <elukey>	 nono please!