add type to enums in crd validation

This commit is contained in:
Felix Kunde
2019-11-26 11:16:02 +01:00
parent 99bb2041ae
commit ba528cba4b
6 changed files with 19 additions and 6 deletions
+1 -2
View File
@@ -79,8 +79,7 @@ to function under access control restrictions. To deploy the operator with this
RBAC policy use:
```bash
kubectl create -f manifests/operatorconfiguration.crd.yaml
kubectl create -f manifests/postgresql-operator-default-configuration
kubectl create -f manifests/configmap.yaml
kubectl create -f manifests/operator-service-account-rbac.yaml
kubectl create -f manifests/postgres-operator.yaml
kubectl create -f manifests/minimal-postgres-manifest.yaml
+1 -2
View File
@@ -80,8 +80,7 @@ manifest but replace the version and tag. Don't forget to also apply
configuration and RBAC manifests first, e.g.:
```bash
kubectl create -f manifests/operatorconfiguration.crd.yaml
kubectl create -f manifests/postgresql-operator-default-configuration
kubectl create -f manifests/configmap.yaml
kubectl create -f manifests/operator-service-account-rbac.yaml
sed -e "s/\(image\:.*\:\).*$/\1$TAG/" manifests/postgres-operator.yaml | kubectl create -f -
+1 -2
View File
@@ -49,8 +49,7 @@ git clone https://github.com/zalando/postgres-operator.git
cd postgres-operator
# apply the manifests in the following order
kubectl create -f manifests/operatorconfiguration.crd.yaml # configuration CRD
kubectl create -f manifests/postgresql-operator-default-configuration # default configuration
kubectl create -f manifests/configmap.yaml # configuration
kubectl create -f manifests/operator-service-account-rbac.yaml # identity and permissions
kubectl create -f manifests/postgres-operator.yaml # deployment
```