Gaëlle Fournier
Gaëlle Fournier
The `kamel kit delete` completion already exists : the command only shows non-platform kits. Is this behavior something that should evolve to all kits (even the platform ones) for the...
@tadayosi @squakez What is expected on then `kamel bind` autocomplete ? While we could default to the custom resources `kamelets.camel.apache.org`, the command description "Bind Kubernetes resources, such as Kamelets, in...
> I think the general idea was that kits of type `platform` are managed by the operator, as opposed to kits created by users, and should be "hidden" away from...
Hi, > Hi, > > Actually, no, you cannot delete platform kits with `kamel kit delete`. They are protected from cli. There's even no flag to force performing it. So...
Hi @ramsayleung, just so you know there is an error in the issue link `https://github.com/ramsayleung/rspotify/issues/452m` (trailing **m**) in your Spotify ticket.
Please don't hesitate to check the troubleshooting documentation to know what to look for: https://camel.apache.org/camel-k/2.2.x/troubleshooting/troubleshooting.html
If this is an arm64 architecture processor you should follow the [installation documentation](https://camel.apache.org/camel-k/2.2.x/installation/advanced/multi-architecture.html). The Kamel CLI defaults to x86 image so you need to set the arm64 operator image explicitly,...
@squakez I'll take care of this.
@squakez I'll update the trait doc.
@squakez @oscerd @christophd @claudio4j Could the tests be triggered please :pray: