Re: [PR] feat: add separate chart for CRDs [apisix-helm-chart]

["finnegan-haack-lhind (via GitHub)" <gi...@apache.org>]

finnegan-haack-lhind commented on PR #919:
URL: https://github.com/apache/apisix-helm-chart/pull/919#issuecomment-5280490880

   Any chance this PR might get merged? Without this change, deploying the ingress controller on any GKE cluster using the GatewayAPI is not possible, as experimental CRDs are not allowed. Trying to install the ingress controller helm chart leads to:
   
   ```
   customresourcedefinitions.apiextensions.k8s.io "grpcroutes.gateway.networking.k8s.io" is forbidden: ValidatingAdmissionPolicy 'enforce-gateway-standard-channel' with binding 'enforce-gateway-standard-channel-binding' denied request: All Gateway API CRDs must belong to the 'standard' channel. Experimental CRDs are not permitted.
   ```
   
   Skipping the CRDs for the helm chart, using the GKE provided GatewayAPI CRDs and deploying the APISIX ingress controller specific CRDs using
   
   ```
   kubectl apply --server-side -f https://raw.githubusercontent.com/apache/apisix-helm-chart/master/charts/apisix-ingress-controller/crds/apisixic-crds.yaml
   ```
   
   also does not work, as at least the GRPCRoute CRD is not supplied by GKE and causes a crash loop in the ingress controller.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org