fix(mongodb-store): bump psmdb-operator to 1.22.0

Percona's server-mongodb-operator 1.21.x has a bug in its cert-manager
TLS handling: when cert-manager is run with
`--enable-certificate-owner-ref=true`, it sets the Certificate object
as the controller-owner of the Secrets it issues. The operator's
WaitForCerts() in that version unconditionally tries to also set the
PerconaServerMongoDB CR as controller-owner of the same Secret,
which Kubernetes rejects since an object can only have one
controller-owner reference. This makes cert-manager-issued TLS
never come up when that cert-manager flag is enabled, on every
reconcile, with no automatic recovery:

  TLS secrets handler: "create ssl by cert-manager: update cert
  mangager certs: failed to apply cert-manager certificates: failed
  to wait for ca cert: set controller reference: Object
  <ns>/<cluster>-ca-cert is already owned by another Certificate
  controller <cluster>-ca-cert". Please create your TLS secret
  <cluster>-ssl manually or setup cert-manager correctly

This is a known upstream issue, fixed in 1.22.0 by adding an
IsControlledBy() check before attempting to set the owner reference:
percona/percona-server-mongodb-operator#1981

Bumps the vendored psmdb-operator subchart's image tag from 1.21.0 to
1.22.0 and regenerates Chart.lock. The vendored CRDs are unchanged;
1.22.0's release notes list only additive, optional features
(service-mesh appProtocol, restore replset remapping, disable-auth
option, custom env vars), none of which mongodb-store's psmdb-db
values currently use, so running 1.22.0 against the existing CRD
schema is expected to be safe.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: jtschelling

distros/kubernetes/nvsentinel/charts/mongodb-store/Chart.lock

@@ -4,9 +4,9 @@ dependencies:
   version: 16.2.2
 - name: psmdb-operator
   repository: ""
-  version: 1.21.1
+  version: 1.22.0
 - name: psmdb-db
   repository: ""
   version: 1.21.1
-digest: sha256:52544f60c2e88079cc18da78164440e042103e5adc065668a648864e2ad938b9
-generated: "2025-11-19T15:26:21.985280107+05:30"
+digest: sha256:1b23ec6672ce758cfa2bb8346506c6c08ef01d2a5a964e049f680115799f4235
+generated: "2026-08-24T16:59:58.660281-07:00"

distros/kubernetes/nvsentinel/charts/mongodb-store/Chart.yaml

@@ -25,7 +25,7 @@ dependencies:
     repository: ""
     condition: useBitnami
   - name: psmdb-operator
-    version: "1.21.1"
+    version: "1.22.0"
     repository: ""
     condition: usePerconaOperator
   - name: psmdb-db

distros/kubernetes/nvsentinel/charts/mongodb-store/charts/psmdb-operator/Chart.yaml

@@ -1,5 +1,5 @@
 apiVersion: v2
-appVersion: 1.21.0
+appVersion: 1.22.0
 description: A Helm chart for deploying the Percona Operator for MongoDB
 home: https://docs.percona.com/percona-operator-for-mongodb/
 maintainers:
@@ -10,4 +10,4 @@ maintainers:
 - email: eleonora.zinchenko@percona.com
   name: eleo007
 name: psmdb-operator
-version: 1.21.1
+version: 1.22.0

distros/kubernetes/nvsentinel/charts/mongodb-store/charts/psmdb-operator/values.yaml

@@ -6,7 +6,7 @@ replicaCount: 1
 
 image:
   repository: percona/percona-server-mongodb-operator
-  tag: 1.21.0
+  tag: 1.22.0
   pullPolicy: IfNotPresent
 
 # disableTelemetry: according to