Actions90
- Jobs Actions
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- CronJobs Actions
Overview
This node interacts with Kubernetes clusters to perform various operations on Kubernetes resources. Specifically, for the Jobs - Delete operation, it deletes a specified Job resource within a given namespace in the Kubernetes cluster.
Common scenarios where this node is beneficial include:
- Automating cleanup of completed or failed Jobs in Kubernetes.
- Managing lifecycle of batch processing tasks by programmatically deleting Jobs after completion.
- Integrating Kubernetes Job management into broader automation workflows without manual kubectl commands.
Example use case: Automatically delete a Kubernetes Job named "data-backup-job" in the "default" namespace once it has finished running, as part of a scheduled workflow.
Properties
| Name | Meaning |
|---|---|
| Namespace | The Kubernetes namespace where the Job resource exists. Defaults to "default". |
| Resource Name | The name of the specific Job resource to delete. |
Output
The output JSON contains the response from the Kubernetes API after attempting to delete the specified Job resource. This typically includes metadata about the deleted resource or status confirmation.
The node does not output binary data.
Dependencies
- Requires an API authentication token or credentials configured in n8n to connect to the Kubernetes cluster.
- The node depends on a Kubernetes client utility internally to communicate with the Kubernetes API.
- Proper RBAC permissions must be granted to the provided credentials to allow deletion of Job resources in the target namespace.
Troubleshooting
No credentials got returned!
This error indicates that the node could not retrieve the necessary Kubernetes API credentials. Ensure that valid credentials are configured and selected in the node.Resource not found or permission denied errors
Verify that the specified Job name exists in the given namespace and that the credentials have sufficient permissions to delete Jobs.Invalid namespace or resource name
Double-check the spelling and correctness of the namespace and resource name inputs.General API errors
Check network connectivity to the Kubernetes API server and confirm that the API endpoint is reachable.