falco-operator
falco-operator copied to clipboard
Kubernetes operator for Falco that allows developers to manage rules for detecting intruders and backdoors
**Motivation** Current API Version is mumoshu.github.io/v1alpha1, but this doesn't represent the current state of the project well. **Feature** Change the API Group to something like falco.security.cncf.io or whatever would be...
In this moment, the operator is deployed using the `helm tiller` plugin. Not all people has helm or neither the tiller plugin installed. Is there another user experience deploying operators...
**Motivation** **Feature** Can we please rename this project to `falco-rules-operator` so that we can use this name for an officially supported install operator? **Alternatives** Keep this name the same for...
**What to document** Some information in the README.md should be fixed: - [ ] According to [new branding guideline](https://github.com/falcosecurity/falco/tree/master/brand) I believe "Sysdig" should not be used there - [ ]...
This adds the Openshift Optional category to the operator
Setup CI
In DockerHub, there is a falco-operator image which has the `0.12.1` tag. But in the Makefile and in the deployment manifests the tag value is `v0.12.1`. AFAIK, the convention followed...
Falco now accepts SIGHUP that triggers a restart. Use it so that falco-operator takes less time to restart falco, and therefore less chances to miss events. https://github.com/falcosecurity/falco/pull/457