The OpenFeature Operator allows you to expose feature flags to your applications. It injects a flagd sidecar into relevant pods and exposes gRPC and HTTP interfaces for flag evaluation. To get started, follow the installation instructions in the docs.
Note
With version v0.5.0, we have migrated
to API version v1beta1. Please check the migration guide to migrate from old configurations.
Important
OFO installs cluster-wide and resolves FeatureFlagSource / InProcessConfiguration resources across namespaces (see annotation syntax). On clusters that treat namespaces as trust boundaries between tenants, one tenant can cause OFO to read these resources from another tenant's namespace. See GHSA-398h-7f66-3h4p for the threat model, mitigations, and roadmap.
A future release will introduce explicit cluster-scoped ClusterFeatureFlagSource / ClusterInProcessConfiguration and remove implicit cross-namespace resolution. Per-tenant operator install is tracked in #795.
- Try the OpenFeature Operator locally on your machine
- Try the OpenFeature Operator in the Killercoda Playground (in browser)
See CHANGELOG.md
See CONTRIBUTING.md for details on how to contribute to the OpenFeature project.
Our community meetings are held regularly and open to everyone, as well as other community channels. Check the [OpenFeature community page]https://openfeature.dev/community/) for the links and participation guidelines.
Thanks so much to our contributors.
Made with contrib.rocks.