For the ODC integration, we need a catalog of (verified) Kamelets that the developer console can lean on to create event sources. We host a catalogue of sources (see https://issues.redhat.com/browse/ENTESB-14697) and this information needs to be packaged with the Camel K operator and made accessible tot he ODC console when the Camel K operator is installed.

How it works:

• When the user installs the operator in a namespace, upon startup of the operator, all embedded kamelets will be installed in that namespace.
• If the user installs the operator globally, each time the user creates an IntegrationPlatform in a namespace, then the global operator will install all kamelets in that namespace.