Portainer icon

Portainer

Interact with Portainer via API

Actions190

Kubernetes → Get Kubernetes Nodes Limits

AI-generated

Overview

This node operation retrieves the resource limits of Kubernetes nodes within a specified environment. It is useful for monitoring and managing the resource allocation (such as CPU and memory limits) across nodes in a Kubernetes cluster. Practical applications include capacity planning, ensuring workloads are balanced according to node limits, and troubleshooting resource constraints.

Properties

Name Meaning
Id Environment (Endpoint) identifier specifying which Kubernetes cluster environment to query. This is a required numeric value.

Output

The output JSON contains details about the resource limits configured on the Kubernetes nodes in the specified environment. This typically includes information such as CPU and memory limits per node. The exact structure depends on the Kubernetes API response but generally provides an array or object with node identifiers and their corresponding resource limit specifications.

No binary data output is expected from this operation.

Dependencies

  • Requires access to a Kubernetes environment endpoint identified by the provided Id.
  • Requires proper authentication credentials configured in n8n to connect to the Kubernetes API.
  • The node relies on Kubernetes API availability and permissions to fetch node resource limits.

Troubleshooting

  • Common issues:

    • Invalid or missing environment identifier (Id) will prevent the node from querying the correct Kubernetes cluster.
    • Insufficient permissions or incorrect credentials may cause authorization errors when accessing the Kubernetes API.
    • Network connectivity issues between n8n and the Kubernetes API endpoint can result in timeouts or connection failures.
  • Error messages:

    • Authorization errors indicating invalid or missing API tokens/credentials.
    • Resource not found errors if the specified environment ID does not correspond to a valid Kubernetes cluster.
    • Timeout or network errors suggesting connectivity problems.

To resolve these issues:

  • Verify that the Id corresponds to a valid and accessible Kubernetes environment.
  • Ensure that the API credentials used have sufficient permissions to read node resource limits.
  • Check network connectivity and firewall settings between n8n and the Kubernetes API server.

Links and References

Discussion