Updating AutoTrace webhook
Instana AutoTrace webhook cannot automatically update the instrumentation. Therefore, you must manually update it by uninstalling previous instrumentation and then reinstalling the webhook by using Helm deployment.
icr.io/instana/instrumentation image. Instana specifies a version tag in the values.yaml file to make sure that the instana-autotrace-webhook Helm chart is regularly updated to use the latest icr.io/instana/instrumentation image.To update Instana AutoTrace webhook and instrumentation, complete the following steps:
-
Remove the current webhook installation by running the following command:
helm uninstall --namespace instana-autotrace-webhook instana-autotrace-webhook -
Update the Helm chart repository on your local Helm installation by running the following command:
helm repo update -
Install the
instana-autotrace-webhookHelm chart deployment again by running the following command:helm install --create-namespace --namespace instana-autotrace-webhook instana-autotrace-webhook \ --repo https://agents.instana.io/helm instana-autotrace-webhook \ --set webhook.imagePullCredentials.password=<download_key> --set <initial-custom-flags> -
Restart the deployment to trigger the start-up of the new application pods that receive the new transformation and instrumentation.
-
Restart the higher-level resources by running the following command:
kubectl rollout restart deployment <deployment-name> -n <deployment-ns> -
Starting with webhook release 1.304.6, the upgrade process is simplified. The webhook now mutates pods directly instead of higher-level resources by default. You can restart deployments to apply upgrades.
If you use a webhook version earlier than 1.304.6, or if you manually enable --set autotrace.enableHigherLevelResourceMutation=true, the webhook mutates resources at the deployment level. In this case, a simple deployment restart is not sufficient. Redeploy the higher-level resources to make sure that transformations are applied.
1.304.6 or later to simplify your upgrade process and enable the restart-based approach.