make envoy-eg pod able to debug

[zirain]

correct me if I'm wrong

Right now, there's no debug tool (curl etc) in envoyproxy/envoy, admin port is listen on 127.0.0.1, we need provider a way to access config_dump for debug?

cc @danehans @arkodg WDYT?

[arkodg]

hey @zirain what about port forwarding to the envoy pod ?

[zirain]

hey @zirain what about port forwarding to the envoy pod ?

that need open more than one shell, once the pod changed, you need port forward again.

I want just run one line script like following:

kubectl exec -it <pod_name> -nenvoy-gateway-system -- curl 127.0.0.1:19000/config_dump

[arkodg]

I understand your pain :). I think we might have to continue with above workflow until

• we have a debug subcommand such as envoy-gateway collect to collect config_dump and much more for offline triaging (we could target this for v0.2.0)
• or we support BYO Envoy Bootstrap config (scheduled for post v0.2.0)

[zirain]

Actually I have some workarounds now, just open a ticket to track this.

IMO, it's necessary, but not that urgent.

here's my proposal:

• change the base-images like this
• add a subcommand like istioctl pc all(what we do in istio project) if we have tools like egctl

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[zirain]

replaced by https://github.com/envoyproxy/gateway/issues/794