You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While k logs -f eks-cloudwatch-dc8c4b6d9-vhkng -n sysdig-agent --follow=true I noticed
2020/07/09 19:14:27 Error while sending events to agent: Post http://sysdig-agent:7765/k8s_audit: dial tcp: lookup sysdig-agent on 172.20.0.10:53: no such host.
2020/07/09 19:14:27 Error while sending events to agent: Post http://sysdig-agent:7765/k8s_audit: dial tcp: lookup sysdig-agent on 172.20.0.10:53: no such host.
2020/07/09 19:14:27 Error while sending events to agent: Post http://sysdig-agent:7765/k8s_audit: dial tcp: lookup sysdig-agent on 172.20.0.10:53: no such host.
2020/07/09 19:14:27 80 logs sent to the agent (1138 total)
2020/07/09 19:14:27 11561 total logs
Attaching k exec -it sysdig-agent-c6jls /bin/sh -n sysdig-agent it appears the agent alias is not resolving
# nc -z -v sysdig-agent 7765
sysdig-agent: forward host lookup failed: No address associated with name
Audit events do not appear in the Secure UI.
The text was updated successfully, but these errors were encountered:
While
k logs -f eks-cloudwatch-dc8c4b6d9-vhkng -n sysdig-agent --follow=true
I noticedAttaching
k exec -it sysdig-agent-c6jls /bin/sh -n sysdig-agent
it appears the agent alias is not resolvingAudit events do not appear in the Secure UI.
The text was updated successfully, but these errors were encountered: