[09:44:36] <brouberol>	 Hi y'all! I don't know whether this is best suited for #-sre or here, but I'll take my chances. I'd like to add the service backing stats.wikimedia.org to the service mesh. The way the service is setup is stats.wikimedia.org --> ATS --> https://analytics-web.discovery.wmnet:8443 (on an-web1001.eqiad.wmnet). It is SSL terminated by an envoy
[09:44:36] <brouberol>	 instance, and forwarded locally to an apache server on port 80
[09:45:45] <brouberol>	 Turns out that for that service to be integrated to the mesh, it also needs to belong to the service catalog, and I'm not too sure as to how to do this for this kind of "simple" setup. I've mostly added services under k8s ingress or LVS, but this is neither
[13:08:45] <claime>	 brouberol: I think you'd use the first example in https://wikitech.wikimedia.org/wiki/Kubernetes/Add_a_new_service#Add_in_Service_Mesh, it's discovery enabled right?
[13:09:45] <brouberol>	 it is discovery enabled indeed. Although that example assumes that the service is also defined in the service.yaml catalog, right? 
[13:09:53] <claime>	 hmmm yeah
[13:10:40] <brouberol>	 and *that* is what I'm unsure of, for this type of discovery "CNAME to a single host" kind of setup 
[13:13:06] <claime>	 yeah, I'm not sure either
[13:15:29] <claime>	 Hmm it's not discovery enabled
[13:15:42] <claime>	 The record is a CNAME, and there's nothing in conftool
[13:18:06] <claime>	 You can look at the graphite definition for a similar setup I think
[13:19:22] <brouberol>	 ok, I think I've been tricked by the CNAME being analytics-web.discovery.wmnet, but there's nothing in conftool
[13:19:39] <brouberol>	 it's just a CNAME that happens to have 'discovery
[13:19:41] <brouberol>	 ' in it
[13:20:01] <claime>	 yeah
[13:20:32] <brouberol>	 thanks, I'll have a look at graphite