Skip to content

Upgrade to 1.2 very hard when using PDB resources #168

Open
@ilfur

Description

@ilfur

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions