Closed dgrove-oss closed 7 months ago
I think it's been fixed already in main with #1746, and should be fixed in v0.6.1 with #1764.
Adding the --feature-gates=VisibilityOnDemand=true
option to the Kueue deployment main container command should work around the issue in the meantime.
I think it's been fixed already in main with #1746, and should be fixed in v0.6.1 with #1764.
Adding the
--feature-gates=VisibilityOnDemand=true
option to the Kueue deployment main container command should work around the issue in the meantime.
Yeah, I believe so, too. @dgrove-oss Could you try to use manifests in the release-0.6 branch if we can avoid this issue?
I tested building from source on the release-0.6 branch (80adb72b) and confirmed that the issue is resolved.
I tested building from source on the release-0.6 branch (80adb72) and confirmed that the issue is resolved.
Thanks for your confirmation! This is just a tip: you could also use the latest release-0.6 image using the following tags without building:
/close
@tenzen-y: Closing this issue.
What happened:
With kueue 0.6.0 deployed on a cluster, deletion of namespaces hangs.
This is a regression from kueue 0.5.3 and from the conditions on the namespace being deleted seems to be related to the visibility changes introduced in kueue 0.6.0.
In more detail, I created a Kubernetes 1.27 cluster running on kind 0.19.
I deployed Kueue 0.6.0 and then created and attempted to delete a namespace. Deletion of the namespace hangs.
What you expected to happen:
I expect the namespace to be deleted successfully.
How to reproduce it (as minimally and precisely as possible): See transcript below:
The
kubectl delete
command hangs and the namespace is stuck in the Terminating state. Details below:Anything else we need to know?:
Environment:
kubectl version
): 1.27.1git describe --tags --dirty --always
): 0.6.0 installed from release manifestcat /etc/os-release
):uname -a
):