-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide docker image for agent, collector, and query service #152
Comments
a travis job that
|
So I don't know why we need this before we have our discovery component built, I think that should be a priority. |
Why does it depend on discovery? We already have the ability to point agent to a single collector, once #137 is done we'll be able to point to many. But doing this PR is independent. |
No one is going to use jaeger with only static hosts |
I quite disagree. Zipkin has no support for discovery of any kind. A lot of companies are still running on pets, not cattle, static routing is perfectly fine. And there are other ways to load balance without having discovery built-in, e.g. DNS. |
I agree with @yurishkuro , running collectors behind a "static" endpoint like a load balancer or k8s service is perfectly reasonable (and our exact use case). |
I'm currently working on an OpenShift template for "production" usage. This includes setting up Cassandra, creating Dockerfiles and allowing each component to be started individually. The templates might also "just work" for Kubernetes (or need small adjustments). My current approach is:
I'm using the
On Kubernetes/OpenShift, people would just point to the service name, which happens to be exposed as a hostname. The internal DNS server will resolve to a "cluster IP", which then load balances the traffic among the pods, perhaps using some affinity logic (ie: route requests from pods on DC 1 preferably to other pods on DC 1). So, I'd say that static hosts are the proper way to do that in cloud native deployments. |
@jpkrohling we'd still need Docker images for all 3 backend components irrespective of where they run, correct? |
Correct. On my WIP branch, I have a |
Solved by #157 |
Assuming there is a cassandra instance we can point to, we need to provide working docker images for:
The text was updated successfully, but these errors were encountered: