search

vmware-tanzu / k-bench

Workload Benchmark for Kubernetes
Other
391 stars 56 forks source link

0 "NumReplicas" in Deployments causes the wait to check until benchmark timeout #24

Open zorro786 opened 3 years ago

zorro786 commented 3 years ago

If a "Deployments" workload is defined without any "NumReplicas", the benchmark spins until timeout. Example workload:

  "BlockingLevel": "operation",
  "Timeout": 540000,
  "CheckingInterval": 3000,
  "Cleanup": false,
  "Operations": [
    {
      "Deployments": {
        "Actions": [
          {
            "Act": "CREATE",
            "Spec": {
              "ImagePullPolicy": "IfNotPresent",
              "Image": "k8s.gcr.io/pause:3.1"
            }
          },
          {
            "Act": "DELETE"
          }
        ],
        "SleepTimes": [
          30000
        ],
        "Count": 1
      }
    }
  ]
}

I would suggest to default it to 1 as it defaults in K8s.