-
Bug
-
Resolution: Obsolete
-
Critical
-
None
-
None
-
None
-
%
-
After talking to Lance, we realised that the current OLM metadata for the Camel-K operator appears to be using the new bundle format, but in fact it's not.
There are two main changes needed:
a) Remove the manifests from the operator and rely on a spearate bundle image: http://pkgs.devel.redhat.com/cgit/containers/fuse-camel-k/tree/Dockerfile?h=fuse-8.0-openshift-rhel-8#n86
b) Update the bundle image to use the new format, it looks like it (i.e. annotations dir), but it's not using the proper structure: http://pkgs.devel.redhat.com/cgit/containers/fuse-camel-k/tree/operator-bundle/manifests?h=fuse-8.0-openshift-rhel-8
For b) please consult https://github.com/operator-framework/operator-registry/blob/master/docs/design/operator-bundle.md
- is related to
-
ENTESB-13959 Released Camel-K TP1 installation does not work from OperatorHub
- Done