-
Notifications
You must be signed in to change notification settings - Fork 352
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
Report error when any registry problem happen #4272
Comments
Thanks for reporting. Yes, I think we need to expose some error details (at least some clear log mentioning the registry is failing). I'm editing the title of this issue to better capture the requirement and label as a feature for future development. If you're willing to contribute to the issue, feel free to ask any development advice. |
It turned out there was an unintentionally applied networkpolicy blocking all requests by default, including those for docker hub and the external container registry. Thus, the operator was not able to build the integration. |
This issue has been automatically marked as stale due to 90 days of inactivity. |
Description
I'm facing an issue when trying to use camel-k on an Azure Kubernetes Cluster with GitLab as container registry.
When I create an integration from a file, the created resource stays in phase "Building Kit" for a while until it fails (phase "Error").
There's no pod created for the integration. I was able to run the same integration on a minikube cluster with internal registry.
There are multiple potential reasons for that behavior, including a misconfiguration of the container registry.
However, troubleshooting is difficult because there aren't many logs created by either the operator or the integration itself.
I couldn't find a way to extend the logging.
Steps to reproduce
It's not possible to mention all steps in detail because of the specific setup. The most important steps I went through are the following:
kamel install --namespace sample-namespace --registry <internal-registry> --organization <internal-organization> --registry-secret <registry-token> --build-publish-strategy=Spectrum --force
kubectl apply -f sample-route.yaml
This is the only reasonably meaningful error message I could finde:
"errorVerbose":"unable to find integration container: sample-route\nerror during trait customization"
The full logs generated by the integration and the operator are listed below.
Does anyone have any idea either why the build fails or how to extend the logging?
Of course I don't expect the underlying problem to be solved by this issue.
Rather, I am looking for a way to get more meaningful logs.
Logs from the integration:
Logs from the operator:
The text was updated successfully, but these errors were encountered: