-
Notifications
You must be signed in to change notification settings - Fork 221
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
Krustlet on Kind shows some weird behavior #712
Comments
The original issues I face seems to be from some minor inconsistencies in docs that I probably misunderstood. I created a PR to the docs projects to propose some updates krustlet/krustlet-docs#20 |
deepu105
changed the title
Error running WASM workloads with Krustlet on kinD
WASM workloads with Krustlet on kinD is in Error status
Jan 13, 2022
deepu105
changed the title
WASM workloads with Krustlet on kinD is in Error status
Krustlet on Kind shows some weird behavior
Jan 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I followed the quick start for kinD and installed krustlet. During the install step I got some errors on the console and when trying to deploy the
hello-wasm
sample I get errorRunning the below command gives some error on the console but I could see Krustlet as a node but the Roles field was empty
Console out, I believe this comes from kindnet pod being scheduled on krustlet and failing since its not a wasm workload
Nodes
Then I tried deploying a pod
The pod status is
ExistCode:0
which I assume is expected for this sample. If I look at the logs I can see the output is printed. And when using a sample that runs something in loop I can see running status. SO I guess that's all normal.But on
kube-system
namespace Thekindnet-*
pod gets scheduled on the krustlet node and the already existing pod on the default node goes into aCrashLoopBackOff
. Not sure if this is an issue or something expectedAlso on the krustlet-wasi logs I see this repeatedly, I believe from trying to run the kindnet docker image on krustlet
kind v0.11.1 go1.16.5 linux/amd64
krustlet 1.0.0-alpha.1
OS : Fedora 35
Will be happy to provide more info if needed
The text was updated successfully, but these errors were encountered: