This bug was initially created as a copy of Bug #1798051
I am copying this bug because:
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.
*** Bug 1804950 has been marked as a duplicate of this bug. ***
Cluster version is 4.4.0-0.nightly-2020-02-20-223401
mac:~ jianzhang$ oc exec catalog-operator-75c9f6d98d-jrx42 -- olm --version
OLM version: 0.14.2
git commit: 3d7f04faecb0072e72858b67af34232f854a17cc
1, Create an OperatorGroup object with the v1alpha2 api version.
mac:~ jianzhang$ cat og.yaml
mac:~ jianzhang$ oc create -f og.yaml
mac:~ jianzhang$ oc get og -n default test-og -o yaml
The OperatorGreoup 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.