KubernetesInstall

Overview

This node enables interaction with Kubernetes resources, specifically supporting operations such as retrieving logs from DaemonSets among other resource management tasks. For the DaemonSets resource and the Logs operation, it fetches the logs of a specified DaemonSet within a given namespace.

Common scenarios where this node is beneficial include:

• Debugging and monitoring Kubernetes DaemonSets by accessing their logs directly.
• Automating log retrieval for DaemonSets in CI/CD pipelines or operational workflows.
• Integrating Kubernetes log data into broader automation or alerting systems.

For example, a user can specify the namespace and the name of a DaemonSet to retrieve its logs, which helps in troubleshooting issues related to that DaemonSet’s pods.

Properties

Output

The node outputs JSON data containing the logs retrieved from the specified DaemonSet. The structure typically includes standard output (stdout) content representing the logs text.

If the node supports binary data output (not explicitly shown for Logs), it would represent raw log files or streamed log content, but here the focus is on JSON-formatted textual logs.

Dependencies

• Requires valid Kubernetes API credentials configured in n8n to authenticate and interact with the Kubernetes cluster.
• Depends on the Kubernetes API being accessible and properly configured for the user’s environment.
• No additional external services are required beyond Kubernetes itself.

Troubleshooting

• No credentials got returned!
  This error indicates missing or misconfigured Kubernetes API credentials. Ensure that the node has access to valid credentials with sufficient permissions.

• Resource not found or empty logs
  If the specified DaemonSet name or namespace is incorrect, the node may return empty results or errors. Verify the resource name and namespace are correct.

• Command must be an array!
  Although more relevant to the "run" operation, if commands are used improperly, this error may appear. For logs, ensure no command input is mistakenly provided.

• Network or permission issues connecting to the Kubernetes API can cause failures. Confirm network connectivity and RBAC permissions.

Links and References

• Kubernetes DaemonSets Documentation
• Kubernetes Logs Documentation
• Kubernetes Field Selectors
• Kubernetes Label Selectors