diff --git a/linkerd.io/content/2-edge/tasks/flagger.md b/linkerd.io/content/2-edge/tasks/flagger.md
index bb415e26d4..09a317275b 100644
--- a/linkerd.io/content/2-edge/tasks/flagger.md
+++ b/linkerd.io/content/2-edge/tasks/flagger.md
@@ -235,7 +235,7 @@ image to a new version by running:
 
 ```bash
 kubectl -n test set image deployment/podinfo \
-  podinfod=quay.io/stefanprodan/podinfo:1.7.1
+  podinfod=quay.io/stefanprodan/podinfo:3.3.1
 ```
 
 Any kind of modification to the pod's spec such as updating an environment
@@ -261,7 +261,7 @@ After the update is complete, this picture will go back to looking just like the
 figure from the previous section.
 
 {{< note >}}
-You can toggle the image tag between `1.7.1` and `1.7.0` to start the rollout
+You can toggle the image tag between `3.3.1` and `3.3.0` to start the rollout
 again.
 {{< /note >}}
 
@@ -308,16 +308,17 @@ that looks something like:
 ```bash
 {
   "hostname": "podinfo-primary-74459c7db8-lbtxf",
-  "version": "1.7.0",
+  "version": "3.3.0",
   "revision": "4fc593f42c7cd2e7319c83f6bfd3743c05523883",
-  "color": "blue",
-  "message": "greetings from podinfo v1.7.0",
+  "color": "#34577c",
+  "logo": "https://raw.githubusercontent.com/stefanprodan/podinfo/gh-pages/cuddle_clap.gif",
+  "message": "greetings from podinfo v3.3.0",
   "goos": "linux",
   "goarch": "amd64",
-  "runtime": "go1.11.2",
-  "num_goroutine": "6",
-  "num_cpu": "8"
-}
+  "runtime": "go1.14.2",
+  "num_goroutine": "8",
+  "num_cpu": "14"
+}   
 ```
 
 This response will slowly change as the rollout continues.
@@ -361,7 +362,7 @@ metadata:
 data:
   trafficRouterPlugins: |-
     - name: "argoproj-labs/gatewayAPI"
-      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.0.0-rc1/gateway-api-plugin-linux-amd64"
+      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.2.0/gateway-api-plugin-linux-amd64"
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
@@ -499,7 +500,7 @@ spec:
     spec:
       containers:
         - name: podinfod
-          image: quay.io/stefanprodan/podinfo:1.7.0
+          image: quay.io/stefanprodan/podinfo:3.3.0
           ports:
             - containerPort: 9898
               protocol: TCP
@@ -512,7 +513,7 @@ We can trigger a rollout to a new version of podinfo by running:
 
 ```bash
 kubectl argo rollouts -n test set image rollouts-demo \
-  podinfod=quay.io/stefanprodan/podinfo:1.7.1
+  podinfod=quay.io/stefanprodan/podinfo:3.3.1
 ```
 
 We can watch the rollout progress by running:
@@ -526,7 +527,7 @@ canary backends by updating the HTTPRoute resource. To watch how this
 configuration changes over the rollout, run:
 
 ```bash
-kubectl -n test get httproute.gateway.networking.k8s.io podinfo -o yaml
+kubectl -n test get httproute.gateway.networking.k8s.io argo-rollouts-http-route -o yaml
 ```
 
 We can also use the Linkerd CLI to observe which pods the traffic is being
diff --git a/linkerd.io/content/2.14/tasks/flagger.md b/linkerd.io/content/2.14/tasks/flagger.md
index e638e20a14..68a1ec3731 100644
--- a/linkerd.io/content/2.14/tasks/flagger.md
+++ b/linkerd.io/content/2.14/tasks/flagger.md
@@ -276,7 +276,7 @@ image to a new version by running:
 
 ```bash
 kubectl -n test set image deployment/podinfo \
-  podinfod=quay.io/stefanprodan/podinfo:1.7.1
+  podinfod=quay.io/stefanprodan/podinfo:3.3.1
 ```
 
 Any kind of modification to the pod's spec such as updating an environment
