Skip to content

Upgrade to 1.2 very hard when using PDB resources #168

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ilfur opened this issue Apr 2, 2025 · 1 comment
Open

Upgrade to 1.2 very hard when using PDB resources #168

ilfur opened this issue Apr 2, 2025 · 1 comment

Comments

@ilfur
Copy link

ilfur commented Apr 2, 2025

OraOperator 1.2 uses new version number for its resources, mainly v4.
The older v1alpha1 version is still there for most other resources so they can get upgraded,
Unfortunately, for "PDB" resources, the v1alpha1 version support is gone, only v4 working.

To describe the urge of my request to add v1alpha1 support for PDBs for a successful upgrade:
First I failed to upgrade because of missing v1alpha1 support in the CRD for PDBs.
So I uninstalled/re-installed OraOperator . My PDB resources were gone and all my hosted SingleInstanceDatabases too. Uninstalling all of my helm charts that use a PDB was also hard, helm complaining that there was no-one there to take care of v1alpha1 PDBs. So I manually had to uninstall all app components of PDB based apps (configmaps secrets, deployments, jobs,....)
So this had some serious consequences in my environment. If only I had manually added v1alpha1 support in the OraOperator 1.2 CRDs myself - but I did not get to that idea in time...

Best regards!

@ilfur
Copy link
Author

ilfur commented Apr 7, 2025

Please do assign someone to fix that and include v1alpha1 support for PDBs again, does not need to be active support but the version has to be present for upgrades.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant