kwok
kwok copied to clipboard
kubernetes-sigs
Kwok Stage Configs are not in expectation
How to use it?
- [ ] kwok
- [X] kwokctl --runtime=docker (default runtime)
- [ ] kwokctl --runtime=binary
- [ ] kwokctl --runtime=nerdctl
- [ ] kwokctl --runtime=kind
What happened?
Just applied the general folder (https://github.com/kubernetes-sigs/kwok/tree/main/kustomize/stage/pod/general) stage configs but caused the pod status from running -> containerCreating -> running
What did you expect to happen?
I hope the status does not change to containerCreating after running.
How can we reproduce it (as minimally and precisely as possible)?
I just the kwok 4.0.0 and apply the general stages config (https://github.com/kubernetes-sigs/kwok/tree/main/kustomize/stage/pod/general)
Anything else we need to know?
No response
Kwok version
$ kwok --version
kwok version v0.4.0 go1.20.7 (linux/amd64)
$ kwokctl --version
kwokctl version v0.4.0 go1.21.0 (linux/amd64)
OS version
On Darwin:
$ uname -a Linux n199-192-082 5.4.143.bsk.8-amd64 #5.4.143.bsk.8 SMP Debian 5.4.143.bsk.8 Wed Jul 20 08:43:36 UTC x86_64 GNU/Linux
On Windows:
C:> wmic os get Caption, Version, BuildNumber, OSArchitecture
paste output here
</details>
Thank you for your feedback. Although this is still experimental, there is no test coverage that looks like the expected behavior changes.
I plan to refine it in this release.
Thank you for your feedback. Although this is still experimental, there is no test coverage that looks like the expected behavior changes.
I plan to refine it in this release.
After I upgraded the Kwok version to v0.5.1, it looks to work well. I saw that there were some PRs to refine the dequeue in playing the pod stages. Not sure if it has already been fixed.
This has been fixed, feel free to open it if there are still issues
/close
@wzshiming: Closing this issue.
In response to this:
This has been fixed, feel free to open it if there are still issues
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