@@ -302,7 +302,7 @@ After the update is complete, this picture will go back to looking just like the
 figure from the previous section.
 
 {{< note >}}
-You can toggle the image tag between `1.7.1` and `1.7.0` to start the rollout
+You can toggle the image tag between `3.3.1` and `3.3.0` to start the rollout
 again.
 {{< /note >}}
 
@@ -349,16 +349,17 @@ that looks something like:
 ```bash
 {
   "hostname": "podinfo-primary-74459c7db8-lbtxf",
-  "version": "1.7.0",
+  "version": "3.3.0",
   "revision": "4fc593f42c7cd2e7319c83f6bfd3743c05523883",
-  "color": "blue",
-  "message": "greetings from podinfo v1.7.0",
+  "color": "#34577c",
+  "logo": "https://raw.githubusercontent.com/stefanprodan/podinfo/gh-pages/cuddle_clap.gif",
+  "message": "greetings from podinfo v3.3.0",
   "goos": "linux",
   "goarch": "amd64",
-  "runtime": "go1.11.2",
-  "num_goroutine": "6",
-  "num_cpu": "8"
-}
+  "runtime": "go1.14.2",
+  "num_goroutine": "8",
+  "num_cpu": "14"
+}   
 ```
 
 This response will slowly change as the rollout continues.
@@ -402,7 +403,7 @@ metadata:
 data:
   trafficRouterPlugins: |-
     - name: "argoproj-labs/gatewayAPI"
-      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.0.0-rc1/gateway-api-plugin-linux-amd64"
+      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.2.0/gateway-api-plugin-linux-amd64"
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
@@ -540,7 +541,7 @@ spec:
     spec:
       containers:
         - name: podinfod
-          image: quay.io/stefanprodan/podinfo:1.7.0
+          image: quay.io/stefanprodan/podinfo:3.3.0
           ports:
             - containerPort: 9898
               protocol: TCP
@@ -553,7 +554,7 @@ We can trigger a rollout to a new version of podinfo by running:
 
 ```bash
 kubectl argo rollouts -n test set image rollouts-demo \
-  podinfod=quay.io/stefanprodan/podinfo:1.7.1
+  podinfod=quay.io/stefanprodan/podinfo:3.3.1
 ```
 
 We can watch the rollout progress by running:
@@ -567,7 +568,7 @@ canary backends by updating the HTTPRoute resource. To watch how this
 configuration changes over the rollout, run:
 
 ```bash
-kubectl -n test get httproute.gateway.networking.k8s.io podinfo -o yaml
+kubectl -n test get httproute.gateway.networking.k8s.io argo-rollouts-http-route -o yaml
 ```
 
 We can also use the Linkerd CLI to observe which pods the traffic is being
diff --git a/linkerd.io/content/2.15/tasks/flagger.md b/linkerd.io/content/2.15/tasks/flagger.md
index bb415e26d4..09a317275b 100644
--- a/linkerd.io/content/2.15/tasks/flagger.md
+++ b/linkerd.io/content/2.15/tasks/flagger.md
@@ -235,7 +235,7 @@ image to a new version by running:
 
 ```bash
 kubectl -n test set image deployment/podinfo \
-  podinfod=quay.io/stefanprodan/podinfo:1.7.1
+  podinfod=quay.io/stefanprodan/podinfo:3.3.1
 ```
 
 Any kind of modification to the pod's spec such as updating an environment
@@ -261,7 +261,7 @@ After the update is complete, this picture will go back to looking just like the
 figure from the previous section.
 
 {{< note >}}
-You can toggle the image tag between `1.7.1` and `1.7.0` to start the rollout
+You can toggle the image tag between `3.3.1` and `3.3.0` to start the rollout
 again.
 {{< /note >}}
 
