You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "diegovisentin (via GitHub)" <gi...@apache.org> on 2023/08/25 16:06:56 UTC
[GitHub] [camel-k] diegovisentin opened a new issue, #4694: Error running integration with private registry
diegovisentin opened a new issue, #4694:
URL: https://github.com/apache/camel-k/issues/4694
I try to use CamelK v2 on Suse RKE2 (a distribution very similar to K3s). For simple environment, I want to use a private registry with plain http (port 80) and no authentication. The "/etc/rancher/rke2/registries.yaml" is
```
mirrors:
"10.43.63.110:80":
endpoint:
- "http://10.43.63.110:80"
```
But the problem is that at some point the build process tries to point to the registry using SSL (so port 443) instead of port 80
This problem seems quite similar to [#4236](https://github.com/apache/camel-k/issues/4236)
Here are the steps I performed:
```
dv@mdwxprd:~$ kubectl get node
NAME STATUS ROLES AGE VERSION
mdwxprd Ready control-plane,etcd,master 31h v1.25.12+rke2r1
```
```
dv@mdwxprd:~$ kubectl get service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubelet ClusterIP None <none> 10250/TCP,10255/TCP,4194/TCP 28h
kubernetes ClusterIP 10.43.0.1 <none> 443/TCP 30h
registry ClusterIP 10.43.63.110 <none> 5000/TCP 25h
```
```
dv@mdwxprd:~$ ./kamel version
Camel K Client 2.0.0
```
```
dv@mdwxprd:~$ ./kamel install --force --olm=false -V --monitoring=true --monitoring-port=8888 --registry '10.43.63.110:5000' --registry-insecure true
Camel K installed in namespace default
```
```
dv@mdwxprd:~$ kubectl get IntegrationPlatform
NAME PHASE BUILD STRATEGY PUBLISH STRATEGY REGISTRY ADDRESS DEFAULT RUNTIME
camel-k Ready routine Spectrum 10.43.63.110:5000 2.16.0
```
```
dv@mdwxprd:~$ kubectl describe IntegrationPlatform
Name: camel-k
Namespace: default
Labels: app=camel-k
Annotations: camel.apache.org/operator.id: camel-k
API Version: camel.apache.org/v1
Kind: IntegrationPlatform
...
Spec:
Build:
Build Configuration:
Maven:
Settings:
Settings Security:
Registry:
Address: 10.43.63.110:5000
Insecure: true
Kamelet:
Traits:
Status:
Build:
Publish Strategy Options:
Kaniko Persistent Volume Claim: camel-k
Base Image: eclipse-temurin:11
Build Catalog Tool Timeout: 1m0s
Build Configuration:
Order Strategy: sequential
Strategy: routine
Maven:
Cli Options:
-V
--no-transfer-progress
-Dstyle.color=never
Local Repository: /etc/maven/m2
Max Running Builds: 3
Publish Strategy: Spectrum
Registry:
Address: 10.43.63.110:5000
Insecure: true
Runtime Version: 2.16.0
Timeout: 5m0s
Cluster: Kubernetes
...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal IntegrationPlatformPhaseUpdated 91s camel-k-integration-platform-controller Integration Platform "camel-k" in phase "Creating"
Normal IntegrationPlatformConditionChanged 89s camel-k-integration-platform-controller Condition "Ready" is "True" for Integration Platform camel-k: integration platform cr
eated
Normal IntegrationPlatformPhaseUpdated 89s camel-k-integration-platform-controller Integration Platform "camel-k" in phase "Ready"
```
```
dv@mdwxprd:~$ kubectl get pod
NAME READY STATUS RESTARTS AGE
camel-k-operator-77b655c7cd-lzmnr 1/1 Running 0 2m12s
registry-7646fbf9b9-2fbhq 1/1 Running 0 4m54s
```
```
dv@mdwxprd:~$ kubectl logs camel-k-operator-77b655c7cd-lzmnr | grep builder
{"level":"info","ts":1692974482.516841,"logger":"camel-k.controller.catalog","msg":"Checking if Camel K builder container 10.43.63.110:5000/default/camel-k-runtime-quarkus-builde
:2.16.0 already exists..."}
{"level":"info","ts":1692974482.529364,"logger":"camel-k.controller.catalog","msg":"Couldn't pull image due to GET http://10.43.63.110:5000/v2/default/camel-k-runtime-quarkus-buil
der/manifests/2.16.0: MANIFEST_UNKNOWN: manifest unknown; map[Tag:2.16.0]"}
{"level":"info","ts":1692974482.529406,"logger":"camel-k.controller.catalog","msg":"Making up Camel K builder container 10.43.63.110:5000/default/camel-k-runtime-quarkus-builder:2
.16.0"}
{"level":"info","ts":1692974482.5295148,"logger":"camel-k.controller.catalog","msg":"spectrum - 2023/08/25 14:41:22 Pulling base image quay.io/quarkus/ubi-quarkus-mandrel-builder-
image:22.2.0.0-Final-java11 (insecure=true)..."}
{"level":"info","ts":1692974488.5420585,"logger":"camel-k.controller.catalog","msg":"spectrum - 2023/08/25 14:41:28 Pushing image 10.43.63.110:5000/default/camel-k-runtime-quarkus
-builder:2.16.0 (insecure=true)..."}
{"level":"info","ts":1692974501.4051602,"logger":"camel-k.controller.catalog","msg":"spectrum - 2023/08/25 14:41:41 10.43.63.110:5000/default/camel-k-runtime-quarkus-builder:2.16.
0: digest: sha256:4430347df867830c1e67d3ca9732a0220444dd8534d518b33b1fe9c3e642f60d size: 3034"}
```
```
dv@mdwxprd:~$ ./kamel run hello.groovy
Integration "hello" created
```
```
dv@mdwxprd:~$ ./kamel get
NAME PHASE KIT
hello Running default/kit-cjk67hssf35s73eekml0
```
```
dv@mdwxprd:~$ kubectl get pod
NAME READY STATUS RESTARTS AGE
camel-k-operator-77b655c7cd-lzmnr 1/1 Running 0 5m51s
hello-5c4cb69d-6rwzw 0/1 ContainerCreating 0 23s
registry-7646fbf9b9-2fbhq 1/1 Running 0 8m33s
```
```
dv@mdwxprd:~$ kubectl get Build -n test -o yaml
apiVersion: v1
items:
- apiVersion: camel.apache.org/v1
kind: Build
...
- spectrum:
baseImage: eclipse-temurin:11
image: 10.43.63.110/default/camel-k-kit-cjk67hssf35s73eekml0:528730
name: spectrum
registry:
address: 10.43.63.110
timeout: 5m0s
...
```
```
dv@mdwxprd:~$ kubectl describe pod hello-5c4cb69d-6rwzw
Name: hello-5c4cb69d-6rwzw
Namespace: default
Priority: 0
Service Account: default
Node: mdwxprd/10.0.10.34
Start Time: Fri, 25 Aug 2023 14:46:39 +0000
Labels: camel.apache.org/integration=hello
pod-template-hash=5c4cb69d
Annotations: camel.apache.org/operator.id: camel-k
cni.projectcalico.org/containerID: e35b742f25093ab55122e282f563d3d8cbfb1f138fcdd55e9d5f35c8282ce9d9
cni.projectcalico.org/podIP: 10.42.0.155/32
cni.projectcalico.org/podIPs: 10.42.0.155/32
Status: Pending
IP: 10.42.0.155
IPs:
IP: 10.42.0.155
Controlled By: ReplicaSet/hello-5c4cb69d
Containers:
integration:
Container ID:
Image: 10.43.63.110/default/camel-k-kit-cjk67hssf35s73eekml0@sha256:ec92a11a157dc90e052973053a234ecc9f5f3b141a33f31ebc72eb0bd692b215
Image ID:
Port: <none>
Host Port: <none>
Command:
/bin/sh
-c
Args:
echo exec java...
...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 103s default-scheduler Successfully assigned default/hello-5c4cb69d-6rwzw to mdwxprd
Warning Failed 43s kubelet Failed to pull image "10.43.63.110/default/camel-k-kit-cjk67hssf35s73eekml0@sha256:ec92a11a157dc90e052973053a234ecc9f5f3b141
a33f31ebc72eb0bd692b215": rpc error: code = DeadlineExceeded desc = failed to pull and unpack image "10.43.63.110/default/camel-k-kit-cjk67hssf35s73eekml0@sha256:ec92a11a157dc90e0529730
53a234ecc9f5f3b141a33f31ebc72eb0bd692b215": failed to resolve reference "10.43.63.110/default/camel-k-kit-cjk67hssf35s73eekml0@sha256:ec92a11a157dc90e052973053a234ecc9f5f3b141a33f31ebc7
2eb0bd692b215": failed to do request: Head "https://10.43.63.110/v2/default/camel-k-kit-cjk67hssf35s73eekml0/manifests/sha256:ec92a11a157dc90e052973053a234ecc9f5f3b141a33f31ebc72eb0bd69
2b215": dial tcp 10.43.63.110:443: i/o timeout
Warning Failed 43s kubelet Error: ErrImagePull
Normal BackOff 42s kubelet Back-off pulling image "10.43.63.110/default/camel-k-kit-cjk67hssf35s73eekml0@sha256:ec92a11a157dc90e052973053a234ecc9f5f3b1
41a33f31ebc72eb0bd692b215"
Warning Failed 42s kubelet Error: ImagePullBackOff
Normal Pulling 28s (x2 over 103s) kubelet Pulling image "10.43.63.110/default/camel-k-kit-cjk67hssf35s73eekml0@sha256:ec92a11a157dc90e052973053a234ecc9f5f3b141a33f31e
bc72eb0bd692b215"
```
--
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-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Error running integration with private registry [camel-k]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #4694:
URL: https://github.com/apache/camel-k/issues/4694#issuecomment-1841865267
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!
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #4694: Error running integration with private registry
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4694:
URL: https://github.com/apache/camel-k/issues/4694#issuecomment-1698694647
Yes, this seems to be a cluster problem, ie, the kubectl tries to pull securely from an insecure registry. I think you need to configure the cluster to make sure the registry http are not redirected to https. I think this GH issue may help: https://github.com/rancher/rke2/issues/2317
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Error running integration with private registry [camel-k]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #4694: Error running integration with private registry
URL: https://github.com/apache/camel-k/issues/4694
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org