Re: [I] Running integrations fail when the used registry has a port other than default 80 [camel-k]
bvahdat commented on issue #5141: URL: https://github.com/apache/camel-k/issues/5141#issuecomment-1995873819 >... there is no need to provide the --registry option during installation as it will be discovered by the tooling. Thanks @squakez, that did the trick 👍 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Running integrations fail when the used registry has a port other than default 80 [camel-k]
squakez commented on issue #5141: URL: https://github.com/apache/camel-k/issues/5141#issuecomment-1994477864 I think the port forward is meant to expose a Kubernetes service in your host machine and not the other way around. If you are using a registry as a Pod [1] (which is already done ootb by Minikube) you need to provide the IP to the operator. As you're running the operator in Minikube, there is no need to provide the `--registry` option during installation as it will be discovered by the tooling. [1] https://camel.apache.org/camel-k/2.2.x/installation/registry/own.html#configuring-registry-run-pod -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Running integrations fail when the used registry has a port other than default 80 [camel-k]
bvahdat commented on issue #5141: URL: https://github.com/apache/camel-k/issues/5141#issuecomment-1994126959 > ... it seems you're connecting to a registry expected to be found at locahost, that means, on the same Pod where the operator is running ... Thanks @squakez. As already provided by the command snippets I make use of [port-forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) which should do the job using `localhost`. By any chance, would you be able to run the [hello.groovy](https://camel.apache.org/camel-k/2.2.x/running/running.html) sample on Minikube and see if that would work for you? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Running integrations fail when the used registry has a port other than default 80 [camel-k]
squakez commented on issue #5141: URL: https://github.com/apache/camel-k/issues/5141#issuecomment-1987849459 I am looking more carefully at this and I think the error message you got is misleading. Having another look at the operator log, it seems you're connecting to a registry expected to be found at `locahost`, that means, on the same Pod where the operator is running. When specifying the registry, you need to provide a resolvable address for the Pod where the operator is running. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Running integrations fail when the used registry has a port other than default 80 [camel-k]
bvahdat commented on issue #5141: URL: https://github.com/apache/camel-k/issues/5141#issuecomment-1986599401 Thanks @squakez for looking into this. So what this means is that currently using [minikube registry](https://minikube.sigs.k8s.io/docs/handbook/registry/) with it's default port `5000` one can not run any camel-k integration. Maybe this needs to mentioned [here](https://camel.apache.org/camel-k/2.2.x/installation/platform/minikube.html)? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Running integrations fail when the used registry has a port other than default 80 [camel-k]
squakez commented on issue #5141: URL: https://github.com/apache/camel-k/issues/5141#issuecomment-1985579038 It seems the problem is not directly on Camel K side, but in the registry that for some reason cannot parse correctly the tag due to the presence of 2 colons. Likely it's this issue that seem to affect Harbor registries: https://github.com/GoogleContainerTools/kaniko/issues/2414 Closing for now, as at this stage we cannot do much more to help with this problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Running integrations fail when the used registry has a port other than default 80 [camel-k]
squakez closed issue #5141: Running integrations fail when the used registry has a port other than default 80 URL: https://github.com/apache/camel-k/issues/5141 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] Running integrations fail when the used registry has a port other than default 80 [camel-k]
bvahdat opened a new issue, #5141:
URL: https://github.com/apache/camel-k/issues/5141
### What happened?
It seems when the registry has a port other than the default `80` then
parsing the registry URL for pushing the tag fails. For more details see also
https://camel.zulipchat.com/#narrow/stream/257299-camel-k/topic/repository.20can.20only.20contain.20the.20characters.2E.2E.2E
Please note that I don't make use of the `docker` driver but `qemu`, though
I believe that would make no difference in the observed behaviour.
### Steps to reproduce
Running on a `Apple M1 ARM64` machine here the steps I ran into this problem:
# install minikube
$> minikube start --driver=qemu --network socket_vmnet --addons registry
😄 minikube v1.32.0 on Darwin 14.2.1 (arm64)
✨ Using the qemu2 driver based on user configuration
💿 Downloading VM boot image ...
> minikube-v1.32.1-arm64.iso: 65 B / 65 B [-] 100.00% ? p/s
0s
> minikube-v1.32.1-arm64.iso: 342.84 MiB / 342.84 MiB 100.00% 15.69
MiB p
👍 Starting control plane node minikube in cluster minikube
💾 Downloading Kubernetes v1.28.3 preload ...
> preloaded-images-k8s-v18-v1...: 341.16 MiB / 341.16 MiB 100.00%
16.95 M
🔥 Creating qemu2 VM (CPUs=2, Memory=6000MB, Disk=2MB) ...
🐳 Preparing Kubernetes v1.28.3 on Docker 24.0.7 ...
▪ Generating certificates and keys ...
▪ Booting up control plane ...
▪ Configuring RBAC rules ...
🔗 Configuring bridge CNI (Container Networking Interface) ...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🔎 Verifying Kubernetes components...
▪ Using image docker.io/registry:2.8.3
▪ Using image gcr.io/k8s-minikube/kube-registry-proxy:0.0.5
🔎 Verifying registry addon...
🌟 Enabled addons: storage-provisioner, default-storageclass, registry
🏄 Done! kubectl is now configured to use "minikube" cluster and "default"
namespace by default
# verify the registry is running properly
$> minikube ssh "curl localhost:5000/v2/_catalog"
{"repositories":[]}
# do port forwarding
$> kubectl port-forward --namespace kube-system service/registry 1:80
Forwarding from 127.0.0.1:1 -> 5000
Forwarding from [::1]:1 -> 5000
# verify that port forwarding works
$> curl localhost:1/v2/_catalog
{"repositories":[]}
# install kamel CLI
$> kamel install --olm=false --log-level debug --operator-image
apache/camel-k:2.2.0-arm64 --base-image
eclipse-temurin:17@sha256:cea8b177ad564c588b33615042fd5ab9e77c1ada49d446e27e2ead2be8a5709b
--registry "http://localhost:1"; --registry-insecure=true
# verify the created POD
$> kubectl get pods
NAME READY STATUSRESTARTS AGE
camel-k-operator-d644cc86f-w56n8 1/1 Running 0 15s
# run hello.groovy from the camel-k documentation
$> kamel run hello.groovy --dev
Integration "hello" created
Progress: integration "hello" in phase Initialization
Condition "IntegrationPlatformAvailable" is "True" for Integration hello:
default/camel-k
Integration "hello" in phase "Initialization"
Progress: integration "hello" in phase Building Kit
Condition "TraitInfo" is "True" for Integration hello: explicitly disabled
by the user
Integration "hello" in phase "Building Kit"
Condition "IntegrationKitAvailable" is "False" for Integration hello:
creating a new integration kit
Integration Kit "kit-cn1kg9t4a17aqu7g", created by Integration "hello",
changed phase to "Build Submitted"
Build "kit-cn1kg9t4a17aqu7g", created by Integration "hello", changed
phase to "Scheduling"
Build "kit-cn1kg9t4a17aqu7g", created by Integration "hello", changed
phase to "Pending"
Build "kit-cn1kg9t4a17aqu7g", created by Integration "hello", changed
phase to "Running"
Integration Kit "kit-cn1kg9t4a17aqu7g", created by Integration "hello",
changed phase to "Build Running"
Build "kit-cn1kg9t4a17aqu7g", created by Integration "hello", changed
phase to "Failed"
Build "kit-cn1kg9t4a17aqu7g", created by Integration "hello", changed
phase to "Initialization" (recovery 1 of 5)
Build "kit-cn1kg9t4a17aqu7g", created by Integration "hello", changed
phase to "Scheduling" (recovery 1 of 5)
Build "kit-cn1kg9t4a17aqu7g", created by Integration "hello", changed
phase to "Pending" (recovery 1 of 5)
Build "kit-cn1kg9t4a17aqu7g", created by Integration "hello", changed
phase to "Running" (recovery 1 of 5)
Build "kit-cn1kg9t4a17aqu7g", created by Integration "hello", changed
phase to "Failed" (recovery 1 of 5)
### Relevant log output
```shell
$> kubectl logs -f camel-k-operator-d644cc86f-w56n8
{"level":"debug","ts":"2024-02-07T09:06:47Z","logger":"events","msg":"Integration
Kit \"kit-cn1kg9t4a17aqu7g\" in phase \"Build
Running\"","type":"Norm