@@ -308,16 +308,17 @@ that looks something like:
 ```bash
 {
   "hostname": "podinfo-primary-74459c7db8-lbtxf",
-  "version": "1.7.0",
+  "version": "3.3.0",
   "revision": "4fc593f42c7cd2e7319c83f6bfd3743c05523883",
-  "color": "blue",
-  "message": "greetings from podinfo v1.7.0",
+  "color": "#34577c",
+  "logo": "https://raw.githubusercontent.com/stefanprodan/podinfo/gh-pages/cuddle_clap.gif",
+  "message": "greetings from podinfo v3.3.0",
   "goos": "linux",
   "goarch": "amd64",
-  "runtime": "go1.11.2",
-  "num_goroutine": "6",
-  "num_cpu": "8"
-}
+  "runtime": "go1.14.2",
+  "num_goroutine": "8",
+  "num_cpu": "14"
+}   
 ```
 
 This response will slowly change as the rollout continues.
@@ -361,7 +362,7 @@ metadata:
 data:
   trafficRouterPlugins: |-
     - name: "argoproj-labs/gatewayAPI"
-      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.0.0-rc1/gateway-api-plugin-linux-amd64"
+      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.2.0/gateway-api-plugin-linux-amd64"
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
@@ -499,7 +500,7 @@ spec:
     spec:
       containers:
         - name: podinfod
-          image: quay.io/stefanprodan/podinfo:1.7.0
+          image: quay.io/stefanprodan/podinfo:3.3.0
           ports:
             - containerPort: 9898
               protocol: TCP
@@ -512,7 +513,7 @@ We can trigger a rollout to a new version of podinfo by running:
 
 ```bash
 kubectl argo rollouts -n test set image rollouts-demo \
-  podinfod=quay.io/stefanprodan/podinfo:1.7.1
+  podinfod=quay.io/stefanprodan/podinfo:3.3.1
 ```
 
 We can watch the rollout progress by running:
@@ -526,7 +527,7 @@ canary backends by updating the HTTPRoute resource. To watch how this
 configuration changes over the rollout, run:
 
 ```bash
-kubectl -n test get httproute.gateway.networking.k8s.io podinfo -o yaml
+kubectl -n test get httproute.gateway.networking.k8s.io argo-rollouts-http-route -o yaml
 ```
 
 We can also use the Linkerd CLI to observe which pods the traffic is being
diff --git a/linkerd.io/content/2.16/tasks/flagger.md b/linkerd.io/content/2.16/tasks/flagger.md
index bb415e26d4..8315995f45 100644
--- a/linkerd.io/content/2.16/tasks/flagger.md
+++ b/linkerd.io/content/2.16/tasks/flagger.md
@@ -235,7 +235,7 @@ image to a new version by running:
 
 ```bash
 kubectl -n test set image deployment/podinfo \
-  podinfod=quay.io/stefanprodan/podinfo:1.7.1
+  podinfod=quay.io/stefanprodan/podinfo:3.3.1
 ```
 
 Any kind of modification to the pod's spec such as updating an environment
@@ -261,7 +261,7 @@ After the update is complete, this picture will go back to looking just like the
 figure from the previous section.
 
 {{< note >}}
-You can toggle the image tag between `1.7.1` and `1.7.0` to start the rollout
+You can toggle the image tag between `3.3.1` and `3.3.0` to start the rollout
 again.
 {{< /note >}}
 
@@ -308,16 +308,17 @@ that looks something like:
 ```bash
 {
   "hostname": "podinfo-primary-74459c7db8-lbtxf",
-  "version": "1.7.0",
+  "version": "3.3.0",
   "revision": "4fc593f42c7cd2e7319c83f6bfd3743c05523883",
-  "color": "blue",
-  "message": "greetings from podinfo v1.7.0",
+  "color": "#34577c",
+  "logo": "https://raw.githubusercontent.com/stefanprodan/podinfo/gh-pages/cuddle_clap.gif",
+  "message": "greetings from podinfo v3.3.0",
   "goos": "linux",
   "goarch": "amd64",
-  "runtime": "go1.11.2",
-  "num_goroutine": "6",
-  "num_cpu": "8"
-}
+  "runtime": "go1.14.2",
+  "num_goroutine": "8",
+  "num_cpu": "14"
+}   
 ```
 
 This response will slowly change as the rollout continues.
@@ -361,7 +362,7 @@ metadata:
 data:
   trafficRouterPlugins: |-
     - name: "argoproj-labs/gatewayAPI"
-      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.0.0-rc1/gateway-api-plugin-linux-amd64"
+      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.2.0/gateway-api-plugin-linux-amd64"
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
@@ -512,7 +513,7 @@ We can trigger a rollout to a new version of podinfo by running:
 
 ```bash
 kubectl argo rollouts -n test set image rollouts-demo \
-  podinfod=quay.io/stefanprodan/podinfo:1.7.1
+  podinfod=quay.io/stefanprodan/podinfo:3.3.1
 ```
 
 We can watch the rollout progress by running:
@@ -526,7 +527,7 @@ canary backends by updating the HTTPRoute resource. To watch how this
 configuration changes over the rollout, run:
 
 ```bash
-kubectl -n test get httproute.gateway.networking.k8s.io podinfo -o yaml
+kubectl -n test get httproute.gateway.networking.k8s.io argo-rollouts-http-route -o yaml
 ```
 
 We can also use the Linkerd CLI to observe which pods the traffic is being
diff --git a/linkerd.io/content/2.17/tasks/flagger.md b/linkerd.io/content/2.17/tasks/flagger.md
index bb415e26d4..ccfdcb1871 100644
--- a/linkerd.io/content/2.17/tasks/flagger.md
+++ b/linkerd.io/content/2.17/tasks/flagger.md
@@ -235,7 +235,7 @@ image to a new version by running:
 
 ```bash
 kubectl -n test set image deployment/podinfo \
-  podinfod=quay.io/stefanprodan/podinfo:1.7.1
+  podinfod=quay.io/stefanprodan/podinfo:3.3.1
 ```
 
 Any kind of modification to the pod's spec such as updating an environment
@@ -261,7 +261,7 @@ After the update is complete, this picture will go back to looking just like the
 figure from the previous section.
 
 {{< note >}}
-You can toggle the image tag between `1.7.1` and `1.7.0` to start the rollout
+You can toggle the image tag between `3.3.1` and `3.3.0` to start the rollout
 again.
 {{< /note >}}
 
@@ -308,10 +308,10 @@ that looks something like:
 ```bash
 {
   "hostname": "podinfo-primary-74459c7db8-lbtxf",
-  "version": "1.7.0",
+  "version": "3.3.0",
   "revision": "4fc593f42c7cd2e7319c83f6bfd3743c05523883",
   "color": "blue",
-  "message": "greetings from podinfo v1.7.0",
+  "message": "greetings from podinfo v3.3.0",
   "goos": "linux",
   "goarch": "amd64",
   "runtime": "go1.11.2",
@@ -361,7 +361,7 @@ metadata:
 data:
   trafficRouterPlugins: |-
     - name: "argoproj-labs/gatewayAPI"
-      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.0.0-rc1/gateway-api-plugin-linux-amd64"
+      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.2.0/gateway-api-plugin-linux-amd64"
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
@@ -499,7 +499,7 @@ spec:
     spec:
       containers:
         - name: podinfod
-          image: quay.io/stefanprodan/podinfo:1.7.0
+          image: quay.io/stefanprodan/podinfo:3.3.0
           ports:
             - containerPort: 9898
               protocol: TCP
@@ -512,7 +512,7 @@ We can trigger a rollout to a new version of podinfo by running:
 
 ```bash
 kubectl argo rollouts -n test set image rollouts-demo \
-  podinfod=quay.io/stefanprodan/podinfo:1.7.1
+  podinfod=quay.io/stefanprodan/podinfo:3.3.1
 ```
 
 We can watch the rollout progress by running:
@@ -526,7 +526,7 @@ canary backends by updating the HTTPRoute resource. To watch how this
 configuration changes over the rollout, run:
 
 ```bash
