Update Jaeger version to 1.5.0 and document used docker tags (#89)

* Jaeger Version++ && Version documentation

Similar to #70, addresses #88

Signed-off-by: Victor Lei <KLEI22@bloomberg.net>

* Clean up Docker Tag Advice
Address PR comments and run CI tests again

Signed-off-by: Victor Lei <klei22@bloomberg.net>

* (version++)++

Signed-off-by: Victor Lei <klei22@bloomberg.net>

* Move image versions to README

Signed-off-by: Victor Lei <klei22@bloomberg.net>

* Update docker image advice
Don't tell people "Feel free to use the latest version"

Signed-off-by: Victor Lei <klei22@bloomberg.net>

README.md

@@ -7,8 +7,8 @@
 Please see [CONTRIBUTING.md](https://github.com/jaegertracing/jaeger-kubernetes/blob/master/CONTRIBUTING.md)
 
 ## Development setup
-This template uses an in-memory storage with a limited functionality for local testing and development.
-Do not use this template in production environments.
+This template uses an in-memory storage with a limited functionality for local testing and development. The image used defaults to the latest version (released)[https://github.com/jaegertracing/jaeger/releases].
+Do not use this template in production environments. Note that functionality may differ from the pinned docker versions for production. 
 
 Install everything in the current namespace:
 ```bash
@@ -21,6 +21,9 @@ can be used instead.
 
 ## Production setup
 
+### Pinned Production Version
+The docker image tags are manually pinned and manually updated. You should use the current pinned version for production. 
+
 ### Backing storage
 
 The Jaeger Collector and Query require a backing storage to exist before being started up. As a starting point for your own 
@@ -148,6 +151,10 @@ kubectl run jaeger-spark-dependencies --schedule="55 23 * * *" --env="STORAGE=ca
 
 If you want to run the job only once and immediately then remove scheduled flag.
 
+## Deploying Docker Tags
+The Jaeger project automatically creates new Docker images with tags that mirror the release number. The production manifests uses pinned versions as to not accidentally break people on new releases.
+> A general tip for deploying docker images (i.e. on kubernetes): it's recommended that you do not use the tag `:latest` in production but rather pin the latest version. See the [kubernetes best practices](https://kubernetes.io/docs/concepts/configuration/overview/#container-images) for more details.
+
 ## Helm support
 A curated [Chart for Kubernetes Helm](https://github.com/kubernetes/charts/tree/master/incubator/jaeger) that adds all components required to run Jaeger.
 

jaeger-production-template.yml

@@ -33,7 +33,7 @@ items:
           jaeger-infra: collector-pod
       spec:
         containers:
-        - image: jaegertracing/jaeger-collector:1.2
+        - image: jaegertracing/jaeger-collector:1.5.0
           name: jaeger-collector
           command:
             - "/go/bin/collector-linux"
@@ -119,7 +119,7 @@ items:
           jaeger-infra: query-pod
       spec:
         containers:
-        - image: jaegertracing/jaeger-query:1.2
+        - image: jaegertracing/jaeger-query:1.5.0
           name: jaeger-query
           command:
             - "/go/bin/query-linux"
@@ -179,7 +179,7 @@ items:
       spec:
         containers:
         - name: agent-instance
-          image: jaegertracing/jaeger-agent:1.2
+          image: jaegertracing/jaeger-agent:1.5.0
           command:
           - "/go/bin/agent-linux"
           - "--config-file=/conf/agent.yaml"

production/cassandra.yml

@@ -120,7 +120,7 @@ items:
       spec:
         containers:
         - name: jaeger-cassandra-schema
-          image: jaegertracing/jaeger-cassandra-schema:1.2
+          image: jaegertracing/jaeger-cassandra-schema:1.5.0
           env:
             - name: MODE
               value: "prod"