gateway-api-app release v1.9.1
Changed
- Apply the CRDs from a dedicated installer image via a
pre-install/pre-upgrade hook Job instead of rendering them as Helm templates. The rendered release no longer contains the CRDs, which kept it from fitting in Helm’s release Secret. - CRDs are applied with server-side apply and are no longer Helm-managed, so
helm uninstall leaves them in place and a CRD rejected by the safe-upgrades policy now surfaces as a failed hook Job. - Reject unknown keys under
install, which previously were silently ignored.
Added
- E2E test suite covering CRD installation, installer hook cleanup, the
safe-upgrades admission policy and the served Gateway API resources. crds.image values to override the installer image. The tag defaults to the chart version.CiliumNetworkPolicy allowing the installer Job to reach the Kubernetes API server, without which the Job cannot apply the CRDs on clusters that default to denying egress. Set ciliumNetworkPolicy.enabled to false to skip it.