Gateway API resources are installed directly from a mutable latest URL
Source references: 1When Gateway API CRDs are missing, the workflow tells `kubectl` to apply remote YAML from GitHub's `releases/latest` path. It pins neither a release, commit, nor content digest and does not require review of the downloaded document.
If upstream content changes or its distribution chain is compromised, an identity with sufficient cluster privileges would install unreviewed resources. CRDs are cluster-scoped configuration and can affect multiple namespaces and future resource handling.
This is an active deployment instruction: when the CRDs are missing, content from GitHub's mutable “latest” URL is passed directly to kubectl apply. No release version or digest is pinned, so the same workflow may install different cluster resources later. Users can require a reviewed, version-pinned release and digest, with download inspection and server-side dry-run before application.
### Verify Gateway API CRDs (only if Istio Gateway API detected)```bashkubectl get crd gateways.gateway.networking.k8s.io httproutes.gateway.networking.k8s.io 2>/dev/null```If missing: `kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/latest/download/standard-install.yaml`