From 118c1146bf949e694a8de416bc17073e6aef8c4c Mon Sep 17 00:00:00 2001 From: Pierre Ozoux Date: Fri, 17 Jul 2026 11:57:30 +0200 Subject: [PATCH] docs: correct kubectl commands (#3129) Co-authored-by: Felix Kunde Co-authored-by: Ida Novindasari --- docs/reference/operator_parameters.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/reference/operator_parameters.md b/docs/reference/operator_parameters.md index cf1d18c14..02c6db8d0 100644 --- a/docs/reference/operator_parameters.md +++ b/docs/reference/operator_parameters.md @@ -42,14 +42,14 @@ and change it. To test the CRD-based configuration locally, use the following -```bash - kubectl create -f manifests/operatorconfiguration.crd.yaml # registers the CRD - kubectl create -f manifests/postgresql-operator-default-configuration.yaml +``` +kubectl create -f manifests/operatorconfiguration.crd.yaml # registers the CRD +kubectl create -f manifests/postgresql-operator-default-configuration.yaml - kubectl create -f manifests/operator-service-account-rbac.yaml - kubectl create -f manifests/postgres-operator.yaml # set the env var as mentioned above +kubectl create -f manifests/operator-service-account-rbac.yaml +kubectl create -f manifests/postgres-operator.yaml # set the env var as mentioned above - kubectl get operatorconfigurations postgresql-operator-default-configuration -o yaml +kubectl get operatorconfigurations postgresql-operator-default-configuration -o yaml ``` The CRD-based configuration is more powerful than the one based on ConfigMaps