-
Argo Workflows: Using the exit handler
2 min read
An exit handler is a template that always executes at the end of a workflow (regardless of whether it completed successfully or returned an error). You can use this run any action, for example: to send notifications after a workflow runs, post the status of the workflow to a webhook, clean up artifacts or run another workflow.
01/11/2024
Read more... -
Argo Workflows: How to actually run a task in a Workflow
5 min read
When we are creating a Workflow in Argo Workflows, we need to define the tasks that we need to do. These tasks are defined using templates: They are the building blocks of a Workflow, defining how each task will be executed.
31/10/2024
Read more... -
Golang: Using the Garbage Collection tracing
3 min read
Go is a garbage-collected language: It will reclaim any unused memory. This automation can sometimes introduce performance challenges. We can use the GODEBUG environment variable to provide insights into specific internal operations of the Go runtime, such as scheduling, memory allocation, and garbage collection.
30/10/2024
Read more... -
Argo Workflows: Passing artifacts in a multi-step WorkflowTemplate
3 min read
In a Workflow we'll need to be able to share data between the different steps. To do so we can use the
artifactssection in the WorkflowTemplate. This allows us to pass data between steps in a Workflow.29/10/2024
Read more... -
Argo Workflows: Input Parameters in a WorkflowTemplate
2 min read
Having a WorkflowTemplate with input parameters in Argo Workflows allows you to create reusable templates that can be customized at runtime. This is useful when you want to pass dynamic values to the workflow template when you submit it.
Following the example of the WorkflowTemplate that builds and pushes a Docker image using Kaniko, we are going to update it to use input parameters.
28/10/2024
Read more...