logos-storage/logos-storage-nim-cs-dist-tests
1
0
Fork 0
mirror of https://github.com/logos-storage/logos-storage-nim-cs-dist-tests.git synced 2026-07-10 17:19:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: do not use anti affinity to enforce pod spread when running tests locally

Browse Source 
Locally, there is only one node in the cluster, so the first pod would schedule on the node, then each subsequent pod would fail to schedule.

This fix ensures that there is no spread affinity when the runner location is ExternalToCluster (local).
This commit is contained in:
E M 2026-06-25 13:47:15 +10:00
parent 6bb176261f
commit beb16f33d1
No known key found for this signature in database
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Framework/KubernetesWorkflow/K8sController.cs
View File

@ -423,8 +423,16 @@ namespace KubernetesWorkflow
}).ToList();
}
private V1Affinity CreateSpreadAffinity()
private V1Affinity? CreateSpreadAffinity()
{
// The required pod anti-affinity forces every pod in the namespace onto a
// distinct node. That only makes sense on the multi-node GKE release cluster
// (InternalToCluster). When running locally (ExternalToCluster, e.g. single-node
// Docker Desktop) it would leave all but the first pod stuck Pending forever, so
// we omit the affinity entirely in that case.
if (RunnerLocationUtils.GetRunnerLocation() == RunnerLocation.ExternalToCluster)
return null;
return new V1Affinity
{
PodAntiAffinity = new V1PodAntiAffinity