Open shaardie opened 6 months ago
Sounds useful.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
@shaardie sounds like useful indeed. Would you still be interested to implement it?
/remove-lifecycle stale
+1
I would like to implement it, but unfortunately there is a big leap between main and the version we are currently using (0.9). Especially, because there seems to be a new controller.
As a quick fix, at least for us, I implemented this on the release-0.9 branch.
As soon as the dust settles and we can switch to a version near the current main, I would try to implement it there again.
/kind feature
Describe the solution you'd like
I think the teardown process of VMs would benefit from an option to shutdown the OpenStack Machine before deleting it. This way it would be possible to benefit from teardown process in the VMs itself. Myself encountered this problem with NVIDIA licensees, which are
borrowed
on VM startup, but never properly released, because the Service on the VM was never stopped properly and therefore had no chance of releasing the license.I think on way of implementing this, would be to add something like an
waitForShutdown
to the OpenStackMachine CRD. It could be defaulted to0s
to keep the old behavior and it would be a single configuration to have the possibility to let the VM properly shutdown and have a timeout for the shutdown, so that it does not hang forever in an error case.If you are interested in such a feature, I would be happy to help implementing it.