[GitHub] [camel-k] amitsadaphule edited a comment on issue #1869: './kamel run xxx' and 'make test-integration' pod failures on Ubuntu 16.04 (with minikube)
amitsadaphule edited a comment on issue #1869: URL: https://github.com/apache/camel-k/issues/1869#issuecomment-766811960 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] amitsadaphule edited a comment on issue #1869: './kamel run xxx' and 'make test-integration' pod failures on Ubuntu 16.04 (with minikube)
amitsadaphule edited a comment on issue #1869: URL: https://github.com/apache/camel-k/issues/1869#issuecomment-766875678 Right, tried stopping, deleting (+ rm -rf ~/.minikube ~/.kube) and re-creating with `minikube start --insecure-registry "10.0.0.0/24"`, to no avail. Something very strange is going on there. Thanks for the pointer! I'll debug in that direction. :) 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] amitsadaphule edited a comment on issue #1869: './kamel run xxx' and 'make test-integration' pod failures on Ubuntu 16.04 (with minikube)
amitsadaphule edited a comment on issue #1869: URL: https://github.com/apache/camel-k/issues/1869#issuecomment-766811960 Thanks @astefanutti ! Got your comment from the other issue earlier :) Unfortunately, I've not been able to get that to work yet. Tried passing the flag to the minikube start command `minikube start --driver=none --insecure-registry "10.0.0.0/24"`, but that does not enable the registry pods which causes the `./kamel install` command to fail with error: ``` # ./kamel install Error: cannot find automatically a registry where to push images ``` So, I executed `minikube addons enable registry` which started the registry and registry proxy pods, but resulted in the same error as before `Unknown desc = Error response from daemon: Get https:///v2/: dial tcp :443: connect: connection refused`. Trying to figure out whether the registry addon and the `--insecure-registry` flag passed to `minikube start` are even related and if so, why the log still shows `https`. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] amitsadaphule edited a comment on issue #1869: './kamel run xxx' and 'make test-integration' pod failures on Ubuntu 16.04 (with minikube)
amitsadaphule edited a comment on issue #1869: URL: https://github.com/apache/camel-k/issues/1869#issuecomment-766811960 Thanks @astefanutti ! Got your comment from the other issue earlier :) Unfortunately, I've not been able to get that to work yet. Tried passing the flag to the minikube start command `minikube start --driver=none --insecure-registry "10.0.0.0/24"`, but that does not enable the registry pods which cases the `./kamel install` command to fail with error: ``` # ./kamel install Error: cannot find automatically a registry where to push images ``` So, I executed `minikube addons enable registry` which started the registry and registry proxy pods, but resulted in the same error as before `Unknown desc = Error response from daemon: Get https:///v2/: dial tcp :443: connect: connection refused`. Trying to figure out whether the registry addon and the `--insecure-registry` flag passed to `minikube start` are even related and if so, why the log still shows `https`. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] amitsadaphule edited a comment on issue #1869: './kamel run xxx' and 'make test-integration' pod failures on Ubuntu 16.04 (with minikube)
amitsadaphule edited a comment on issue #1869: URL: https://github.com/apache/camel-k/issues/1869#issuecomment-765450861 Same issue even after deleting ik, it and re-executing `./kamel run examples/Sample.java`. ``` # kubectl get all -n default NAMEREADY STATUS RESTARTS AGE pod/camel-k-operator-57bbcbd6dc-j5kcv 1/1 Running0 4h28m pod/sample-95d958b69-z556d 0/1 ImagePullBackOff 0 55s NAME TYPECLUSTER-IP EXTERNAL-IP PORT(S) AGE service/kubernetes ClusterIP 10.96.0.1443/TCP 10d NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/camel-k-operator 1/1 11 4h28m deployment.apps/sample 0/1 10 56s NAME DESIRED CURRENT READY AGE replicaset.apps/camel-k-operator-57bbcbd6dc 1 1 1 4h28m replicaset.apps/sample-95d958b69 1 1 0 56s ``` ``` # kubectl get ik,it -A NAMESPACE NAME PHASE TYPE IMAGE default integrationkit.camel.apache.org/kit-c05e6g5f57dq9p35q41g Ready platform 10.103.184.236/default/camel-k-kit-c05e6g5f57dq9p35q41g@sha256:bb486d97a46e7d45e55497c99d01d869bfb1c71023220dda2c7d1343ed6bc200 NAMESPACE NAME PHASE KIT REPLICAS default integration.camel.apache.org/sample Running kit-c05e6g5f57dq9p35q41g 1 ``` ``` # kubectl describe pod sample-95d958b69-z556d -n default ... ... Events: Type Reason Age From Message -- --- Normal Scheduled 2m22sdefault-scheduler Successfully assigned default/sample-95d958b69-z556d to p006vm87 Normal Pulling55s (x4 over 2m18s) kubeletPulling image "10.103.184.236/default/camel-k-kit-c05e6g5f57dq9p35q41g@sha256:bb486d97a46e7d45e55497c99d01d869bfb1c71023220dda2c7d1343ed6bc200" Warning Failed 55s (x4 over 2m18s) kubeletFailed to pull image "10.103.184.236/default/camel-k-kit-c05e6g5f57dq9p35q41g@sha256:bb486d97a46e7d45e55497c99d01d869bfb1c71023220dda2c7d1343ed6bc200": rpc error: code = Unknown desc = Error response from daemon: Get https://10.103.184.236/v2/: dial tcp 10.103.184.236:443: connect: connection refused Warning Failed 55s (x4 over 2m18s) kubeletError: ErrImagePull Normal BackOff44s (x6 over 2m17s) kubeletBack-off pulling image "10.103.184.236/default/camel-k-kit-c05e6g5f57dq9p35q41g@sha256:bb486d97a46e7d45e55497c99d01d869bfb1c71023220dda2c7d1343ed6bc200" Warning Failed 29s (x7 over 2m17s) kubeletError: ImagePullBackOff ``` Maybe something is wrong with the registry setup itself? Is there a different way to setup the local registry for minikube instead of `minikube addons enable registry` that is known to be working for camel-k? 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] amitsadaphule edited a comment on issue #1869: './kamel run xxx' and 'make test-integration' pod failures on Ubuntu 16.04 (with minikube)
amitsadaphule edited a comment on issue #1869: URL: https://github.com/apache/camel-k/issues/1869#issuecomment-765442414 @astefanutti sorry about the mixed up logs. The one from `kubectl get ip camel-k -o yaml` that I posted above is from a different VM altogether. And the pod description there matches the IP: ``` Events: Type Reason Age From Message -- --- Normal BackOff 9m38s (x1055 over 4h9m) kubelet Back-off pulling image "10.103.184.236/default/camel-k-kit-c03kvrjdiqnieco98l2g@sha256:5938d9b4fc02824a622db92ab3650685a0e53c6faa8c82d2e14a72442e00ab5e" Warning Failed 4m40s (x1077 over 4h9m) kubelet Error: ImagePullBackOff ``` I'll still try executing `kubectl delete ik,it --all` to delete the following resources and re-creating the build. ``` # kubectl get ik,it -A NAMESPACE NAME PHASE TYPE IMAGE default integrationkit.camel.apache.org/kit-c03kvrjdiqnieco98l2g Ready platform 10.103.184.236/default/camel-k-kit-c03kvrjdiqnieco98l2g@sha256:5938d9b4fc02824a622db92ab3650685a0e53c6faa8c82d2e14a72442e00ab5e NAMESPACE NAME PHASE KIT REPLICAS default integration.camel.apache.org/sample Running kit-c03kvrjdiqnieco98l2g 1 ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] amitsadaphule edited a comment on issue #1869: './kamel run xxx' and 'make test-integration' pod failures on Ubuntu 16.04 (with minikube)
amitsadaphule edited a comment on issue #1869:
URL: https://github.com/apache/camel-k/issues/1869#issuecomment-765379303
Thanks for the reply @astefanutti ! I'm using minikube and here's how I
setup the registry:
1. Built `gcr.io/google_containers/kube-registry-proxy:0.4` image from
source https://github.com/povilasv/kube-registry-proxy.git
2. Built `registry` binary from source
https://github.com/docker/distribution-library-image.git
3. Built `registry.hub.docker.com/library/registry:2.7.1` image from source
https://github.com/docker/distribution-library-image.git by copying the
`registry` binary built in step #2 to `distribution-library-image` directory
4. Executed `minikube addons enable registry`
Post that I was able to see the registry pods coming up. Here's the pods
status post kamel install/run:
```
# kubectl get pods -A
NAMESPACE NAMEREADY STATUS
RESTARTS AGE
default camel-k-operator-57bbcbd6dc-j5kcv 1/1 Running
0 154m
default sample-5bc495b9cb-rbbzm 0/1 ImagePullBackOff
0 151m
kube-system coredns-f9fd979d6-7678j 1/1 Running
6 10d
kube-system etcd-p006vm87 1/1 Running
12 10d
kube-system kube-apiserver-p006vm87 1/1 Running
14 10d
kube-system kube-controller-manager-p006vm871/1 Running
9 10d
kube-system kube-proxy-q7pfw1/1 Running
6 10d
kube-system kube-scheduler-p006vm87 1/1 Running
6 10d
kube-system registry-8d28l 1/1 Running
3 2d15h
kube-system registry-proxy-q26fb1/1 Running
3 2d15h
```
Also, here's the output of `kubectl get ip camel-k -o yaml`
```
# kubectl get ip camel-k -o yaml
apiVersion: camel.apache.org/v1
kind: IntegrationPlatform
metadata:
creationTimestamp: "2021-01-22T10:11:08Z"
generation: 1
labels:
app: camel-k
managedFields:
- apiVersion: camel.apache.org/v1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:labels:
.: {}
f:app: {}
f:spec:
.: {}
f:build:
.: {}
f:maven:
.: {}
f:settings: {}
f:publishStrategy: {}
f:registry:
.: {}
f:address: {}
f:insecure: {}
f:kamelet: {}
f:resources: {}
f:status:
.: {}
f:build:
.: {}
f:baseImage: {}
f:buildStrategy: {}
f:maven:
.: {}
f:localRepository: {}
f:settings:
.: {}
f:configMapKeyRef:
.: {}
f:key: {}
f:name: {}
f:timeout: {}
f:persistentVolumeClaim: {}
f:publishStrategy: {}
f:registry:
.: {}
f:address: {}
f:insecure: {}
f:runtimeVersion: {}
f:timeout: {}
f:cluster: {}
f:kamelet:
.: {}
f:repositories: {}
f:phase: {}
f:resources: {}
f:version: {}
manager: kamel
operation: Update
time: "2021-01-22T10:11:17Z"
name: camel-k
namespace: default
resourceVersion: "703539"
selfLink:
/apis/camel.apache.org/v1/namespaces/default/integrationplatforms/camel-k
uid: 74046037-87a3-4c9f-bd12-40af390713c7
spec:
build:
maven:
settings: {}
publishStrategy: Spectrum
registry:
address: 10.103.184.236
insecure: true
kamelet: {}
resources: {}
status:
build:
baseImage: adoptopenjdk/openjdk11:ubi
buildStrategy: routine
maven:
localRepository: /tmp/artifacts/m2
settings:
configMapKeyRef:
key: settings.xml
name: camel-k-maven-settings
timeout: 3m45s
persistentVolumeClaim: camel-k
publishStrategy: Spectrum
registry:
address: 10.103.184.236
insecure: true
runtimeVersion: 1.6.0
timeout: 5m0s
cluster: Kubernetes
kamelet:
repositories:
- uri: github:apache/camel-kamelets
phase: Ready
version: 1.3.0
```
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.
For queries about this service, please
