> Hi,
> I've updated the master to use M3-SNAPSHOT, since we've cut a release of M2
> last saturday.
That did the trick, thanks a lot.
Cheers,
Luca Morandini
d "exec: \"kamel\": executable file not found
in $PATH"
Back-off restarting failed container
>>
Needless to say, the executable seems to be in the image when I try to
'docker run' it (the image can be found at
docker.io/lmorandini/camel-k:1.0.0-M2-SNAPSHOT).
Any help appreciated,
Luca Morandini
On Wed, Sep 18, 2019 at 7:46 PM Luca Morandini
wrote:
>
> However, the camel-k-cache still does not start ("pod has unbound
> PersistentVolumeClaims").
Creating a Persistent Volume and a Storage Class with a
"storageclass.kubernetes.io/is-default-class: true"
local/go/src/runtime/proc.go:200"}
How can I make the PV writable by the builder?
The cluster is K8s on OpenStack.
Cheers,
Luca Morandini
On Mon, Sep 9, 2019 at 6:03 PM Luca Morandini wrote:
>
> I was not able to deploy Camel-K on a K8s cluster due to
I patched-up Camel-K by adding the option of disabling the cache
(--skip-kaniko-build-cache=true) -see
(https://github.com/apache/camel-k/issues/736.
However, the camel-k
Folks,
I was not able to deploy Camel-K on a K8s cluster due to
(https://github.com/apache/camel-k/issues/736).
This issue was fixed a few days ago, but I'd rather avoid building the
client from source: could you please tell me the ETA of a new (and
patched-up) release?
Cheers,
Luca Morandini
