Portainer icon

Portainer

Interact with Portainer via API

Actions190

Kubernetes → Delete Kubernetes Services

AI-generated

Overview

This node operation allows you to delete Kubernetes services in bulk by specifying namespaces and the corresponding services within them. It is useful for automating cleanup tasks in Kubernetes clusters, such as removing obsolete or unwanted services across multiple namespaces efficiently. For example, if you want to remove several services from different namespaces after a deployment rollback or during environment teardown, this operation can streamline that process.

Properties

Name Meaning
Id Environment identifier (a numeric ID representing the target Kubernetes environment).
Body A JSON string representing a map where each key is a Kubernetes namespace and the value is an array of service names to delete within that namespace.

Example of the Body property content:

{
  "default": ["service1", "service2"],
  "kube-system": ["service3"]
}

Output

The node outputs JSON data representing the result of the delete operations. Typically, this would include status information about each service deletion request, such as success confirmations or error details per service. The output does not explicitly mention binary data handling, so it is assumed to be purely JSON.

Dependencies

  • Requires access to a Kubernetes environment identified by the provided environment ID.
  • Needs an API authentication token or credential configured in n8n to authorize requests against the Kubernetes cluster.
  • The node uses HTTP requests to interact with the Kubernetes API or a proxy API managing Kubernetes resources.

Troubleshooting

  • Invalid Environment ID: If the environment identifier is incorrect or missing, the node will fail to connect to the Kubernetes cluster. Verify the environment ID corresponds to a valid configured Kubernetes environment.
  • Malformed Body JSON: The Body property must be a valid JSON string mapping namespaces to arrays of service names. Invalid JSON or incorrect structure will cause errors. Use proper JSON formatting.
  • Permission Issues: Insufficient permissions to delete services in specified namespaces will result in authorization errors. Ensure the API token or credentials have adequate rights.
  • Nonexistent Services or Namespaces: Attempting to delete services or namespaces that do not exist may return errors or warnings. Confirm the services and namespaces are correct before running the node.

Links and References

Discussion