Open Sindica opened 3 years ago
This is for system tenant. I will test in tenant arktos and zeta and see whether it happens again.
I ran load test locally with tenant arktos and zeta, Both were able to schedule pods onto both RPs. Suspect this is a system tenant only issue. As we don't have a concrete plan to deal with system tenant objects, lowering the priority.
What happened: In local scale out test, perf test pods sometimes can only being created in one RP: Failed RP kubelet log:
Successful RP kubelet log:
What you expected to happen: Both RPs should be able to get secret and create running pods.
How to reproduce it (as minimally and precisely as possible): ./hack/arktos-up-scale-out-poc.sh
Anything else we need to know?: The following file might need additional code changes: . pkg/controller/volume/scheduling/scheduler_binder.go:477 . pkg/kubelet/kubelet.go . pkg/scheduler/factory/factory.go (Refactor AggregateNodeLister) . pkg/scheduler/nodeinfo/util.go (// TODO - set rpId in NodeInfo) . pkg/scheduler/scheduler.go (sched.config.NodeListers[0])
Environment:
kubectl version
):cat /etc/os-release
):uname -a
):