github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update website/content/docs/api-gateway/upgrade-specific-versions.mdx

Browse Source 
Co-authored-by: Karl Cardenas <kcardenas@hashicorp.com>
pull/12863/head
Nathan Coleman 3 years ago committed by GitHub
parent 45be1d370f
commit d2234fc6f7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File

4
website/content/docs/api-gateway/upgrade-specific-versions.mdx
Unescape View File

@ -222,8 +222,8 @@ Ensure that the following requirements are met prior to upgrading:
1. According to the Kubernetes Gateway API specification, [Gateway Class](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io%2fv1alpha2.GatewayClass) configurations should only be applied to a gateway upon creation. To see the effects on preexisting gateways after upgrading your CRD installation, delete and recreate any gateways by issuing the following commands: 1. According to the Kubernetes Gateway API specification, [Gateway Class](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io%2fv1alpha2.GatewayClass) configurations should only be applied to a gateway upon creation. To see the effects on preexisting gateways after upgrading your CRD installation, delete and recreate any gateways by issuing the following commands:
```shell-session ```shell-session
$ kubectl delete -f <path_to_gateway_config.yaml> $ kubectl delete --filename <path_to_gateway_config.yaml>
$ kubectl create -f <path_to_gateway_config.yaml> $ kubectl create --filename <path_to_gateway_config.yaml>
``` ```
<!--- <!---
remove this warning once updating a gateway triggers reconciliation on child routes remove this warning once updating a gateway triggers reconciliation on child routes

Write Preview
Loading…
Cancel
Save