Is there an existing issue already for this bug?

• I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

• I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

• I have read the troubleshooting guide and I think this is a new bug.

Contact Details

No response

Version

1.28 (latest patch)

What version of Kubernetes are you using?

1.34

What is your Kubernetes environment?

Self-managed: kind (evaluation)

How did you install the operator?

YAML manifest

What happened?

If you create a cluster with the cnpg.io/skipWalArchiving: 'enabled' annotation, the status command will not understand that and show that archiving is starting up.

Continuous Backup status
First Point of Recoverability:  Not Available
Working WAL archiving:          Starting Up
WALs waiting to be archived:    0
Last Archived WAL:              -
Last Failed WAL:                -

It should show "disabled".

Cluster resource

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct