-
Notifications
You must be signed in to change notification settings - Fork 709
Description
Description:
What issue is being seen? Describe what should be happening instead of
It's error withkubectl port-forward pod/$OTEL_POD_NAME -n monitoring 19001:19001
Repro steps:
Include sample requests, environment, etc. All data and inputs
required to reproduce the bug.
No special data.
Note: If there are privacy concerns, sanitize the data prior to
sharing.
Environment:
Include the environment like gateway version, envoy version and so on.
add-ons version 1.6.1
envoy-gateway version 1.5.0
Logs:
Include the access logs and the Envoy logs.
error msg like:
# kubectl port-forward pod/$OTEL_POD_NAME -n monitoring 19001:19001
Forwarding from 127.0.0.1:19001 -> 19001
Forwarding from [::1]:19001 -> 19001
Handling connection for 19001
E0104 15:19:50.696897 27284 portforward.go:409] an error occurred forwarding 19001 -> 19001: error forwarding port 19001 to pod 7e10850c41d629557874aa822d0f6d16d2801c8450bc5d1cb4b6c8e52b632751, uid : failed to execute portforward in network namespace "/var/run/netns/cni-8832de09-48d0-4338-c29b-0cc013c2c67f": failed to connect to localhost:19001 inside namespace "7e10850c41d629557874aa822d0f6d16d2801c8450bc5d1cb4b6c8e52b632751", IPv4: dial tcp4 127.0.0.1:19001: connect: connection refused IPv6 dial tcp6 [::1]:19001: connect: connection refused
error: lost connection to pod