When we added structural schemas, we inadvertently dropped v1alpha2 operatorgroup. This wasn't communicated as a deprecated api, so we should not remove it from 4.4.
4.3 still has the v1alpha2, but this backport PR needs to be updated to include it before it can merge: https://github.com/operator-framework/operator-lifecycle-manager/pull/1197
Marking the related bug blocked on this one.
Moving this to 4.5, will clone to 4.4 and 4.3
Cluster version: 4.5.0-0.nightly-2020-03-06-190457
1, Create an OperatorGroup object with the v1alpha2 api version.
oc create -f og.yaml operatorgroup.operators.coreos.com/test-og created
oc get og -n default test-og -o yaml
The OperatorGroup works well, LGTM, verify it.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.