public_git/postgres-operator
1
0
Fork 0
mirror of https://github.com/zalando/postgres-operator.git synced 2026-10-09 05:35:52 +02:00
Code Issues Projects Releases Wiki Activity

Look for secrets in the deployed namespace

Browse Source
This commit is contained in:
Sergey Dudoladov
2018-02-14 15:37:30 +01:00
parent 5837015b3c
commit d5d15b7546
4 changed files with 50 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+17
View File
@@ -61,6 +61,23 @@ to test your that your setup is working.
Note: if you use multiple Kubernetes clusters, you can switch to Minikube with `kubectl config use-context minikube`
### Select the namespace to deploy to
The operator can run in a namespace other than `default`. For example, to deploy it to the `test` namespace, run the following:
kubectl create namespace test
kubectl config set-context minikube --namespace=test
All subsequent `kubectl` commands will work with the `test` namespace. The operator will run in this namespace and look up needed resources - such as its config map - there.
### Specify the namespace to watch
Watching a namespace for an operator means tracking requests to change Postgresql clusters in the namespace such as "increase the number of Postgresql replicas to 5" and reacting to the requests, in this example by actually scaling up.
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 preference.
Note that for an operator to create pods in the watched namespace, one needs to create the `operator` service account in the namespace.
### Create ConfigMap
ConfigMap is used to store the configuration of the operator