optional priorityClasses for score / mcore jobs about harvester HOT 3 CLOSED

Thanks @rptaylor . I deployed the code changes and seems OK to me.

• a MCORE worker with priority class

[harvester]# kubectl describe pods grid-job-9305688-zt9cz
Name:                 grid-job-9305688-zt9cz
Namespace:            harvester
Priority:             500
Priority Class Name:  uber-user-significant
Node: ...

• a SCORE worker without priority class

[harvester]# kubectl describe pods grid-job-9305686-vrvcx
Name:         grid-job-9305686-vrvcx
Namespace:    harvester
Priority:     0
Node:  ...

Let me know if you need any adjustment.

from harvester.

hi @rptaylor,

In principle it's implemented, but for testing it would help me if you can define a priorityClass in your TEST cluster and you let me know the name. Is that possible?

The CRIC parameters will be:

k8s.scheduler.priorityClassName.score
k8s.scheduler.priorityClassName.score_himem
k8s.scheduler.priorityClassName.mcore
k8s.scheduler.priorityClassName.mcore_himem

Regards,
Fernando

from harvester.

Hi @fbarreir , certainly, I made a priorityClass called uber-user-significant on the dev cluster (edit: renamed). Thanks! I'll test it.

from harvester.