You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/configuration.md
+23Lines changed: 23 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,7 @@ Supported flags are as follows (result of running `./flagd start --help`):
13
13
-c, --server-cert-path string Server side tls certificate path
14
14
-k, --server-key-path string Server side tls key path
15
15
-s, --service-provider string Set a service provider e.g. http or grpc (default "http")
16
+
-a, --sync-provider-args Sync provider arguments as key values separated by =
16
17
-d, --socket-path string Set the flagd socket path. With grpc the service will become available on this address. With http(s) the grpc-gateway proxy will use this address internally
17
18
-y, --sync-provider string Set a sync provider e.g. filepath or remote (default "filepath")
18
19
-f, --uri strings Set a sync provider uri to read data from this can be a filepath or url. Using multiple providers is supported where collisions between flags with the same key, the later will be used.
@@ -22,3 +23,25 @@ Environment variable keys are uppercased, prefixed with `FLAGD_` and all `-` are
22
23
`sync-provider` in environment variable form is `FLAGD_SYNC_PROVIDER`.
23
24
24
25
Config file expects the keys to have the exact naming as the flags.
26
+
27
+
28
+
### Customising sync providers
29
+
30
+
Custom sync providers can be used to provide flag evaluation logic.
31
+
32
+
#### Kubernetes provider
33
+
34
+
The Kubernetes provider allows flagD to connect to a Kubernetes cluster and evaluate flags against a specified FeatureFlagConfiguration resource as defined within the [open-feature-operator](https://github.com/open-feature/open-feature-operator/blob/main/apis/core/v1alpha1/featureflagconfiguration_types.go) spec.
35
+
36
+
To use an existing FeatureFlagConfiguration custom resource, start flagD with the following command:
An additional optional flag `refreshtime` can be applied to shorten the cache refresh when using the Kubernetes provider ( The default is 5s ). As an example:
0 commit comments