Description
GKE version: 1.35.1-gke.1396002
apisix helm chart version: 2.12.6
apisix version: 3.15.0
In GKE version 1.35, a validatingadmissionpolicy resource called enforce-gateway-standard-channel was added. This prevents the deployment of gateway API-related resources with the gateway.networking.k8s.io/channel: experimental annotation. Unfortunately, this annotation is present in the gwapi-crds.yaml file within the Apisix charts, causing Helm deployment failures. This is because gateway API-related resources are deployed through GKE's own components. While Apisix's gateway API-related CRD resources don't need to be deployed, I couldn't find a corresponding switch in values.yaml. The only solution I can think of is deleting the gwapi-crds.yaml file. Are there any better workarounds?
Environment
GKE version: 1.35.1-gke.1396002
apisix helm chart version: 2.12.6
apisix version: 3.15.0
Description
GKE version: 1.35.1-gke.1396002
apisix helm chart version: 2.12.6
apisix version: 3.15.0
In GKE version 1.35, a
validatingadmissionpolicyresource calledenforce-gateway-standard-channelwas added. This prevents the deployment of gateway API-related resources with thegateway.networking.k8s.io/channel: experimentalannotation. Unfortunately, this annotation is present in thegwapi-crds.yamlfile within the Apisix charts, causing Helm deployment failures. This is because gateway API-related resources are deployed through GKE's own components. While Apisix's gateway API-related CRD resources don't need to be deployed, I couldn't find a corresponding switch invalues.yaml. The only solution I can think of is deleting thegwapi-crds.yamlfile. Are there any better workarounds?Environment
GKE version: 1.35.1-gke.1396002
apisix helm chart version: 2.12.6
apisix version: 3.15.0