You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2024/08/16 17:12:00 UTC
[jira] [Commented] (YUNIKORN-1117) Use k8s Nodes condition to determine health of the node
[ https://issues.apache.org/jira/browse/YUNIKORN-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874329#comment-17874329 ]
Craig Condit commented on YUNIKORN-1117:
----------------------------------------
I think we should stay out of this entirely. The concept of whether a node is healthy or not is far more complex than what taints exist. It's even somewhat environment-dependent. This is the job of the API server, not the scheduler.
> 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: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org