This repository has been archived by the owner on May 18, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 158
Naming to support other backends #23
Comments
First we have to split cassandra related stuff from jaeger deployment. Adding ES will probably require some changes to jaeger deployment (use some flag etc.). The problem is that K8s resource files do not support parameters, so we might use something like helm (I don't know yet). In terms of storage templates maybe it would be if we could reuse ES deployment from k8s and just make sure that it works with Jaeger. |
Related to #54 |
I will close this in favour of #54 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The Elasticsearch backend is ready, I assume we'll eventually want to have templates for it as well. How should this affect the naming of directories and files in this repo?
The text was updated successfully, but these errors were encountered: