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 manage various Kubernetes resources. Specifically, the Delete operation under the Services resource allows users to delete a specified Kubernetes Service within a given namespace.
Common scenarios for this node include automating Kubernetes resource management tasks such as cleaning up unused services, managing lifecycle of microservices, or integrating Kubernetes operations into broader automation workflows.
For example, you might use this node to automatically delete a service after a deployment pipeline finishes testing, ensuring that temporary services do not persist unnecessarily.
Properties
| Name | Meaning |
|---|---|
| Namespace | The Kubernetes namespace where the target Service resides. Defaults to "default". |
| Resource Name | The name of the specific Service resource to delete within the specified namespace. |
Output
The node outputs JSON data representing the result of the delete operation. This typically includes status information returned by the Kubernetes API about the deletion request (e.g., confirmation of deletion or error details).
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to a Kubernetes cluster.
- Needs credentials providing API access to the Kubernetes cluster (an API key or token).
- The node depends on a Kubernetes client utility internally to communicate with the cluster.
Troubleshooting
- No credentials got returned!: This error indicates missing or misconfigured Kubernetes API credentials. Ensure valid credentials are set up and linked to the node.
- Resource not found or cannot be deleted: If the specified Service name does not exist in the given namespace, the Kubernetes API will return an error. Verify the resource name and namespace are correct.
- Permission denied errors: The API credentials must have sufficient permissions to delete Services in the target namespace.
- Invalid input types: For other operations like
run, the node expects certain inputs (e.g., command array). While not directly related to Delete, ensure inputs match expected types to avoid errors.