Rancher27 icon

Rancher27

Interact with Rancher/Kubernetes API
Join our community

Actions40

Overview

This node enables interaction with Rancher and Kubernetes APIs, specifically managing Kubernetes resources such as StatefulSets. For the StatefulSet Delete operation, it deletes a specified StatefulSet resource within a given Kubernetes namespace.

This is useful in scenarios where you want to automate the cleanup or removal of stateful applications managed by StatefulSets in your Kubernetes cluster. For example, you might delete a StatefulSet when decommissioning an application or during CI/CD pipeline steps that require environment teardown.

Properties

Name Meaning
Cluster Name or ID Select the Kubernetes cluster where the StatefulSet exists. 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 within the project where the StatefulSet resides.

These properties are required to identify the exact location of the StatefulSet to delete.

Output

The output is a JSON object representing the response from the Rancher/Kubernetes API after attempting to delete the StatefulSet. It typically contains status information about the deletion request.

No binary data output is produced by this operation.

Example output structure (conceptual):

{
  "status": "Success",
  "details": {
    "name": "statefulset-name",
    "namespace": "namespace-name"
  }
}

Dependencies

  • Requires an API authentication token credential for Rancher/Kubernetes API access.
  • The node depends on the Rancher/Kubernetes API being accessible and properly configured.
  • The user must have appropriate permissions to delete StatefulSets in the specified namespace.

Troubleshooting

  • Common issues:

    • Insufficient permissions to delete the StatefulSet.
    • Incorrect cluster, project, or namespace selection leading to resource not found errors.
    • Network connectivity issues to the Rancher/Kubernetes API endpoint.

  • Common error messages:

    • "Resource not found" — Verify the cluster, project, namespace, and StatefulSet name are correct.
    • "Unauthorized" or "Forbidden" — Check API credentials and user permissions.
    • "Timeout" or "Connection refused" — Ensure network connectivity and API server availability.

Resolving these usually involves verifying input parameters, credentials, and network settings.

Links and References

Discussion