Portainer icon

Portainer

Interact with Portainer via API

Actions190

Kubernetes → Get Kubernetes RBAC Status

AI-generated

Overview

This node operation retrieves the Kubernetes RBAC (Role-Based Access Control) status for a specified environment or endpoint. It is useful in scenarios where you need to verify or audit the current RBAC configuration of a Kubernetes cluster, such as checking permissions, roles, and bindings applied within the cluster. For example, administrators can use this node to programmatically fetch RBAC status to ensure compliance with security policies or to troubleshoot access issues.

Properties

Name Meaning
Id Environment (Endpoint) identifier. This numeric ID specifies which Kubernetes environment's RBAC status to retrieve.

Output

The output will contain JSON data representing the RBAC status of the specified Kubernetes environment. This typically includes details about roles, role bindings, cluster roles, and cluster role bindings configured in the cluster. The exact structure depends on the Kubernetes API response but generally provides comprehensive information about access control settings.

No binary data output is expected from this operation.

Dependencies

  • Requires an active connection to a Kubernetes environment identified by the provided environment ID.
  • Requires appropriate API authentication credentials configured in n8n to access the Kubernetes cluster.
  • The node depends on the Portainer API or a similar management API that exposes Kubernetes RBAC status via an authenticated request.

Troubleshooting

  • Common Issues:

    • Invalid or missing environment ID may cause failure to retrieve RBAC status.
    • Insufficient permissions or incorrect API credentials can lead to authorization errors.
    • Network connectivity issues between n8n and the Kubernetes environment/API endpoint.
  • Error Messages:

    • Authorization errors indicating invalid or expired credentials: Verify and update the API authentication token or key.
    • Not found or invalid environment ID errors: Confirm the environment ID corresponds to a valid Kubernetes endpoint.
    • Timeout or network errors: Check network connectivity and API endpoint availability.

Links and References

Discussion