kubectl logs camel-k-kit-brt2kkf89ag8tugjbqn0-builder -c buildahand see that it's due to that image pull issue. My problem is that I spent 5+ minutes waiting for the pod to error so I could look at it and see what happened. Is there a way to set it to only do one recovery before failing?
Are the camel-k builder pods incompatible with knative when istio injection is turned on for the namespace? I did the following and I am not having any luck until I try the Spectrum build strategy
1) Reset my docker-for-desktop cluster (Kubernetes version 1.16.5 if it matters)
2) Install knative-serving version 1.14 with istio-injection
kubectl label namespace default istio-injection=enabled
4) Run kamel install using the github registry
kamel run --dev --name customers --dependency camel-undertow --property camel.rest.port=8080 --open-api customer-api.json customer-api.xml from the redhat example above.
I'm trying to run kamel on a managed kubernetes cluster with DigitalOcean.
I've setup a namespace for it, and created the registry secret I need to access our container registry (GitLab)
I install kamel using:
kamel install --registry registry.gitlab.com/xxxx/yyyy --registry-secret gitlab-reg --namespace camel
Everything seems to startup. So I then run a standard "Hello World" example:
kamel run Test-Groovy.groovy --namespace camel
It then shows as "building" when I run "kamel get", and in Kubernetes I can see a new pod start up, but the pod continually fails and restarts.
In the logs for the camel-k-operator pods, I see this error:
Error during unshare(CLONE_NEWUSER): Operation not permitted
User namespaces are not enabled in /proc/sys/kernel/unprivileged_userns_clone.
level=error msg="error parsing PID \"\": strconv.Atoi: parsing \"\": invalid syntax"
level=error msg="(unable to determine exit status)"
I can't see any steps I've missed around permissions so I'm unsure where to go next.