We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I join one pod, but another I cannot. What could be the reason for this?
$ k debug selection-staging-798847b54b-g6nf9 container created, open tty... bash-5.1# hostname selection-staging-798847b54b-g6nf9 bash-5.1# exit exit $ k debug selection-db-staging-5974f5b9c9-8lqp7 error execute remote, error sending request: Post http://10.147.245.22:10027/api/v1/debug?command=%5B%22bash%22%5D&container=docker%3A%2F%2F84a34bba16510f36e4a3e044cd339eaa89af3c8f360b921fbcad60f548784fac&image=nicolaka%2Fnetshoot%3Alatest: dial tcp 10.147.245.22:10027: connect: connection refused error: error sending request: Post http://10.147.245.22:10027/api/v1/debug?command=%5B%22bash%22%5D&container=docker%3A%2F%2F84a34bba16510f36e4a3e044cd339eaa89af3c8f360b921fbcad60f548784fac&image=nicolaka%2Fnetshoot%3Alatest: dial tcp 10.147.245.22:10027: connect: connection refused
The text was updated successfully, but these errors were encountered:
Hi! Try to activate: hostNetwork: true
hostNetwork: true
And try to use this command, this helps to me.
kubectl-debug -n monitoring monitoring-prometheus-node-exporter-6f4ls --agentless=true --port-forward=true --agent-image=aylei/debug-agent:v0.1.1
If it works change in daemonset.yaml image: aylei/debug-agent:latest To image: aylei/debug-agent:v0.1.1
image: aylei/debug-agent:latest
image: aylei/debug-agent:v0.1.1
Also I have changed ports in daemonset.yaml from 10027 to 10028 (strange network problem: Predicate PodFitsHostPorts failed)
Predicate PodFitsHostPorts failed
Good luck!
Sorry, something went wrong.
No branches or pull requests
I join one pod, but another I cannot. What could be the reason for this?
The text was updated successfully, but these errors were encountered: