Rancher27 icon

Rancher27

Interact with Rancher/Kubernetes API
Join our community

Actions40

Overview

This node integrates with Rancher/Kubernetes API to manage Kubernetes nodes, specifically supporting the "Taint" operation on nodes. The "Taint" operation allows users to add or update taints on a specified Kubernetes node. Taints are key-value pairs with an effect that influence pod scheduling by marking nodes so that pods with matching tolerations can be scheduled accordingly.

Common scenarios for this node include:

  • Preventing certain pods from being scheduled on specific nodes by applying taints.
  • Managing node behavior in a cluster by controlling pod placement through taints.
  • Automating node maintenance workflows where taints signal unschedulable or special conditions.

Practical example:

  • You want to mark a node as unschedulable for general workloads but allow only critical pods to run there. You apply a taint with key maintenance, value true, and effect NoSchedule. Pods without a matching toleration will not be scheduled on this node.

Properties

Name Meaning
Node ID The unique identifier of the Kubernetes node to which the taints will be applied.
Taints A collection of taints to add or update on the node. Each taint includes:
- Key: The taint key (string).
- Value: The taint value (string).
- Effect: The taint effect, one of: NoSchedule, PreferNoSchedule, or NoExecute.
Cluster Name or ID Selects the target Kubernetes cluster by name or ID.
Project Name or ID Selects the project within the cluster by name or ID.
Namespace Name or ID Selects the namespace within the project by name or ID.

Output

The node outputs JSON data representing the result of the taint operation on the node. This typically includes the updated node object or confirmation details returned by the Rancher/Kubernetes API after applying the taints.

If binary data were involved (not applicable here), it would represent raw files or logs, but this node focuses on JSON structured data.

Dependencies

  • Requires access to a Rancher or Kubernetes cluster via the Rancher/Kubernetes API.
  • Needs an API authentication token or API key credential configured in n8n to authenticate requests.
  • The node depends on the Rancher API client libraries bundled internally.
  • Requires proper configuration of cluster, project, and namespace selections to target the correct Kubernetes environment.

Troubleshooting

  • Invalid Node ID: If the provided node ID does not exist or is incorrect, the API call will fail. Verify the node ID is correct and accessible.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or token is valid and has sufficient permissions.
  • Insufficient Permissions: The user associated with the API credentials must have permission to modify node taints.
  • Incorrect Taint Format: Providing taints without required fields (key, effect) or invalid effect values may cause errors. Use only supported effects (NoSchedule, PreferNoSchedule, NoExecute).
  • Cluster/Project/Namespace Mismatch: Selecting incompatible or non-existent clusters, projects, or namespaces will lead to errors. Confirm these selections correspond to your Kubernetes setup.

Links and References

Discussion