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'll use this issue to list the ideas of features, feel free to propose yours and I'll add them if I think they're relevant:
dry-run
kubernetes:delete
kubernetes:script
kubernetes:disableuser
kubernetes:log
kubernetes:checkpoint
kubernetes:tshark
kubernetes:tcpdump
kubernetes:cordon
kubernetes:drain
ansible:playbook
shell:command
shell:script
aws:lambda
aws:cli
aws:command
calico:networkpolicy
cilium:networkpolicy
gcp:cloudfunction
webhook
allow
*:networkpolicy
debug
debug=true
The text was updated successfully, but these errors were encountered:
Replace by an opened discussion #277
Sorry, something went wrong.
See #277
No branches or pull requests
I'll use this issue to list the ideas of features, feel free to propose yours and I'll add them if I think they're relevant:
dry-run
option in the rulekubernetes:delete
to delete resources other than Pods (secrets/configmaps/deployment/statefulset/replicaset/daemonset)kubernetes:script
to run a shell script in a podkubernetes:disableuser
disable a control plane userkubernetes:log
get last logs from a podkubernetes:checkpoint
create a checkpointkubernetes:tshark
,kubernetes:tcpdump
kubernetes:cordon
kubernetes:drain
ansible:playbook
run an ansible playbook locally/remotelyshell:command
run a shell command locallyshell:script
run a shell script locallyaws:lambda
run an AWS Lambda functionaws:cli
run an AWS CLI Command (maybeaws:command
is a better name?)calico:networkpolicy
cilium:networkpolicy
gcp:cloudfunction
webhook
allow
parameter of*:networkpolicy
debug
mode: only display the received event which match, except ifdebug=true
The text was updated successfully, but these errors were encountered: