Hi All,
Just bouncing something I've found and seeing if anyone else has also seen the issue.
I am hoping someone else has seen this and help validate that there is an underlying problem brewing.
After having a 'stable' API version in the dynakube CRD for many years (I could just upgrade the operator and not change the Dynakube), Dynatrace has recently introduced multiple new Dynakube CRD API versions (v1beta1 -> v1beta5), more recently 1.5.x operator onwards has somewhat been tied to a new API version each release based newly introduced functionality. Even though older API versions are supported, there has also been a 'supported version' introduced, meaning that an upgrade will be inevitable.
** I am using the OCI approach and automated deployment via flux, I am making sure that the order of operator, then dynakube is enforced.
I am seeing an issue where:
The upgrade from Dynakube CRD API xxx -> yyy fails due to incompatible CRD's once the operator has been upgraded. I can no longer just apply a the CRD, but need to delete the existing Dynakube first (technically uninstalling dynatrace), then run the operator upgrade, then re-apply the updated CRD. It looks like the updated operator is removing the previous CRD'S, required for the Dynakube to work.
I don't really care about getting new API versions, but more around the issues in upgrading not working cleanly.
