# PITR in Kubernetes Cluster not being taken - Operator not found

**URL:** <https://forums.percona.com/t/pitr-in-kubernetes-cluster-not-being-taken-operator-not-found/14720>\
**Category:** Percona Backup for MongoDB\
**Tags:** troubleshooting\
**Created:** [March 11, 2022, 3:18pm UTC](https://forums.percona.com/t/pitr-in-kubernetes-cluster-not-being-taken-operator-not-found/14720 "2022-03-11T15:18:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon17965173](https://avatars.discourse-cdn.com/v4/letter/a/278dde/32.png) [@anon17965173](https://forums.percona.com/u/anon17965173)\
**Post date:** [March 11, 2022, 3:18pm UTC](https://forums.percona.com/t/pitr-in-kubernetes-cluster-not-being-taken-operator-not-found/14720/1 "2022-03-11T15:18:01Z")

</div>

I have PITR enabled as per documentation:

```auto

backup:
  enabled: true
  restartOnFailure: true
  image:
    repository: percona/percona-server-mongodb-operator
    tag: 1.11.0-backup
  serviceAccountName: percona-server-mongodb-operator
  resources:
  limits:
    cpu: "2500m"
    memory: "4Gi"
  requests:
    cpu: "256m"
    memory: "0.256Gi"
  storages:
    my-s3:
      type: s3
      s3:
        bucket: my-bucket
        credentialsSecret: my-secret
        endpointUrl: my-url
  pitr:
    enabled: true
  tasks:
   - name: daily
     enabled: true
     schedule: "0 0 * * *"
     keep: 30
     storageName: my-s3
     compressionType: gzip

```

When I do: `kubectl describe psmdb-backup`, I see latest backup was take a month ago, which was the manual backup I did back then, to proove S3 connection works fine.

I then do:

`kubectl describe job.batch/percona-db-psmdb-db-backup-daily-27427680` and get:

```auto
Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Warning FailedCreate 7m47s (x3811 over 15d) job-controller Error creating: pods "percona-db-psmdb-db-backup-daily-27427680-" is forbidden: error looking up service account default/percona-server-mongodb-operator: serviceaccount "percona-server-mongodb-operator" not found
  Warning FailedCreate 54s (x4 over 2m4s) job-controller Error creating: pods "percona-db-psmdb-db-backup-daily-27427680-" is forbidden: error looking up service account default/percona-server-mongodb-operator: serviceaccount "percona-server-mongodb-operator" not found

```

I then do: `kubectl describe sa percona-operator-psmdb-operator` and get:

```auto
Name: percona-operator-psmdb-operator
Namespace: default
Labels: app.kubernetes.io/managed-by=Helm
Annotations: meta.helm.sh/release-name: percona-operator
                     meta.helm.sh/release-namespace: default
Image pull secrets: <none>
Mountable secrets: percona-operator-psmdb-operator-token-sbl45
Tokens: percona-operator-psmdb-operator-token-sbl45
Events: <none>

```

What could the problem be in this case?

---

<div class="post-metadata">

**Author:** ![anon17965173](https://avatars.discourse-cdn.com/v4/letter/a/278dde/32.png) [@anon17965173](https://forums.percona.com/u/anon17965173)\
**Post date:** [March 11, 2022, 8:13pm UTC](https://forums.percona.com/t/pitr-in-kubernetes-cluster-not-being-taken-operator-not-found/14720/2 "2022-03-11T20:13:29Z")

</div>

The solution was to fix the name mismatch between the helm chart and the actual service account name as described in this thread: [Backup task used wrong sa ?!](https://forums.percona.com/t/backup-task-used-wrong-sa/14158)

This should be fixed in the helm chart. I don’t remember changing the key `serviceAccountName` in the helm chart.