Pasquale Congiusti
Pasquale Congiusti
I'd even consider moving k8s api forward. However I don't know which is the impact there. @astefanutti may add his opinion about that. But yes, we can move a little...
> Install serverless-operator.v1.22.0 In `1.8.2` community version we're aligned with Knative `1.1.0` version. Please, make sure to use that version of the community Knative operator and confirm if it's still...
If you can recover the operator for 1.1.0 would be better, though the patch release should not be a problem in terms of compatibility.
Thanks for your interest.
> The mount trait will just mount the PVC, no matter if the PVC is statically or dynamically provisioned. > > Is that right @squakez @astefanutti ? Yes, that's my...
I think the idea of the issue is to have the trait accepting the parameters to create the PVC on the fly. As an example, we can think the following...
@haanhvu we may reason about that for sure. In any case, the business logic would be pretty similar and you'd need to related the mount trait anyway. IMO, we should...
No we have nothing like that. Maybe we could think to introduce a syntax such as `namespace/kit`.
Let's wait for others input. I have no strong opinion about the possibility to use cross namespace references, but others may have concerns about that.
I think the new `kamel promote` (https://github.com/apache/camel-k/pull/3325) may be your solution. You can already use installing nightly build or waiting for 1.10 release.