Community operators fail to install with "unpack job not completed: " about community-operators-prod HOT 2 CLOSED

You are using OCP 4.9 and seems that these projects are distribution versions that are not compatible with 4.9 and is using APIs which were removed from k8s 1.22 and OCP 4.9. More info: #138.

The look the examples provided by you:

• spark-gcp is using the removed and not supported APIs for CRDs : https://github.com/k8s-operatorhub/community-operators/blob/main/operators/spark-gcp/2.4.0/sparkapplications.sparkoperator.k8s.io.crd.yaml#L1
• etcd: https://github.com/k8s-operatorhub/community-operators/blob/main/operators/etcd/0.9.4/etcdbackups.etcd.database.coreos.com.crd.yaml#L1

Then, see that https://github.com/coreos/etcd-operator seems no longer maintained and we already raised an issue for the authors of spark-gcp: kubeflow/spark-operator#1339

Note that the 4.9 index for community operators is not generated yet. However, our plan is to deprecate all distributions and not publish the scenarios that we are able to identify that does not work on 4.9 from 4.9+ index to avoid it.

from community-operators-prod.

Hi @tbuskey,

Note that now the 4.9 indexes were built for community operators. So, you ought to use this index to do the test,
Then, if you find any problem with the distributions made on it let us know. Also, you will see that the community index for 4.9 does not have the projects and the scenarios which are programmatically able to check the usage of the removed APIs in 1.22/OCP 4.9 or the ones that were configured by the authors to not be published on 4.9.

Our checks are limited to the manifests inside and are not bulletproof. But, these tests cover the most common scenarios. The authors should also be contacted in case of problems.

It seems that we ought to close this issue as well.

from community-operators-prod.