Update docs to clarify different service accounts
This commit is contained in:
parent
155ae8d50f
commit
44a2812f5a
|
|
@ -76,7 +76,7 @@ Watching a namespace for an operator means tracking requests to change Postgresq
|
||||||
|
|
||||||
By default, the operator watches the namespace it is deployed to. You can change this by altering the `WATCHED_NAMESPACE` env var in the operator deployment manifest or the `watched_namespace` field in the operator configmap. In the case both are set, the env var takes the precedence.
|
By default, the operator watches the namespace it is deployed to. You can change this by altering the `WATCHED_NAMESPACE` env var in the operator deployment manifest or the `watched_namespace` field in the operator configmap. In the case both are set, the env var takes the precedence.
|
||||||
|
|
||||||
Note that for an operator to create pods in the watched namespace, one needs to create the `operator` service account in the namespace.
|
Note that for an operator to manage pods in the watched namespace, the operator's service account (as specified in the operator deployment manifest) has to have appropriate privileges to access the watched namespace. The watched namespace also needs to have a (possibly different) service account that allows database pods to talk to the Kubernetes API.
|
||||||
|
|
||||||
### Create ConfigMap
|
### Create ConfigMap
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue