You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I encountered an issue when using Zarf to deploy a failing application. During the deployment, I used Ctrl-C to interrupt the process, but this did not allow Zarf to clean up the state it put in the cluster. As a result, I am forced to wait for the deployment to fail multiple times before Zarf can properly clean up the failed deployment, which can take a significant amount of time (up to 15 minutes per timeout).
Describe the solution you'd like
I propose implementing a graceful shutdown signal when using Ctrl-C during deployment. This will allow Zarf to clean up the cluster state if the deployment is interrupted. Additionally, if Ctrl-C is used during the graceful shutdown, it should trigger a hard stop like it currently does.
Describe alternatives you've considered
An alternative solution would be to provide a separate command to manually trigger a cleanup of a failed deployment in the cluster. This would allow users to clean up the state without waiting for multiple deployment timeouts. The current zarf package delete command fails to clean up a failed deploy due to some secret not existing that it expects.
Additional context
This improvement would save users time and frustration when dealing with failed deployments in Zarf. By implementing a graceful shutdown signal upon using Ctrl-C, users can have more control over their deployment process and avoid waiting for extended periods due to multiple timeouts.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I encountered an issue when using Zarf to deploy a failing application. During the deployment, I used Ctrl-C to interrupt the process, but this did not allow Zarf to clean up the state it put in the cluster. As a result, I am forced to wait for the deployment to fail multiple times before Zarf can properly clean up the failed deployment, which can take a significant amount of time (up to 15 minutes per timeout).
Describe the solution you'd like
I propose implementing a graceful shutdown signal when using Ctrl-C during deployment. This will allow Zarf to clean up the cluster state if the deployment is interrupted. Additionally, if Ctrl-C is used during the graceful shutdown, it should trigger a hard stop like it currently does.
Describe alternatives you've considered
An alternative solution would be to provide a separate command to manually trigger a cleanup of a failed deployment in the cluster. This would allow users to clean up the state without waiting for multiple deployment timeouts. The current
zarf package delete
command fails to clean up a failed deploy due to some secret not existing that it expects.Additional context
This improvement would save users time and frustration when dealing with failed deployments in Zarf. By implementing a graceful shutdown signal upon using Ctrl-C, users can have more control over their deployment process and avoid waiting for extended periods due to multiple timeouts.
The text was updated successfully, but these errors were encountered: