istio.io/istio@v0.0.0-20240520182934-d79c90f27776/releasenotes/notes/gateway-api118.yaml (about)

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