Posting to eventgate doesn't currently work. From the proxy logs:
{"timestamp":"2026-07-28T13:26:53.028968918Z","sequence":612,"loggerClassName":"org.jboss.logging.Logger","loggerName":"org.wikimedia.wdqs.events.QueryEventFilters","level":"WARN","message":"Event posting failure: connection timed out after 15000 ms: eventgate-analytics.discovery.wmnet/10.2.2.42:4592","threadName":"vert.x-eventloop-thread-0","threadId":24,"mdc":{},"ndc":"","hostName":"wdqs-main-external-proxy-79b7f66d87-7cbc2","processName":"/usr/lib/jvm/java-25-openjdk-amd64/bin/java","processId":1}This is because egress to eventgate isn't enabled in our Kubernetes config.
@BTullis: "Eventgate access can be enabled in one of two different ways, either through external-services, or through the service mesh that uses envoy. We can look into the pros and cons of both options." We are going with the second option.
Our current understanding of the requirements is that we need to
- enable egress at all for the service mesh
- add a discovery listener on eventgate-analytics
- change the eventgate posting host from http://eventgate-analytics.discovery.wmnet:4592 to http://localhost:6004 to go through the mesh
Additionally we should treat this as an opportunity to learn about the service mesh and network policies work so we understand it better for our future work as a platform team. We are therefore upgrading the complexity of this task to account for the time spent learning and knowledge sharing.
AC:
- update the chart to allow service mesh egress
- update the helmfile to add the discovery listener and update the event posting URL
- knowledge share about the service mesh - how does this work?