Done
Details
Assignee
dmitriy.kostiukdmitriy.kostiuk(Deactivated)Reporter
Pavel TankovPavel Tankov(Deactivated)Needs QA
YesComponents
Fix versions
Affects versions
Priority
Medium
Details
Details
Assignee
dmitriy.kostiuk
dmitriy.kostiuk(Deactivated)Reporter
Pavel Tankov
Pavel Tankov(Deactivated)Needs QA
Yes
Components
Fix versions
Affects versions
Priority
Smart Checklist
Smart Checklist
Smart Checklist
Created November 8, 2023 at 2:57 PM
Updated March 5, 2024 at 3:42 PM
Resolved December 20, 2023 at 8:59 AM
https://docs.percona.com/percona-operator-for-postgresql/2.0/cluster-wide.html?h=wide#namespace-scope
I am following the official documentation about installing PGO in a Namespace-scope. I follow the steps verbatim:
kubectl create namespace percona-db-1 namespace/percona-db-1 created kubectl apply -f deploy/operator.yaml -n percona-db-1 deployment.apps/percona-postgresql-operator created kubectl apply -f deploy/cr.yaml -n percona-db-1 error: resource mapping not found for name: "cluster1" namespace: "" from "deploy/cr.yaml": no matches for kind "PerconaPGCluster" in version "pgv2.percona.com/v2" ensure CRDs are installed first
I think the proper command is:
kubectl apply -f deploy/bundle.yaml -n percona-db-1