public_git/postgres-operator
1
0
Fork 0
mirror of https://github.com/zalando/postgres-operator.git synced 2026-10-18 04:06:17 +02:00
Code Issues Projects Releases Wiki Activity

Remove further mentions of service account

Browse Source
This commit is contained in:
Sergey Dudoladov
2018-05-17 15:51:29 +02:00
parent cbbbd69157
commit 8b4dc02b2b
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -3
View File
@@ -128,7 +128,7 @@ ConfigMap is used to store the configuration of the operator
First you need to install the service account definition in your Minikube cluster. First you need to install the service account definition in your Minikube cluster.
$ kubectl --context minikube create -f manifests/serviceaccount.yaml $ kubectl --context minikube create -f manifests/operator-service-account-rbac.yaml
Next deploy the postgres-operator from the docker image Zalando is using: Next deploy the postgres-operator from the docker image Zalando is using:
@@ -173,8 +173,7 @@ kubectl create -f manifests/postgres-operator.yaml
kubectl create -f manifests/minimal-postgres-manifest.yaml kubectl create -f manifests/minimal-postgres-manifest.yaml
``` ```
Note that the service account in `operator-rbac.yaml` is named `zalando-postgres-operator` and not Note that the service account in `operator-rbac.yaml` is named `zalando-postgres-operator`. You may have to change the `service_account_name` in the operator configmap and `serviceAccountName` in the postgres-operator deployment appropriately.
the `operator` default that is created in the `serviceaccount.yaml`. So you will have to change the `service_account_name` in the operator configmap and `serviceAccountName` in the postgres-operator deployment appropriately.
This is done intentionally, as to avoid breaking those setups that This is done intentionally, as to avoid breaking those setups that
already work with the default `operator` account. In the future the operator should ideally be run under the already work with the default `operator` account. In the future the operator should ideally be run under the