[GitHub] [camel-k] ReggieCarey commented on issue #1376: MicroK8s' built-in registry declared for the Camel K installation, but not used - integration installations fail
ReggieCarey commented on issue #1376: URL: https://github.com/apache/camel-k/issues/1376#issuecomment-940643758 I could not get integrations to work. Sent from my iPhone > On Oct 7, 2021, at 21:18, Tadayoshi Sato ***@***.***> wrote: > > > @ReggieCarey What happens if you run some example app with the operator? The original issue is when you run some app on MicroK8s. Thanks. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or unsubscribe. -- 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
[GitHub] [camel-k] ReggieCarey commented on issue #1376: MicroK8s' built-in registry declared for the Camel K installation, but not used - integration installations fail
ReggieCarey commented on issue #1376: URL: https://github.com/apache/camel-k/issues/1376#issuecomment-937998360 I just tried to install on MicroK8s and it complained initially. However I attempted the following and it appears to have worked: ``` $ kamel install --registry-insecure true --registry localhost:32000/v1 OLM is not available in the cluster. Fallback to regular installation. Camel K installed in namespace default $ kubectl get all NAMEREADY STATUSRESTARTS AGE pod/camel-k-operator-7bb969fb8b-t4jqd 1/1 Running 0 108s NAME TYPECLUSTER-IP EXTERNAL-IP PORT(S) AGE service/kubernetes ClusterIP 10.152.183.1 443/TCP 17h NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/camel-k-operator 1/1 11 108s NAME DESIRED CURRENT READY AGE replicaset.apps/camel-k-operator-7bb969fb8b 1 1 1 108s ``` -- 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
[GitHub] [camel-k] ReggieCarey commented on issue #1376: MicroK8s' built-in registry declared for the Camel K installation, but not used - integration installations fail
ReggieCarey commented on issue #1376: URL: https://github.com/apache/camel-k/issues/1376#issuecomment-937998360 I just tried to install on MicroK8s and it complained initially. However I attempted the following and it appears to have worked: ``` $ kamel install --registry-insecure true --registry localhost:32000/v1 OLM is not available in the cluster. Fallback to regular installation. Camel K installed in namespace default $ kubectl get all NAMEREADY STATUSRESTARTS AGE pod/camel-k-operator-7bb969fb8b-t4jqd 1/1 Running 0 108s NAME TYPECLUSTER-IP EXTERNAL-IP PORT(S) AGE service/kubernetes ClusterIP 10.152.183.1 443/TCP 17h NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/camel-k-operator 1/1 11 108s NAME DESIRED CURRENT READY AGE replicaset.apps/camel-k-operator-7bb969fb8b 1 1 1 108s ``` -- 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
