[
https://issues.apache.org/jira/browse/YUNIKORN-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458841#comment-17458841
]
Craig Condit commented on YUNIKORN-974:
---------------------------------------
Given the tagging issues discovered with 0.12.0 and the subsequent mailing list
discussion, I'd propose that we retag all components with v0.12.1 (after go mod
tidy on all dependencies) for the release, and delete all the github v0.12.0
tags to avoid confusion, since those are now tainted for at least the core,
release, and shim repos.
> Release blockers for 0.12
> -------------------------
>
> Key: YUNIKORN-974
> URL: https://issues.apache.org/jira/browse/YUNIKORN-974
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Craig Condit
> Assignee: Chaoran Yu
> Priority: Blocker
> Labels: pull-request-available
>
> Upon testing the 0.12.0 release candidate from Dec 9, I ran into the
> following issues:
> - Verify_Non_Matching_NodeSelector_Respected e2e test times out (cause
> unknown)
> - Admission controller logs several TLS cert errors (seems to be caused by
> the v1beta -> v1 CSR changes)
> - Scheduler shuts down after 10 minutes (possibly related to the health
> checker changes)
> I think we should consider each of these release blockers and re-release 0.12
> once they are fixed.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
