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
The Networking Monitoring section of the Getting Started guide states that "no new events" will be generated when using curl to connect from the "xwing" Pod to a cluster-internal FQDN (like deathstar.svc.cluster.local) or its equivalent ClusterIP (like 10.100.100.1).
However, this isn't correct. No new connect events will be generated, but new process and exit events will be generated since execution monitoring is still active:
The Networking Monitoring section of the Getting Started guide states that "no new events" will be generated when using
curl
to connect from the "xwing" Pod to a cluster-internal FQDN (likedeathstar.svc.cluster.local
) or its equivalent ClusterIP (like10.100.100.1
).However, this isn't correct. No new
connect
events will be generated, but newprocess
andexit
events will be generated since execution monitoring is still active:We should either:
connect
events, but that execution monitoring events are still reported; or--event-types
, but I haven't personally tested this yet).The text was updated successfully, but these errors were encountered: