-
Bug
-
Resolution: Done-Errata
-
Major
-
4.12
-
None
-
ODC Sprint 236
-
1
-
Rejected
-
False
-
Description of problem:
ODC automatically loads all Camel K Kamelets from openshift-operators namespace in order to display those resources in the event sources/sinks catalog. This is not working when the Camel K operator is installed in another namespace (e.g. in Developer Sandbox the Camel K operator had to be installed in camel-k-operator namespace)
Version-Release number of selected component (if applicable):
4.12
How reproducible:
Display event sources/sinks catalog in ODC on a cluster where Camel K is installed in a namespace other than openshift-operators (e.g. Developer Sandbox)
Steps to Reproduce:
1. Make sure to have a cluster where Knative eventing is available 2. Install Camel K operator in camel-k-operator namespace (e.g. via OLM) 3. Display the event source/sink catalog in ODC
Actual results:
No Kamelets are visible in the catalog
Expected results:
All Kamelets (automatically installed with the operator) should be visible as potential event sources/sinks in the catalog
Additional info:
The Kamelet resources are being watched in two namespaces (current user namespace and global operator namespace. https://github.com/openshift/console/blob/master/frontend/packages/knative-plugin/src/hooks/useKameletsData.ts#L12-L28 We should allow configuration of the global namespace or also add camel-k-operator namespace as 3rd place to look for installed Kamelets.
- blocks
-
OCPBUGS-15982 Load Kamelets as event sources/sinks from custom Camel K operator namespace
- Closed
- is cloned by
-
OCPBUGS-15982 Load Kamelets as event sources/sinks from custom Camel K operator namespace
- Closed
- links to
-
RHSA-2023:5006 OpenShift Container Platform 4.14.z security update