Actions90
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- Jobs Actions
- CronJobs Actions
CronJobs → Run
AI-generatedOverview
This node interacts with Kubernetes to perform various operations on Kubernetes resources, specifically supporting the 'Run' operation for CronJobs among others. It allows users to run a pod with a specified image, command, and environment variables within a given namespace and resource name. This is useful for automating Kubernetes job executions, testing containerized applications, or running batch jobs programmatically.
Use Case Examples
- Run a CronJob pod with a specific container image and command to automate scheduled tasks.
- Execute a command inside a Kubernetes pod to perform maintenance or data processing tasks.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use for running the pod. |
| Command | The command array to execute inside the pod. |
| Environment Variables | Environment variables to set inside the pod. |
| Namespace | The Kubernetes namespace where the pod or resource exists. |
| Resource Name | The name of the Kubernetes resource (e.g., pod or CronJob) to run or operate on. |
Output
JSON
stdout- The standard output from running the pod with the specified image, command, and environment variables.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- Ensure the Kubernetes credentials are correctly configured and have sufficient permissions to run pods and access resources in the specified namespace.
- Verify that the 'command' and 'env' inputs are valid JSON arrays; otherwise, the node will throw an error.
- Resource name is mandatory for operations like run, restart, exec, and others; missing this will cause errors.
- Check that the specified container image is accessible and valid in the Kubernetes environment to avoid pod creation failures.