Some Pods not Running after deploy RKE2

[archermask]

hello, this is my first try to deploy RKE2 on my Lab. I use 3 nodes like below:

Is those pods normal if not in "Running" state?
And those pods not match with expected replicas.
I run command kubectl get pod -n kube-system and below is the screenshoot:

[manuelbuil]

Yes. Those pods belong to a job and they completed their task successfully. I recommend you to read the different types of workloads available in Kubernetes: https://kubernetes.io/docs/concepts/workloads/controllers/

[archermask]

oh thankyou. but I have question
why these pods stuck in "Pending" state? Cause in other kubernetes cluster like in cloud, kubernetes in docker desktop, minikube, etc these pods can run.
But only in RKE2 can't run. These pods are components for Veeam Kasten

[manuelbuil]

There could be a lot of reasons. Normally if you use kubectl describe for those pods, it will tell you what's going on. For example, there might be an affinity rule which does not allow a pod to run in the same node as another pod. So the second pod remains "Pending" until a viable node appears.

[archermask]

run kubectl describe -n kasten-io pod/catalog-svc-7c7d58f6c9-77qj9

error message like this:
0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.

[brandond]

Are you sure you have sufficient resources available on your nodes to meet the resource requests of both the pod and the storage provider? What are the inbound volumes and why are the volumes not bound?