Skip to content

Commit

Permalink
Added workaround for kubectl logs and get pods commands (#225)
Browse files Browse the repository at this point in the history
Signed-off-by: Kevin Earls <[email protected]>
  • Loading branch information
kevinearls authored and jpkrohling committed Feb 22, 2019
1 parent abacd35 commit 6309182
Showing 1 changed file with 11 additions and 2 deletions.
13 changes: 11 additions & 2 deletions README.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ To get the pod name, query for the pods belonging to the `simplest` Jaeger inst

[source,bash]
----
$ kubectl get pods -l jaeger=simplest
$ kubectl get pods -l app.kubernetes.io/instance=simplest
NAME READY STATUS RESTARTS AGE
simplest-6499bb6cdd-kqx75 1/1 Running 0 2m
----
Expand All @@ -117,11 +117,20 @@ Similarly, the logs can be queried either from the pod directly using the pod na

[source,bash]
----
$ kubectl logs -l jaeger=simplest
$ kubectl logs -l app.kubernetes.io/instance=simplest
...
{"level":"info","ts":1535385688.0951214,"caller":"healthcheck/handler.go:133","msg":"Health Check state change","status":"ready"}
----

NOTE: On OpenShift the container name must be specified
[source,bash]
----
$ kubectl logs -l app.kubernetes.io/instance=simplest -c jaeger
...
{"level":"info","ts":1535385688.0951214,"caller":"healthcheck/handler.go:133","msg":"Health Check state change","status":"ready"}
----


For reference, here's how a more complex all-in-one instance can be created:

.all-in-one.yaml
Expand Down

0 comments on commit 6309182

Please sign in to comment.