Open rwarford opened 7 months ago
I am experiencing the same issue.
More on this. Installed the experimental channel CRDs of the Gateway release 0.4.0 and issue resolved.
$kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.0.0/experimental-install.yaml
This installs the alpha CRDs for GPCRoute and TLSRoute. I think the plugin fails on the sync call if ALL referenced CRDs are not present (GPCRoute and TLSRoute are excluded in the standard channel).
More on this. Installed the experimental channel CRDs of the Gateway release 0.4.0 and issue resolved.
$kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.0.0/experimental-install.yaml
This installs the alpha CRDs for GPCRoute and TLSRoute. I think the plugin fails on the sync call if ALL referenced CRDs are not present (if is they are excluded in using resource type filter.
I think this must be the case. Seems like it should work with services and ingresses and just ignore routes if the CRDs aren't installed.
Maybe this can help anyone else coming looking for a solution. I only really needed the gateway to watch ingresses.networking.k8s.io. So I just restricted the ClusterRole with a Kustomize patch. This works around the issue at least for now.
Maybe this can help anyone else coming looking for a solution. I only really needed the gateway to watch ingresses.networking.k8s.io. So I just restricted the ClusterRole with a Kustomize patch. This works around the issue at least for now.
this is the right solution. the chart should add rbac dynamically, however, it's static: (rbac)[https://github.com/ori-edge/k8s_gateway/blob/master/charts/k8s-gateway/templates/rbac.yaml#L28-L33]
another issue is you can't deactivate it to create your own RBAC with this chart.
I installed via Helm chart 2.0.4 (app version 0.3.4) and DNS resolution works correctly. I uninstalled then installed Helm chart 2.1.0 (app version 0.4.0) and DNS resolution no longer works (dig reports SERVFAIL). I've tried Helm chart 2.4.0 and get the same results.
Logs from app version 0.4.0 (note the Could not sync required resources error):
Logs from app version 0.3.4 (which is working correctly):