kwok node stuck in a NotReady state after using kustomize to deploy kwok

[network-charles]

How to use it?

• kwok
• kwokctl --runtime=docker (default runtime)
• kwokctl --runtime=binary
• kwokctl --runtime=nerdctl
• kwokctl --runtime=kind

What happened?

When deploying kwok using kustomize, it deploys successfully, but when you create a new fake node, it is stuck in a NotReady state.

I believe that the required "default custom resources (CRs) of stages" is missing. When I install this myself, it worked.

My suggested fix is to include stage to the kustomize definition.

resources:
- ../stage

Let me know what you think, @wzshiming.

What did you expect to happen?

I expected the node to be in a ready state.

kwok-node-1          Ready    agent           18s     fake

How can we reproduce it (as minimally and precisely as possible)?

1. Deploy kwok using kustomize
2. Create a fake node

Anything else we need to know?

No response

Kwok version

$ kwok --version
# Its not showing an output on my mac. I installed kwok using homebrew

$ kwokctl --version
kwokctl version v0.6.1 go1.22.3 (darwin/amd64)

OS version

# On Darwin:
$ uname -a
Darwin macs-MacBook-Pro.local 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64

[wzshiming]

In fact, this is a limitation of apiserver, CRD and its CR cannot be applied at the same time, they have to be separated twice.

[network-charles]

Ok, so does it mean that the kustomize section in the docs is missing a critical step about applying the CR?

[wzshiming]

Yes, it is true that this section has not been maintained for a long time, and has been stuck in a state before CRD configuration kwok was available.

[network-charles]

Alright, I will submit a PR.