Updating the Agent

To upgrade the Scalyr Kubernetes Agent from version 2.1.1 or newer run:

kubectl apply -f https://raw.githubusercontent.com/scalyr/scalyr-agent-2/release/k8s/no-kustomize/scalyr-service-account.yaml

kubectl apply -f https://raw.githubusercontent.com/scalyr/scalyr-agent-2/release/k8s/no-kustomize/scalyr-agent-2.yaml

This will perform a rolling upgrade of all Agent pods.

If you see errors containing `namespaces "scalyr" not found` when you upgrade, it is likely that you installed the Scalyr Agent using the instructions before the 2.1.1 Scalyr Agent release. See below for how to resolve this.

Upgrading Scalyr Agents Runnng in Default Namespace (Pre-2.1.1) 

If you are upgrading from an earlier version it is probably installed in the default namespace, if you wish to switch to the `scalyr` namespace first move your existing secret and configmap to the new namespace.

kubectl get secret scalyr-api-key --namespace=default --export -o yaml | kubectl apply -f - --namespace=scalyr

kubectl get configmap scalyr-config --namespace=default --export -o yaml | kubectl apply -f - --namespace=scalyr

Delete your old deployment to avoid running two Agents at once.

kubectl delete -f https://raw.githubusercontent.com/scalyr/scalyr-agent-2/release/k8s/default-namespace/scalyr-agent-2.yaml

Create the new DaemonSet in the new namespace.

kubectl apply -f https://raw.githubusercontent.com/scalyr/scalyr-agent-2/release/k8s/no-kustomize/scalyr-service-account.yaml

kubectl apply -f https://raw.githubusercontent.com/scalyr/scalyr-agent-2/release/k8s/no-kustomize/scalyr-agent-2.yaml

Staying in the default namespace

If you want to keep your installation in the default namespace you can upgrade your agent by running the following:

kubectl apply -f https://raw.githubusercontent.com/scalyr/scalyr-agent-2/release/k8s/default-namespace/scalyr-service-account.yaml

kubectl apply -f https://raw.githubusercontent.com/scalyr/scalyr-agent-2/release/k8s/default-namespace/scalyr-agent-2.yaml