Skip to content

Commit bc3e734

Browse files
Bump Gateway API version in migration guide (#2075)
1 parent 5836759 commit bc3e734

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

linkerd.io/content/2-edge/tasks/gateway-api-ownership-migration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ externally provided CRDs _before_ upgrading to Linkerd 2.18:
4242

4343
```bash
4444
kubectl apply -f \
45-
https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.1/standard-install.yaml
45+
https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.0/standard-install.yaml
4646
```
4747

4848
Next, run the usual upgrade command:
@@ -82,7 +82,7 @@ Next, overwrite Linkerd’s CRDs with the externally managed ones:
8282

8383
```bash
8484
kubectl apply -f \
85-
https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.1/standard-install.yaml
85+
https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.0/standard-install.yaml
8686
```
8787

8888
For all subsequent configuration updates or chart upgrades, use

linkerd.io/content/2.19/tasks/gateway-api-ownership-migration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ externally provided CRDs _before_ upgrading to Linkerd 2.18:
4242

4343
```bash
4444
kubectl apply -f \
45-
https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.1/standard-install.yaml
45+
https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.0/standard-install.yaml
4646
```
4747

4848
Next, run the usual upgrade command:
@@ -82,7 +82,7 @@ Next, overwrite Linkerd’s CRDs with the externally managed ones:
8282

8383
```bash
8484
kubectl apply -f \
85-
https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.1/standard-install.yaml
85+
https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.0/standard-install.yaml
8686
```
8787

8888
For all subsequent configuration updates or chart upgrades, use

0 commit comments

Comments
 (0)