2 min read
With Argo workflows you can automate tasks like building and pushing Docker images on a regular schedule: You just need to use the CronWorkflow to call any WorkflowTemplate.
In this example we are going to set up an Argo CronWorkflow that runs every hour, clones a Git repository, builds a Docker image using Kaniko, and pushes it to a Docker registry.
06/11/2024
Read more...3 min read
When we need to have a stateful application running on Kubernetes, we might need to use a StatefulSet. With a StatefulSet, we can manage stateful applications where each pod needs a stable, unique network identity and storage that persists across pod rescheduling. Unlike Deployments, which focus on maintaining a specified number of replicas, StatefulSets ensure each pod is given a unique ordinal index and retains the same identity throughout its lifecycle. If a pod is deleted or a node fails, the replacement pod will maintain the same identity and storage.
04/11/2024
Read more...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...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...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 artifacts
section in the WorkflowTemplate. This allows us to pass data between steps in a Workflow.
29/10/2024
Read more...