Support Jaeger production mode
While we technically provide the ability to switch Jaeger from allInOne
to production
, I've found in testing that this doesn't really work as it should. Primary issue is with networkPolicies interfering with communication to Elasticsearch, but there may be more issues as well. This will involve a bit of discovery effort to find out what we need to change to get production
mode working.
There is a brief overview of the deployment strategies in https://www.jaegertracing.io/docs/1.29/operator/#deployment-strategies . For BB you can deploy with the production stategy by overriding in your values:
jaeger:
values:
jaeger:
spec:
strategy: "production"
Once you deploy you will likely see issues with the pods being able to hit the Elastic instance. A good place to start is with the policies that already exist:
- https://repo1.dso.mil/platform-one/big-bang/apps/core/jaeger/-/blob/main/chart/templates/bigbang/networkpolicies/egress-logging.yaml
- https://repo1.dso.mil/platform-one/big-bang/apps/core/elasticsearch-kibana/-/blob/main/chart/templates/bigbang/networkpolicies/es-allow.yaml#L2-23
We will likely need to adjust these labels depending on the deployment strategy being used (from initial checking, it looks like the collector and query pods need access to Elastic - at minimum).
AC:
-
Network policies updated to support production mode -
Any other changes needed made so that production mode is supported in a "default" BB deployment (i.e. nothing has to be deleted or manually edited)