Skip to content

Update argo rollout tutorial #2055

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 10 commits into
base: main
Choose a base branch
from
Open

Update argo rollout tutorial #2055

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
aa5aff3
add reference to the linkerd directive
GTRekter Aug 25, 2025
68cf524
Fix enterprise training link (#2026)
bezarsnba Aug 25, 2025
d6d86a9
fix(deps): bump actions/download-artifact from 4.3.0 to 5.0.0 (#2016)
dependabot[bot] Aug 25, 2025
4e3cc93
fix(deps): bump actions/checkout from 4 to 5 (#2022)
dependabot[bot] Aug 25, 2025
3d38452
docs(edge/multicluster): use edge Helm repo & chart on 2-edge page (#…
bezarsnba Aug 28, 2025
afe8920
Use edge Helm repo on docs 2.15 and newer (#2031)
travisbeckham Aug 29, 2025
9ca182e
Updated link to authzpolicy-grafana.yaml (#2033)
travisbeckham Sep 3, 2025
b48f28e
Updated to use the new podinfo images
GTRekter Oct 23, 2025
8a815be
update argo
GTRekter Oct 23, 2025
3924c6d
Merge branch 'main' into ivanp/update-argo-tutorial
GTRekter Oct 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 14 additions & 13 deletions linkerd.io/content/2-edge/tasks/flagger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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 >}}

Expand Down Expand Up @@ -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.
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand All @@ -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:
Expand All @@ -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
Expand Down
27 changes: 14 additions & 13 deletions linkerd.io/content/2.14/tasks/flagger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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 >}}

Expand Down Expand Up @@ -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.
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand All @@ -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:
Expand All @@ -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
Expand Down
27 changes: 14 additions & 13 deletions linkerd.io/content/2.15/tasks/flagger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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 >}}

Expand Down Expand Up @@ -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.
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand All @@ -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:
Expand All @@ -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
Expand Down
25 changes: 13 additions & 12 deletions linkerd.io/content/2.16/tasks/flagger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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 >}}

Expand Down Expand Up @@ -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.
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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:
Expand All @@ -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
Expand Down
16 changes: 8 additions & 8 deletions linkerd.io/content/2.17/tasks/flagger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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 >}}

Expand Down Expand Up @@ -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",
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand All @@ -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:
Expand All @@ -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
Expand Down
Loading