search

solo-io / gloo

The Feature-rich, Kubernetes-native, Next-Generation API Gateway Built on Envoy
https://docs.solo.io/
Apache License 2.0
4.07k stars 437 forks source link

gloo-proxy not listensing on 8080 when using flannel or calico #5979

Open flyer103 opened 2 years ago

flyer103 commented 2 years ago

Gloo Edge Version

1.9.x

Kubernetes Version

1.19.x

Describe the bug

When deploying Gloo in K8s cluster using Flannel, we found that gloo-proxy Pod did not listen on port 8080. After the weave-net plug-in was tried, gloo-proxyPod listened on port 8080 normally.

A similar problem occurs when gloo is deployed in a K8s cluster using Calico, with gloo-proxy Pod not listening on port 8080.

Steps to reproduce the bug

In a K8s cluster using Flannel or Calico, deploy gloo and then go into gloo-porxy Pod to check for listening ports.

Expected Behavior

gloo-proxy Pod can listen on port 8080 as expected.

Additional Context

No response

github-actions[bot] commented 3 months ago

This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.