Investigate Camel K deployment on k3d

[orpiske]

Basically, we need to investigate deploying and running Camel K on k3d. I tried it this week and it did not work. There's a brief mention about it as well by @johnpoth on the issue #2302.

[johnpoth]

hi @orpiske works fine for me :) For basic clusters I use

k3d cluster create camel-k --registry-create

what kind of errors are you getting ?

[orpiske]

hi @orpiske works fine for me :) For basic clusters I use

k3d cluster create camel-k --registry-create

what kind of errors are you getting ?

So, it looks like Camel K is trying to use HTTPs to access the registry, but, apparently, k3d uses only HTTP.

{"level":"error","ts":1626798994.1791985,"logger":"camel-k.controller.build","msg":"Build kit-c3rflojh3lth2r39adp0 failed: could not pull base image image k3d-registry:5000/adoptopenjdk/openjdk11:slim: Get \"htt
ps://k3d-registry:5000/v2/\": dial tcp: lookup k3d-registry on 10.43.0.10:53: server misbehaving","request-namespace":"default","request-name":"kit-c3rflojh3lth2r39adp0","api-version":"camel.apache.org/v1","kind
":"Build","ns":"default","name":"kit-c3rflojh3lth2r39adp0","stacktrace":"github.com/apache/camel-k/pkg/controller/build.(*monitorRoutineAction).updateBuildStatus\n\tgithub.com/apache/camel-k/pkg/controller/build
/monitor_routine.go:191\ngithub.com/apache/camel-k/pkg/controller/build.(*monitorRoutineAction).runBuild\n\tgithub.com/apache/camel-k/pkg/controller/build/monitor_routine.go:175"}

@johnpoth I actually reported this after verifying an issue that was raised to me by another user ... So I am glad to know it is working for you.

What version of Camel K and K3d are you using?

[hguerrero]

@johnpoth can you validate that it works on Mac OSX? It looks like the registry is not available from within the pod. This makes me think that there is a missing configuration. However, there are not enough logs to determine what is not reachable.

[johnpoth]

hello !

Ah yes that's known issue in k3d, unfortunately it doesn't seem to be resolved yet. I used the workaround described in k3d-io/k3d#522 ,

Once setup you want to install Camel-k like so:

kamel install --registry="k3d-camel-k-registry:37060" --registry-insecure=true

Obviously, registry name and port may differ ... Let me know if you have any questions!

HTH

[github-actions]

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

[orpiske]

It looks like this already works, so I'm closing this one.