-
Notifications
You must be signed in to change notification settings - Fork 30
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
akka.actor.ActorInitializationException when trying to send API requests #70
Comments
Hi @razzu , thank you for following up on that matter. Can you try using http instead of https ? [INFO] [07/29/2021 09:28:18.485] [main] [skuber.api] Using following context for connecting to Kubernetes cluster: Context(Cluster(v1,https://192.168.0.1:443,false,So By the way, I tested with Kubernetes cluster and the connection is established. |
Thanks for the input! Unfortunately I'm not sure how to test that or whether I can actually change this behaviour. The app runs on a pod inside a managed K8s cluster and I can't really modify anything related to the Kubernetes installation. I'm letting Skuber do the Have you also tested this running inside a cluster? Or just from the outside? |
@razzu |
The invite doesn't seem to be working for me. |
@razzu |
I am running into the same issue. Did anything come out of the discord conversation about how you resolved this? |
@hagay3 and @razzu I think this issue is with KubernetesClientImpl code where engine.setUseClientMode(true) is not being set.
|
@brycechesternewman Please let me know if it resolves the issue |
2.7.3 resolved this issue. Thanks for the quick turn around on the merge. |
Hi,
This is a follow-up to a previous issue (#59).
After updating skuber to 2.7.2, all API requests sent by Skuber fail with an Akka initialization exception. I've tried this inside a Kubernetes cluster, with default configuration settings. Full log of my dummy app:
Note that this works if I downgrade Skuber to 2.7.0.
My
build.sbt
file is quite simple, only Skuber and a few extra things:The actual code doesn't do much, just tries to retrieve a ConfigMap and then start a watch:
Note that it doesn't even create the Future (so it doesn't reach the
Failure
branch inonComplete
.Let me know if there's anything else I can try! I've run out of ideas.
Thanks!
The text was updated successfully, but these errors were encountered: