We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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 -
The text was updated successfully, but these errors were encountered:
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.
10.100.191.95
Sorry, something went wrong.
not a camel-k issue
No branches or pull requests
When running a route like
The knative service fails to deploy and describing the knative service shows this error :
The text was updated successfully, but these errors were encountered: