[Bug]: Upgrading CNPG operator #11723

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

vishal.tanawade@emerson.com

Version

trunk (main)

What version of Kubernetes are you using?

1.34

What is your Kubernetes environment?

Cloud: Azure AKS

How did you install the operator?

Helm

What happened?

Hi @dosu,

I am using CNPG 1.26 with Barman plugin 0.11.0.
I am taking backups on azure blob storage.
I am using image catalog, Scheduled backups, on demand backups , restore database, delete database features of CNPG.

As of now current version is 1.30.1 . now i want to upgrade to latest version.

Can i directly upgrade to latest version or should I upgrade one by one minor version? and why?

In existing cluster there are around 100-200 db running which uses CNPG 1.26 . so will there any impact of that db /data loss?
Can i upgrade only CNPG and use Barman old plugin (0.11.0) or it is not compatible.
What are the steps to upgrade it. Give my all steps with step details / step number.
It both (CNPG and Barman) should be upgraded then give detailed steps for both.
Also, what will happened to existing db clusters / data?
what are the steps we need to verify like db creation , taking backup like that.

@dosu , please help

Cluster resource

Relevant log output

Code of Conduct

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