mirror of
https://github.com/k3s-io/kubernetes.git
synced 2026-07-28 10:08:23 +00:00
7226a3084e
We want to be sure that the maximum number of pods per claim are actually scheduled concurrently. Previously the test just made sure that they ran eventually. Running 256 pods only works on more than 2 nodes, so network-attached resources have to be used. This is what the increased limit is meant for anyway. Because of the tightened validation of node selectors in 1.32, the E2E test has to use MatchExpressions because they allow listing node names.
56 lines
1.4 KiB
YAML
56 lines
1.4 KiB
YAML
kind: Cluster
|
|
apiVersion: kind.x-k8s.io/v1alpha4
|
|
containerdConfigPatches:
|
|
# Enable CDI as described in
|
|
# https://github.com/container-orchestrated-devices/container-device-interface#containerd-configuration
|
|
- |-
|
|
[plugins."io.containerd.grpc.v1.cri"]
|
|
enable_cdi = true
|
|
nodes:
|
|
- role: control-plane
|
|
kubeadmConfigPatches:
|
|
- |
|
|
kind: ClusterConfiguration
|
|
scheduler:
|
|
extraArgs:
|
|
v: "5"
|
|
vmodule: "allocator=6,dynamicresources=6" # structured/allocator.go, DRA scheduler plugin
|
|
controllerManager:
|
|
extraArgs:
|
|
v: "5"
|
|
apiServer:
|
|
extraArgs:
|
|
runtime-config: "resource.k8s.io/v1beta1=true"
|
|
- |
|
|
kind: InitConfiguration
|
|
nodeRegistration:
|
|
kubeletExtraArgs:
|
|
v: "5"
|
|
- role: worker
|
|
kubeadmConfigPatches:
|
|
- |
|
|
kind: JoinConfiguration
|
|
nodeRegistration:
|
|
kubeletExtraArgs:
|
|
v: "5"
|
|
- role: worker
|
|
kubeadmConfigPatches:
|
|
- |
|
|
kind: JoinConfiguration
|
|
nodeRegistration:
|
|
kubeletExtraArgs:
|
|
v: "5"
|
|
- role: worker
|
|
kubeadmConfigPatches:
|
|
- |
|
|
kind: JoinConfiguration
|
|
nodeRegistration:
|
|
kubeletExtraArgs:
|
|
v: "5"
|
|
# Feature gates must be the last entry in this YAML.
|
|
# Some Prow jobs add more feature gates with
|
|
#
|
|
# --config <(cat test/e2e/dra/kind.yaml; echo " <some feature>: true")
|
|
featureGates:
|
|
DynamicResourceAllocation: true
|