-
Notifications
You must be signed in to change notification settings - Fork 347
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
java.lang.ClassNotFoundException: io.quarkus.bootstrap.runner.QuarkusEntryPoint after k8s node update #3122
Comments
@squakez @astefanutti we did a lot of examination, with no success at all. Do you have an idea where we could search for the root cause of this behavior? Camel Spring-Boot routes are running well in sam k8s Cluster as other Java programs. The nodes are still running on cgroup v1 level. What can we check further? Many thanks for any hint in this case. |
We did proof that Camel-K and the Integration are running on AWS cluster 1.21 but not on 1.22. So again .. any help to debug the issue would help. |
The only thing comes to my mind, is we updated the Kubernetes API to version 1.21.4 and it's in 1.8.2, so there wasn't any kind of work on 1.22.x |
@oscerd I did try Camel-K on GKE with Node version Any further hints where to find additional debug information? k8s logs may be? |
Finally we did find the reason, that in our (managed) cluster environment the RBAC has been changed so that the Operator wasn't allowed to load dependencies further. For an improvement here it would be hepful to see such information within the Operator logs. |
@catshout What was changed in the RBAC? Depending on the info, we might be able to find a way to improve the operator so that it can show some helpful message in the log. |
This issue has been automatically marked as stale due to 90 days of inactivity. |
Hi everybody.
Our k8s cluster has been updated yesterday to v1.22.6. After the update the Camel-K routes don't work anymore. We did create a sample route like
and did get the following error
Any ideas what might be the reason for and how to fix it?
The text was updated successfully, but these errors were encountered: