# Falco Operator 0.2.0 reaches production-ready status > Falco Operator 0.2.0 adds Kubernetes-style reconciliation, status conditions, finalizers, and a Component resource for managing the wider stack. Canonical URL: https://www.devobs.io/news/news-falco-operator-production-ready-020/ By: Elias Brooks Published: 2026-09-06T11:58:54.649Z Updated: 2026-09-06T11:58:54.649Z Event date: 2026-03-23 Section: Security The Falco project released Falco Operator 0.2.0 on March 23 and described it as the operator’s first production-ready release. The [release post](https://falco.org/blog/falco-operator-0-2-0/) highlights Server-Side Apply, Kubernetes-style status conditions, deletion protection through finalizers, and a new `Component` custom resource. ## Reconciliation replaces installation scripts Falco spans more than a single daemon: deployments may include plugins, rules, Falcosidekick, metadata collection, and a user interface. Static manifests can install those pieces, but they do not continuously reconcile desired state or expose a consistent health model. The operator brings those concerns into Kubernetes controllers. The new status conditions—such as `Available`, `Reconciled`, and `ResolvedRefs`—are operationally valuable because existing Kubernetes tooling can watch them. A platform team can alert on failed reconciliation rather than discovering drift only when runtime detections disappear. Finalizers also protect referenced resources from deletion while they remain in use. ## Production-ready still requires a failure drill An operator adds another control plane. Before fleet rollout, teams should deploy it to a test cluster, deliberately break a referenced rule or plugin, and confirm that status conditions identify the cause. They should also delete and recreate managed objects to verify finalizer behavior and recovery. The most dangerous failure is a healthy controller managing an unhealthy detection pipeline. Controller uptime alone says little about whether Falco is receiving kernel events or whether alerts reach their destination. Readiness criteria should therefore combine operator conditions with a synthetic rule that fires on demand and is observed downstream. Version 0.2.0 makes the operator a credible lifecycle tool. Its value is strongest when teams monitor both reconciliation and the end-to-end security signal it is supposed to preserve. ## Source references -