How do I stop an Argo workflow when the script exits?

To stop an Argo workflow when the script exits, you can implement one or more of the following strategies:

1. **Using Exit Handlers:** Argo Workflows supports exit handlers that can trigger specific actions when a workflow completes, whether it succeeds or fails. You can define an exit handler to clean up resources or perform other termination tasks.

2. **Workflow Timeouts:** You can set a timeout for your workflow to ensure it doesn't run indefinitely. If the script exits unexpectedly, the workflow will be automatically terminated after the specified duration.

3. **Conditional Steps:** Implement conditional logic within your workflow to check the status of the script execution. If the script exits, subsequent steps can be skipped, effectively stopping the workflow.

4. **Signal Handling in Scripts:** Modify your script to send a termination signal or update a status flag upon exiting. The workflow can monitor this signal or flag to decide whether to continue or stop.

5. **Kubernetes Integration:** Since Argo Workflows run on Kubernetes, you can leverage Kubernetes' native features to manage workflow lifecycles. For example, you can use Kubernetes Jobs with appropriate restart policies to handle script exits.

**Example: Using Exit Handlers**

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: stop-workflow-
spec:
  entrypoint: main
  templates:
  - name: main
    steps:
    - - name: run-script
        template: script
  - name: script
    container:
      image: your-script-image
      command: ["sh", "-c", "your-script.sh"]
  exitHandlers:
  - template: cleanup
  - name: cleanup
    container:
      image: alpine:latest
      command: ["sh", "-c", "echo Cleaning up resources..."]
                        

In this example, the `cleanup` template will be executed when the workflow exits, ensuring that any necessary cleanup is performed.

Learn more about this