Publish Helm chart version 0.5.0; App version: 1.189.0

README.md

@@ -37,12 +37,26 @@ $ kubectl get pod test-nodejs -n test-apps -o=jsonpath='{.metadata.labels.instan
 true
 ```
 
-Assuming that you _also_ installed the Host agent, e.g., using the `instana/agent` helm chart, the Node.js process will soon appear in your Instana dashboard.
+Assuming that you _also_ installed the Instana host agent, e.g., using the `instana/agent` helm chart, the Node.js process will soon appear in your Instana dashboard.
+For more information, refer to the [Installing the Host Agent on Kubernetes](https://www.instana.com/docs/setup_and_manage/host_agent/on/kubernetes) documentation.
 
-## Gotchas
+## Updates
 
-The Instana Autotrace Webhook will take effect on _new_ Kubernetes resources.
-That is, you may need to delete your Pods, ReplicaSets and Deployments and create them anew, for the Instana Autotrace Webhook to do its magic.
+The Instana Autotrace Webhook does not currently have an automated way of upgrading the instrumentation it will install.
+The instrumentation is delivered over the [`instana/instrumentation` image](https://hub.docker.com/repository/docker/instana/instrumentation).
+The `instana-autotrace-webhook` Helm chart will be regularly updated to use the newest `instana/instrumentation` image; so, to update the instrumentation to the latest and greatest version, you can upgrade the deployment with:
+
+```bash
+helm upgrade --namespace instana-autotrace-webhook instana-autotrace-webhook \
+  --repo https://agents.instana.io/helm instana-autotrace-webhook
+```
+
+## Gotchas and Known Limitations
+
+- The Instana Autotrace Webhook will take effect on _new_ Kubernetes resources.
+  That is, you may need to delete your Pods, ReplicaSets and Deployments and create them anew, for the Instana Autotrace Webhook to do its magic.
+- Autoprofile and colelcting some runtime metrics will only work on Node.js version 12.
+  A future version of the Helm chart will deliver native modules for other supported Node.js versions.
 
 ## Configuration
 
@@ -57,3 +71,9 @@ However, you may want to have more control over which pod is instrumented and wh
 By setting the `autotrace.opt-in=true` value when deploying the Helm chart, the Autotrace Webhook will only modify pods that carry the `instana.autotrace: true` label.
 
 Irrespective of the value of the `autotrace.opt-in`, the Autotrace Webhook will _not_ touch pods that carry the `instana.autotrace: false` label
+
+## Changelog
+
+### v0.5.0
+
+- Work towards support Helm chart upgrades to deliver new instrumentation, see the [Updates](#updates) section for more information.

incubator/instana-autotrace-webhook/templates/deployment.yml

@@ -8,7 +8,7 @@ spec:
   replicas: {{ .Values.webhook.replicas }}
   selector:
     matchLabels:
-      {{- include "instana-autotrace-webhook.commonLabels" . | nindent 6 }}
+      app.kubernetes.io/instance: instana-autotrace-webhook
   template:
     metadata:
       name: instana-autotrace-webhook

incubator/instana-autotrace-webhook/values.yaml

@@ -7,7 +7,7 @@ webhook:
   ssl:
     insecure: false
     caBundle:
-  image: containers.instana.io/instana/release/agent/instana-autotrace-webhook@sha256:4758541fd5d56922d25b0cbebcb50a0a26632b9082d43b8464df2bad3686d0ad
+  image: containers.instana.io/instana/release/agent/instana-autotrace-webhook@sha256:726acedd2f0fd4fab9d2a01eda99010186e88f66828bc73c3517ce730884c343
   imagePullPolicy: Always
   imagePullCredentials:
     registry: containers.instana.io
@@ -22,7 +22,7 @@ autotrace:
   opt_in: false
   failurePolicy: Ignore # We do not want to cause any trouble in scheduling; for local testing, use 'Fail'
   instrumentation:
-    image: instana/instrumentation@sha256:91c6a069ba19dba5416a80d45dda874d0c56a73d23ce3bc543e42a6b8330babd
+    image: instana/instrumentation@sha256:0a506a6a352bfe75e3eebc8b1ed203508cfc7bd1678e7ae49c87b5509fecc2b5
     imagePullPolicy: Always
   kong:
     enabled: true