fix scheduler predicates test that may violate DNS label rules

This commit fixes an issue where in clusters which have FQDN as the node names, one of the scheduling predicates tests will fail because it will try and run a pod with a name that violates DNS-1123 rules. As an example, one such pod name could look like "filler-pod-kube-node-0.kubelet.mesos". Signed-off-by: 's avatarPaulo Pires <pjpires@gmail.com>
parent 20a1a647
...@@ -291,7 +291,7 @@ var _ = SIGDescribe("SchedulerPredicates [Serial]", func() { ...@@ -291,7 +291,7 @@ var _ = SIGDescribe("SchedulerPredicates [Serial]", func() {
for nodeName, cpu := range nodeToAllocatableMap { for nodeName, cpu := range nodeToAllocatableMap {
requestedCPU := cpu * 7 / 10 requestedCPU := cpu * 7 / 10
fillerPods = append(fillerPods, createPausePod(f, pausePodConfig{ fillerPods = append(fillerPods, createPausePod(f, pausePodConfig{
Name: "filler-pod-" + nodeName, Name: "filler-pod-" + string(uuid.NewUUID()),
Resources: &v1.ResourceRequirements{ Resources: &v1.ResourceRequirements{
Limits: v1.ResourceList{ Limits: v1.ResourceList{
v1.ResourceCPU: *resource.NewMilliQuantity(requestedCPU, "DecimalSI"), v1.ResourceCPU: *resource.NewMilliQuantity(requestedCPU, "DecimalSI"),
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment