Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Knative minikube service failure #482

Closed
kameshsampath opened this issue Feb 22, 2019 · 2 comments
Closed

Knative minikube service failure #482

kameshsampath opened this issue Feb 22, 2019 · 2 comments

Comments

@kameshsampath
Copy link
Contributor

When running a route like

  .convertBodyTo(String.class)
  .to("log:info");

The knative service fails to deploy and describing the knative service shows this error :

  conditions:
  - lastTransitionTime: "2019-02-22T11:32:40Z"
    message: 'Revision "print-00001" failed with message: "Unable to fetch image \"10.100.191.95/knativetutorial/camel-k-ctx-bhntq7a6pkmls1neqo4g:8281\":
      Get https://10.100.191.95/v2/: dial tcp 10.100.191.95:443: connect: connection
      timed out".'
    reason: RevisionFailed
    severity: Error
    status: "False"
    type: ConfigurationsReady
  -
@kameshsampath
Copy link
Contributor Author

As knative always expect the registry to be v2 we need to tell Knative to skip the local default registry for v2 check

val=$(kubectl -n knative-serving get cm config-controller -oyaml \
  | yq r - data.registriesSkippingTagResolving \
  | awk '{print $1",10.100.191.95"}')
kubectl -n knative-serving get cm config-controller -oyaml \
  | yq w - data.registriesSkippingTagResolving $val \
  | kubectl apply -f - 

Where 10.100.191.95 is the registry address of the minikube, adding this was able to make the service working.

@lburgazzoli
Copy link
Contributor

not a camel-k issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants