glooctl proxy doesn't support envoy as daemonset

solo-io / gloo

The Feature-rich, Kubernetes-native, Next-Generation API Gateway Built on Envoy

https://docs.solo.io/

Apache License 2.0

4.03k stars 433 forks source link

glooctl proxy doesn't support envoy as daemonset #1250

Open EItanya opened 4 years ago

EItanya commented 4 years ago

Currently the glooctl proxy commands attempt to port-forward to the gateway-proxy pod by using the deployments/gateway-proxy-v2 syntax from kubectl. However, this does not support the daemonset use case recently added to the helm chart

https://github.com/solo-io/gloo/blob/c2e95f8a9f2ec5c559e8f2985bb575d1a742a2a9/projects/gloo/cli/pkg/cmd/gateway/dump.go#L41

george-oakling commented 4 years ago

still valid?

kevin-shelaga commented 2 years ago

Still valid. All glooctl commands fail when gloo edge is deployed as a daemonset. This makes debugging very difficult.

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