Open rhuss opened 11 months ago
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen
. Mark the issue as
fresh by adding the comment /remove-lifecycle stale
.
/remove-lifecycle stale
When creating a binding with e.g.
kn source kamelet binding create my-source --broker default --kamelet chuck-norris-source
and a global installation for the Camel-K operator, and thechuck-norris-source
is available in thecamel-system
namespace, then the following error appears:This is because the validation doesn't check the kamelet in the "system namespace". The challenge here is to find out what the system namespace is.
Several solution could be possible:
KameletCatalog
that would store all available kamelets from the system namespace either in thespec:
or in thestatus:
field, and gets populated by the operator.ClusterKamelet
that is a real cluster-wide resource (and not a namespaced resource in a special namespace that is not necessarily fixed). This might pose a problem for multi-tenant setups, but it's the easiest thing to lookupk get kamelet -A
and check those field whether it could be used.If nothing of this work, then there should be at least a way to skip the validation (like e.g. with a
--force
option)