Rancher27 icon

Rancher27

Interact with Rancher/Kubernetes API
Join our community

Actions40

Overview

This node enables interaction with Rancher and Kubernetes APIs to manage various Kubernetes resources, including CronJobs. Specifically for the CronJob - Resume operation, it allows users to resume a suspended CronJob in a specified Kubernetes namespace. This is useful when you want to restart scheduled jobs that were previously paused or suspended.

Common scenarios include:

  • Resuming automated batch jobs after maintenance windows.
  • Restarting periodic tasks that were temporarily halted.
  • Managing job schedules dynamically based on operational needs.

Example: You have a CronJob that runs nightly backups but had been suspended during system upgrades. Using this node's Resume operation, you can programmatically resume the CronJob once upgrades are complete.

Properties

Name Meaning
Cluster Name or ID Select the Kubernetes cluster where the CronJob resides. Can be chosen from a list or specified via expression.
Project Name or ID Select the project within the cluster. Depends on the selected cluster.
Namespace Name or ID Select the namespace containing the CronJob. Depends on the selected project.

These properties identify the exact location of the CronJob resource to operate on.

Output

The node outputs JSON data representing the result of the Resume operation on the CronJob resource. The output typically includes details about the updated CronJob object as returned by the Rancher/Kubernetes API, such as its metadata and current status indicating it is no longer suspended.

No binary data output is involved.

Dependencies

  • Requires an active connection to a Rancher or Kubernetes cluster.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests to the Rancher/Kubernetes API.
  • The node depends on internal methods to load available clusters, projects, and namespaces dynamically.

Troubleshooting

  • Common issues:

    • Incorrect cluster, project, or namespace selection leading to "resource not found" errors.
    • Insufficient permissions or invalid API credentials causing authorization failures.
    • Attempting to resume a CronJob that is already active may result in no changes or warnings.

  • Error messages:

    • "Resource not found" — Verify that the cluster, project, namespace, and CronJob exist and are correctly specified.
    • "Unauthorized" or "Forbidden" — Check API credentials and user permissions.
    • "Invalid operation" — Ensure the CronJob is currently suspended before attempting to resume.

Resolving these usually involves verifying configuration inputs and ensuring proper access rights.

Links and References

Discussion