Initial commit for Pod Affinity Anti Affinity Scheduling workload#92
Initial commit for Pod Affinity Anti Affinity Scheduling workload#92wabouhamad wants to merge 1 commit intoopenshift-scale:masterfrom
Conversation
|
@mffiedler @chaitanyaenr please review |
|
@mffiedler @chaitanyaenr please review, been running these workloads from Jenkins since OCP 4.2 |
| The Pod Affinity Anti Affinity workload playbook is `workloads/pod-affinity.yml` and will run the Pod Affinity Anti Affinity workload on your cluster. | ||
|
|
||
| The first step is to deploy a pod labeled with `security=s1` which the scheduler will deploy on one of the worker nodes in the clusters. | ||
| Pod Affinity Anti Affinity workload's purpose is to validate if the OpenShift cluster can deploy 130 hello-pods with pod affinity to labeled pod, and get deployed on the same worker node. Additionally, this workload will also test deploying 130 additional hello-pods with anti-affinity to the `security=s1` labeled pod, and will be deployed on the other worker nodes. Deployed pods have memory and CPU requests, and goal is to be close 85% CPU capacity after all pods are deployed. |
There was a problem hiding this comment.
Maybe add a pointer to the script and pod spec/template in svt repo since they are being maintained there. This way, we will the location in case we need to modify something. On the other hand, it might be a good idea to bake in the script and pod templates into the workload itself like how we are doing in case of other workloads like nodevertical for example : https://github.com/openshift-scale/workloads/blob/master/workloads/templates/workload-nodevertical-script-cm.yml.j2#L75. This way we will have a clear idea of what workload is doing as well easier to modify it in case we want to change something. Thoughts?
3 participants
Initial commit for the Pod Affinity Anti-Affinity Scheduling workload: