-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
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
hubble: allow filtering by agent event subtypes #14305
hubble: allow filtering by agent event subtypes #14305
Conversation
When originally adding support for agent events in #14168, generic agent events were left out since there are non currently produced by the Cilium agent. However, this leads to a mismatch between the AgenteEventType_* values and the respective monitor API values. In order to allow filtering on agent event types these should match, so mark the value for generic agent events as reserved in enum AgenteEventType. Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Use the filter sub type to specify agent event type. Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
test-me-please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we still need to have an API discussion to know if #14242 (comment) also needs to be tackled.
retest-runtime hit #14125 https://jenkins.cilium.io/job/Cilium-PR-Runtime-4.9/2904/ |
retest-net-next hit #13261 https://jenkins.cilium.io/job/Cilium-PR-K8s-1.12-net-next/1543/ |
retest-4.19 |
retest-4.9 |
Follow-up for #14242
The first commit updates the protobuf enum values for the agent event types, so they match the respective monitor API values. This will make the implementation on the Hubble CLI side more straight-forward.
The second commit introduces functionality to filter agent events by event type (e.g. endpoint creation, policy update).