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.09k stars 438 forks source link

glooctl check doesn't work when gateway-proxy is deployed as daemonset #7606

Open radenkoletic opened 1 year ago

radenkoletic commented 1 year ago

Gloo Edge Version

1.14.x (beta)

Kubernetes Version

1.23.x

Describe the bug

I'm using helm to deploy the gloo edge version v1.14.0-beta3. gateway-proxy is deployed using daemonset. Everything works fine except the glooctl check. It reports Gloo installation is incomplete: no active gateway-proxy pods exist in cluster when checking for proxies. If I switch to deployment controller for gateway-proxy it will pass.

Steps to reproduce the bug

  1. install gloo edge version v1.14.0-beta3 using helm
  2. use daemonset to deploy gateway-proxy
  3. run glooctl check

Expected Behavior

glooctl check should pass

Additional Context

No response

github-actions[bot] commented 4 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.