koderover
[installation] The gateway cannot start listening properly.
Describe the bug In an Alibaba Cloud ACK cluster running Kubernetes version 1.30.1, when deploying Zadig 3.0 using Helm, I found that the Gloo gateway's gateway component fails to start listening properly, causing the gateway-proxy to be unable to access the system.
Pod Status List
Log of abnormal Pod
gateway
gateway-proxy
{"level":"error","ts":"2024-08-01T02:06:25.854Z","logger":"gateway.v1.event_loop.gateway.validation-resync-notifications","caller":"validation/notification_channel.go:40","msg":"error reading from stream. attempting to establish new stream.","version":"1.9.1","error":"rpc error: code = Unavailable desc = transport is closing","stacktrace":"github.com/solo-io/gloo/projects/gateway/pkg/validation.MakeNotificationChannel.func1\n\t/workspace/gloo/projects/gateway/pkg/validation/notification_channel.go:40"}
Version used
- Zadig: 3.0
- Kubernetes: 1.30.1
Installation Environment
- Cluster：AliCloud（ACK）1.30.1
- Nodes：4 Cores / 16 GB RAM
- Operating System：Alibaba Cloud Linux 3.2104
Hi, could you please confirm the cluster name, and also check whether the namespace is correctly set in the Helm installation values?
Since there has been no response from the user for an extended period, we will proceed to close this issue. If you have any further questions or need assistance, feel free to reopen or create a new issue.
