istio
31 строка · 1.7 Кб
1apiVersion: release-notes/v2
2kind: feature
3area: traffic-management
4releaseNotes:
5- |
6**Improved** [Gateway API Automated Deployment](https://istio.io/latest/docs/tasks/traffic-management/ingress/gateway-api/#automated-deployment) management logic.
7See Upgrade Notes for more information.
8
9upgradeNotes:
10- title: Gateway API Automated Deployment changes.
11content: |
12This change impacts you only if you use [Gateway API Automated Deployment](https://istio.io/latest/docs/tasks/traffic-management/ingress/gateway-api/#automated-deployment).
13Note that this only applies to the Kubernetes Gateway API, not the Istio `Gateway`.
14You can check if you are using this feature with the following command:
15
16{{< text bash >}}
17$ kubectl get gateways.gateway.networking.k8s.io -ojson | jq -r '.items[] | select(.spec.gatewayClassName == "istio") | select((.spec.addresses | length) == 0) | "Found managed gateway: " + .metadata.namespace + "/" + .metadata.name'
18Found managed gateway: default/gateway
19{{< /text >}}
20
21If you see "Found managed gateway", you may be impacted by this change.
22
23Prior to Istio 1.18, the managed gateway worked by creating a minimal Deployment configuration which
24was fully populated at runtime with Pod injection. To upgrade gateways, users would restart the Pods
25to trigger a re-injection.
26
27In Istio 1.18, this has changed to create a fully rendered Deployment and no longer rely on injection.
28As a result, *Gateways will be updated, via a rolling restart, when their revision changes*.
29
30Additionally, users using this feature must update their control plane to Istio 1.16.5+ or 1.17.3+ before adopting Istio 1.18.
31Failure to do so may lead to conflicting writes to the same resources.
32