Skip to content

Commit

Permalink
Update documentation/docs/FAQ.mdx
Browse files Browse the repository at this point in the history
CR fix

Co-authored-by: roekatz <roe@roekatz.com>
  • Loading branch information
orweis and roekatz committed May 9, 2023
1 parent 131a345 commit 6de4025
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion documentation/docs/FAQ.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,8 @@ Hence OPAL-clients are aware of changes very quickly, and can react to the chang

## Can I run the OPAL-server without `OPAL_BROADCAST_URI` ?

This is mainly useful for light-workloads (Where a single worker is enough) and development environments (where you just don't want the hassle of setting up a Kafka / Redis / Postgres service)
Yes. This is mainly useful for light-workloads (Where a single worker is enough) and development environments (where you just don't want the hassle of setting up a Kafka / Redis / Postgres service).
Since server replication requires broadcasting, make sure that `UVICORN_NUM_WORKERS=1` and pod scaling is set to 1 (when running on k8s)

## How does OPAL guarantee that the policy data is actually in sync with the actual application state. We get that OPAL server publishes updates to OPAL client but is there error correction in place.

Expand Down

0 comments on commit 6de4025

Please sign in to comment.