Workflows
Workflows enable users to create and manage stage components within the development lifecycle, customize deployments based on environments, enforce rules and triggers, and create reusable building blocks for streamlined automation.
Workflows within Kubeark represent a series of tasks that are executed in a sequential order. These tasks can be initiated through different methods, including manual runs, triggers, and cronjobs.
With its low-code approach and event-driven architecture, Workflows enables intelligent responses to events, simplifying automation in the context of Kubernetes. By creating reusable building blocks, Workflows fosters collaboration and accelerates development across teams, providing a solid foundation for efficient and standardized processes.
Kubeark Workflows empower users to seamlessly manage and customize different stage components within the development lifecycle.
With Workflows in Kubeark, you can automate the creation of Template Groups, Templates, and Versions, allowing for streamlined management of your infrastructure as code, ensuring consistent and efficient deployment processes throughout your development lifecycle.
Workflows can be found on the bottom left of your Kubeark platform interface, under the Automation menu.
Workflows within Kubeark represent a series of tasks that are executed in a sequential order. These tasks can be initiated through different methods, including manual runs, triggers, and cronjobs.
- Manual Runs: Users have the ability to manually start a workflow, providing flexibility and control over when and how the tasks are executed. This allows for on-demand execution of specific workflows based on user intervention or decision-making.
- Triggers: Workflows can also be triggered automatically based on predefined events or conditions. These triggers can be set up to respond to various events within the Kubernetes environment, such as the creation or update of specific resources, changes in configuration, or other custom-defined events. When a trigger event occurs, the associated workflow is automatically initiated, enabling seamless and automated task execution.
- Cronjobs: In addition to manual runs and triggers, workflows can also be scheduled using cronjobs. Cronjobs provide the ability to define recurring or periodic executions of workflows based on a specific time or schedule. This allows for the automation of repetitive tasks or regular maintenance operations, ensuring that critical processes are performed at designated intervals without the need for manual intervention.
In the context of workflows, a workflow node refers to an individual step or task within a workflow. It represents a discrete unit of work that is executed as part of the overall workflow process.
Each node typically has inputs, outputs, and defined behavior or actions associated with it. Nodes can include actions like data transformations, decision points, integrations with external systems, or any other specific task required to accomplish the workflow's objectives. The workflow nodes are connected together to define the sequence and dependencies of the tasks within the workflow.
Find more about nodes in the Workflow Editor section
