Which operator(s) is this request for?
Why this matters
Organizations running the Percona Operator for PostgreSQL gain full independence from the Crunchy Data release cycle, giving Percona the freedom to ship features, fixes, and security patches on its own schedule without waiting for upstream. The renamed CRD group (pstream.pgv2.percona.com) allows the Percona v3 operator and the upstream Crunchy operator to coexist in the same Kubernetes namespace without conflict, protecting existing workloads during evaluation or transition.
Jira: https://perconadev.atlassian.net/browse/K8SPG-1016
Community Note
- Please vote on this issue by adding a 👍 reaction to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, as they generate noise and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Which operator(s) is this request for?
Why this matters
Organizations running the Percona Operator for PostgreSQL gain full independence from the Crunchy Data release cycle, giving Percona the freedom to ship features, fixes, and security patches on its own schedule without waiting for upstream. The renamed CRD group (
pstream.pgv2.percona.com) allows the Percona v3 operator and the upstream Crunchy operator to coexist in the same Kubernetes namespace without conflict, protecting existing workloads during evaluation or transition.Jira: https://perconadev.atlassian.net/browse/K8SPG-1016
Community Note