Automation Menu
Core Concepts
4min
When talking about Automation int the Kubeark context, it is important to understand the core concepts and terminology around the platform interface.
Workspace
- An organizational construct that groups together related resources and settings for effective management and collaboration.
- It serves as a container within which users can manage a variety of entities such as Kubernetes clusters, templates, and deployments, as well as infrastructure components.
- Workspaces allow users to segment and organize their projects or resources based on teams, projects, or any logical grouping, providing a structured approach to resource management.
Workflows
- A workflow in Kubeark is an automated sequence of tasks or operations designed to accomplish a specific objective or process.
- It represents a series of actions, often linked by logic or conditions, that are executed to manage and orchestrate tasks within the platform.
- Workflows in Kubeark typically involve automating interactions between different components like Kubernetes resources, infrastructure elements, and other integrated services.
Nodes
- Fundamental building blocks of a workflow.
- Represent specific actions or operations like data transformations, system integrations, and conditional branching.
- Organized into various types such as Control Nodes, Action Nodes, Task Nodes, and Kubeark Nodes, each serving a distinct purpose within the workflow.
Triggers
- Mechanisms that initiate the execution of a workflow.
- Can be set to respond to internal events within Kubeark as well as from external sources, such as changes in resource status or specific system conditions.
- Enable workflows to run automatically, facilitating real-time responses to events.
Webhooks
- Used to trigger workflows based on external events.
- Allow Kubeark workflows to integrate with external systems and services.
- When a specific event occurs in an external service, the webhook sends data to Kubeark, triggering the associated workflow.
Forms
- User interfaces within the main Workspace container for capturing input. Forms can trigger subsequent Workflows.
- Allow for manual data entry or selections that can determine the course or configuration of a workflow.
- Useful for workflows that require user decisions or inputs at certain stages.
Cron Jobs
- Enable scheduling of workflows to run at specified times or intervals.
- Useful for regular tasks like maintenance, backups, or periodic updates.
- Help automate repetitive tasks, ensuring they occur without manual intervention.
- Cron Jobs operate at Workspace level and can be associated with multiple subsequent Workflows
