Actions90
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- Jobs Actions
- CronJobs Actions
Overview
This node interacts with Kubernetes clusters to perform various operations on Kubernetes resources, including CronJobs. Specifically, the 'Restart' operation allows restarting a CronJob within a specified namespace. This is useful for automating management tasks in Kubernetes environments, such as restarting scheduled jobs to apply new configurations or recover from failures.
Use Case Examples
- Restarting a CronJob named 'daily-backup' in the 'default' namespace to apply updated job specifications.
- Automating the restart of CronJobs as part of a CI/CD pipeline to ensure scheduled tasks run with the latest code or environment settings.
Properties
| Name | Meaning |
|---|---|
| Image | The container image to use when running or restarting a pod related to the CronJob. |
| Namespace | The Kubernetes namespace where the CronJob resource is located. |
| Resource Name | The name of the specific CronJob resource to restart. |
Output
JSON
stdout- The standard output from running or restarting the pod associated with the CronJob, typically containing execution logs or command results.
Dependencies
- Requires Kubernetes API credentials to authenticate and interact with the Kubernetes cluster.
Troubleshooting
- If no credentials are returned, the node will throw an error indicating missing Kubernetes API credentials. Ensure credentials are properly configured.
- If the 'command' parameter is not an array when running a pod, an error is thrown. Verify that the command input is a valid JSON array.
- Errors may occur if the specified namespace or resource name does not exist or is inaccessible. Confirm the namespace and resource name are correct and that the credentials have sufficient permissions.