Remove YuniKorn application CRD should be fine, I don't think we ever
reached the GA for this feature, and I don't think anyone is using it.
The operator plugin, however, I don't think we should remove, for example
the Spark CRD plugin
Craig Condit created YUNIKORN-1888:
--
Summary: Allow allocations to be added to existing nodes
Key: YUNIKORN-1888
URL: https://issues.apache.org/jira/browse/YUNIKORN-1888
Project: Apache YuniKorn
I’m definitely in favor of removing the CRD, and sooner rather than later. It
negatively impacts some of the ongoing refactoring tasks as it influences the
recovery pipeline. I think given the alpha state of the CRD, if there are no
objections we can remove this in 1.4.0.
Craig
> On Jul 27,
Craig Condit created YUNIKORN-1887:
--
Summary: SI: Add tag for application recovered flag
Key: YUNIKORN-1887
URL: https://issues.apache.org/jira/browse/YUNIKORN-1887
Project: Apache YuniKorn
Peter Bacsko created YUNIKORN-1886:
--
Summary: Optimize scheduling cycle if there's no placeholder
allocation or reservation
Key: YUNIKORN-1886
URL: https://issues.apache.org/jira/browse/YUNIKORN-1886
[
https://issues.apache.org/jira/browse/YUNIKORN-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko resolved YUNIKORN-1881.
Fix Version/s: 1.4.0
Resolution: Fixed
Merged to master.
> Improve the
[
https://issues.apache.org/jira/browse/YUNIKORN-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikandan R resolved YUNIKORN-1835.
Resolution: Fixed
> User belong to zero or multiple groups
>
