Rollout sequencing with custom stages is now generally available

## Feature Feature Rollout sequencing with custom stages is now generally available. This version of rollout sequencing, which is recommended if you're configuring an environment for the first time, offers a robust set of features including the following: * **Define custom stages**: Sequence the rollout of a new GKE version across environments. With custom stages, you can, for example, deploy a new version on a small subset of production clusters before a wider rollout. * **Choose the scope of rollouts**: Decide what types of versions that GKE rolls out in the sequence. For example, you can have GKE roll out patch versions, but not minor versions, across a sequence. * **Initiate a rollout**: Create a rollout of a specific version, if you want GKE to roll out that version across your sequence. * **Manage a rollout**: Pause, resume, cancel rollouts, or complete rollout stages as needed. For more information, see[About rollout sequencing with custom stages](https://cloud.google.com/kubernetes-engine/docs/concepts/rollout-sequencing-custom-stages/about-rollout-sequencing). ## Change Change GKE Dataplane V2 clusters running version 1.35.1-gke.1516000 or later now use CNI version 1.1.0 in the CNI configuration files. This change requires downstream CNI plugins to be compatible with CNI version 1.1.0. Customers using self-managed open-source Istio or in-cluster unmanaged Cloud Service Mesh (CSM) variant must manually upgrade their CSM CNI version to 1.23 to ensure compatibility. If you use an incompatible CNI version, nodes might fail to reach a `Ready` state and might show `NetworkPluginNotReady` errors.