-kubectl -n test get httproute.gateway.networking.k8s.io podinfo -o yaml
+kubectl -n test get httproute.gateway.networking.k8s.io argo-rollouts-http-route -o yaml
 ```
 
 We can also use the Linkerd CLI to observe which pods the traffic is being
diff --git a/linkerd.io/content/2.18/tasks/flagger.md b/linkerd.io/content/2.18/tasks/flagger.md
index bb415e26d4..09a317275b 100644
--- a/linkerd.io/content/2.18/tasks/flagger.md
+++ b/linkerd.io/content/2.18/tasks/flagger.md
@@ -235,7 +235,7 @@ image to a new version by running:
 
 ```bash
 kubectl -n test set image deployment/podinfo \
-  podinfod=quay.io/stefanprodan/podinfo:1.7.1
+  podinfod=quay.io/stefanprodan/podinfo:3.3.1
 ```
 
 Any kind of modification to the pod's spec such as updating an environment
@@ -261,7 +261,7 @@ After the update is complete, this picture will go back to looking just like the
 figure from the previous section.
 
 {{< note >}}
-You can toggle the image tag between `1.7.1` and `1.7.0` to start the rollout
+You can toggle the image tag between `3.3.1` and `3.3.0` to start the rollout
 again.
 {{< /note >}}
 
@@ -308,16 +308,17 @@ that looks something like:
 ```bash
 {
   "hostname": "podinfo-primary-74459c7db8-lbtxf",
-  "version": "1.7.0",
+  "version": "3.3.0",
   "revision": "4fc593f42c7cd2e7319c83f6bfd3743c05523883",
-  "color": "blue",
-  "message": "greetings from podinfo v1.7.0",
+  "color": "#34577c",
+  "logo": "https://raw.githubusercontent.com/stefanprodan/podinfo/gh-pages/cuddle_clap.gif",
+  "message": "greetings from podinfo v3.3.0",
   "goos": "linux",
   "goarch": "amd64",
-  "runtime": "go1.11.2",
-  "num_goroutine": "6",
-  "num_cpu": "8"
-}
+  "runtime": "go1.14.2",
+  "num_goroutine": "8",
+  "num_cpu": "14"
+}   
 ```
 
 This response will slowly change as the rollout continues.
@@ -361,7 +362,7 @@ metadata:
 data:
   trafficRouterPlugins: |-
     - name: "argoproj-labs/gatewayAPI"
-      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.0.0-rc1/gateway-api-plugin-linux-amd64"
+      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.2.0/gateway-api-plugin-linux-amd64"
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
@@ -499,7 +500,7 @@ spec:
     spec:
       containers:
         - name: podinfod
-          image: quay.io/stefanprodan/podinfo:1.7.0
+          image: quay.io/stefanprodan/podinfo:3.3.0
           ports:
             - containerPort: 9898
               protocol: TCP
@@ -512,7 +513,7 @@ We can trigger a rollout to a new version of podinfo by running:
 
 ```bash
 kubectl argo rollouts -n test set image rollouts-demo \
-  podinfod=quay.io/stefanprodan/podinfo:1.7.1
+  podinfod=quay.io/stefanprodan/podinfo:3.3.1
 ```
 
 We can watch the rollout progress by running:
@@ -526,7 +527,7 @@ canary backends by updating the HTTPRoute resource. To watch how this
 configuration changes over the rollout, run:
 
 ```bash
-kubectl -n test get httproute.gateway.networking.k8s.io podinfo -o yaml
+kubectl -n test get httproute.gateway.networking.k8s.io argo-rollouts-http-route -o yaml
 ```
 
 We can also use the Linkerd CLI to observe which pods the traffic is being
diff --git a/run.linkerd.io/public/flagger.yml b/run.linkerd.io/public/flagger.yml
index 6ed90664ed..00e9f81c07 100644
--- a/run.linkerd.io/public/flagger.yml
+++ b/run.linkerd.io/public/flagger.yml
@@ -109,7 +109,7 @@ spec:
     spec:
       containers:
       - name: podinfod
-        image: quay.io/stefanprodan/podinfo:1.7.0
+        image: quay.io/stefanprodan/podinfo:3.3.0
         imagePullPolicy: IfNotPresent
         ports:
         - containerPort: 9898