falcosecurity-retire / falco-operator

Kubernetes operator for Falco that allows developers to manage rules for detecting intruders and backdoors
Apache License 2.0
68 stars 9 forks source link

Deploy operator without `helm tiller` #4

Open nestorsalceda opened 5 years ago

nestorsalceda commented 5 years ago

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 like:

The point is that the less external dependencies we have, the better for get more people involved using and contributing to Falco, so I think that using just kubectl like etcd or prometheus would be awesome.

Thanks!

mumoshu commented 5 years ago

@nestorsalceda Good suggestion!

I'd render the helm chart to produce a set of manifests and include it in the repo.

flickerfly commented 4 years ago

An example using a Subscription to a catalog like OperatorHub.io provides at https://operatorhub.io/install/falco.yaml may be appropriate here.

poiana commented 3 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

poiana commented 3 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale