Portainer icon

Portainer

Interact with Portainer via API

Actions190

Kubernetes → Delete Roles

AI-generated

Overview

This node operation allows you to delete Kubernetes Roles in specified namespaces. It is useful for managing and cleaning up role-based access control (RBAC) configurations within a Kubernetes cluster by removing roles that are no longer needed or should be revoked.

Typical use cases include:

  • Automating the removal of outdated or temporary roles across multiple namespaces.
  • Enforcing security policies by deleting roles that violate compliance.
  • Cleaning up roles during environment teardown or migration processes.

For example, you might provide a payload mapping namespaces to arrays of role names, and the node will delete those roles accordingly.

Properties

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

Example of Payload value:

{
  "default": ["role1", "role2"],
  "kube-system": ["admin-role"]
}

Output

The node outputs JSON data reflecting the result of the delete operations. This typically includes confirmation of deleted roles or error information if deletion failed. The exact structure depends on the API response but generally contains status messages per namespace and role.

No binary data output is produced by this operation.

Dependencies

  • Requires connection to a Kubernetes environment identified by the provided environment ID.
  • Needs appropriate API authentication credentials configured in n8n to authorize role deletions.
  • The node relies on the Portainer API or a similar Kubernetes management API endpoint as indicated by the bundled source code.

Troubleshooting

  • Invalid Environment ID: If the environment identifier does not correspond to a valid Kubernetes environment, the node will fail. Verify the environment ID is correct.
  • Malformed Payload: The payload must be a valid JSON string mapping namespaces to arrays of role names. Invalid JSON or incorrect structure will cause errors.
  • Insufficient Permissions: Deleting roles requires proper permissions. Ensure the API credentials have RBAC rights to delete roles in the specified namespaces.
  • Role Not Found: Attempting to delete a non-existent role may return an error or warning. Confirm role names exist before deletion.
  • API Connectivity Issues: Network or authentication problems with the Kubernetes API endpoint can cause failures. Check connectivity and credential validity.

Links and References


If you need further details or examples, feel free to ask!

Discussion