We use an ExternalName service to forward traces to our application agnostic jaeger instance that we deploy in the observe namespace. We need this deployed in advance for train-ticket otherwise the pods will crash. When I made this change in the conductor, it broke all the other apps. @Saadmrp1038 pushed in a hotfix which showcases this bug: #541.
Conveniently though, train-ticket has a kubernetes job for setup, which is a convenient place to add the external name service.
This PR is also useful to see the initial jaeger changes.
We use an
ExternalNameservice to forward traces to our application agnostic jaeger instance that we deploy in the observe namespace. We need this deployed in advance for train-ticket otherwise the pods will crash. When I made this change in the conductor, it broke all the other apps. @Saadmrp1038 pushed in a hotfix which showcases this bug: #541.Conveniently though, train-ticket has a kubernetes job for setup, which is a convenient place to add the external name service.
This PR is also useful to see the initial jaeger changes.