[
https://issues.apache.org/jira/browse/YUNIKORN-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit closed YUNIKORN-1117.
----------------------------------
Target Version: (was: 1.6.0)
Resolution: Won't Do
Closing this as it will cause problems. The scheduler's job is not to determine
healthy status of nodes, only to adhere to node taints and pod tolerations
(which we already do). It's not even really a great idea from a performance
tuning perspective, as it's extremely unusual to see more than a few nodes in
an unhealthy state at once.
> Use k8s Nodes condition to determine health of the node
> -------------------------------------------------------
>
> Key: YUNIKORN-1117
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1117
> Project: Apache YuniKorn
> Issue Type: Improvement
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
>
> Among multiple conditions discussed in
> [https://kubernetes.io/docs/concepts/architecture/nodes/#condition], only
> "Ready" has been used. We should use other conditions as well to determine a
> generic {{isNodeHealthy}} factor and eventually passing to core as well.
> Please refer the discussion
> [https://github.com/apache/incubator-yunikorn-k8shim/pull/380#issuecomment-1066328969]
> for more details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
