Closed raviprakash007 closed 8 months ago
This is a GKE issue first reported here: https://github.com/envoyproxy/gateway/issues/2301
Some possible workarounds:
manager: l7mp/stunner-gateway-operator:0.16.0 , working.
Closing this then. Feel free to reopen is something related comes up. Meanwhile, fingers crossed for Google advancing the Gateway API version to v1 soon.
Would it make sense to link this github issue in addition to logging setup problem running operator {"error": "cannot register gateway controller: failed to get API group resources: unable to retrieve the complete list of server APIs: gateway.networking.k8s.io/v1: the server could not find the requested resource"}
?
Cool idea. The problem is surfaced by the K8s controller runtime here. We would need to carefully unwrap the error using some advanced errors.Is
magic and direct the user here if there's a match for this specific error. I'll try to implement this once I find some spare cycles.
I have a Google Cloud K8 cluster. Where I tried to install Stunner using Helm. The process I followed is as follows:
Output:
Now, in k8, I checked the services pods are up and working.
Services:
ConfigMap:
Workloads:
And if I check the workload logs, it says:
What is the problem and how can I expose the Stunner to external world?