percona-operators-on-k8s

To create Percona custom resources safely, verify every CR field, kind, and apiVersion against Percona Developer Knowledge for the installed operator version before emitting manifests. This prevents misconfigurations caused by mismatched fields across different operator versions.

Percona PXC and Percona Server (PS) function as two distinct MySQL operators with different CRDs, apiVersions, and field names. You cannot copy fields between them; manifests must target the specific operator variant you have installed to avoid configuration errors.

Managing backups and PITR for Percona databases involves applying operator-specific patterns for PXC, MongoDB, or PostgreSQL. You must validate backup configuration fields against Percona Developer Knowledge to ensure correct point-in-time recovery setup.

Percona operator manifests fail after upgrades if CR fields or apiVersions mismatch the installed operator version. Always validate your custom resource definitions against Percona Developer Knowledge before applying updated manifests to prevent outages.

No, Percona MongoDB and PostgreSQL operators require distinct custom resource fields and apiVersions. You must verify CR definitions against the specific operator version in Percona Developer Knowledge before emitting any manifests.

The best way to scale Percona database clusters on Kubernetes is by modifying the custom resource with operator-specific scaling patterns, verifying all CR field changes against Percona Developer Knowledge before applying the updated manifest.