Portainer icon

Portainer

Interact with Portainer via API

Actions190

Kubernetes → Update Kubernetes Namespace Deprecated

AI-generated

Overview

This node operation allows updating a Kubernetes namespace using a deprecated method. It is designed to modify the details of an existing namespace within a Kubernetes environment by specifying its identifier and new configuration data. This can be useful in scenarios where you need to programmatically adjust namespace settings, such as changing labels, annotations, or resource quotas.

Practical examples include:

  • Updating namespace metadata to reflect organizational changes.
  • Modifying resource limits or policies applied to a namespace.
  • Automating namespace configuration updates as part of CI/CD pipelines.

Properties

Name Meaning
Id The numeric identifier of the Kubernetes environment where the namespace exists.
Namespace The name of the Kubernetes namespace to update.
Body A JSON string containing the updated details of the namespace (e.g., metadata, spec).

Output

The node outputs JSON data representing the response from the Kubernetes API after attempting to update the namespace. This typically includes the updated namespace object with its current state and metadata.

If the node supports binary data output, it would generally relate to raw HTTP responses or logs, but this specific operation focuses on JSON data only.

Dependencies

  • Requires access to a Kubernetes cluster API endpoint.
  • Needs appropriate authentication credentials (such as a token or certificate) configured in n8n to authorize API requests.
  • The node depends on the Kubernetes API being accessible and the user having permissions to update namespaces.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or missing credentials.
    • Insufficient permissions to update the specified namespace.
    • Malformed JSON in the "Body" property causing request errors.
    • Specifying a non-existent namespace or environment ID.

  • Error messages and resolutions:

    • 401 Unauthorized: Check that the API credentials are correct and have sufficient permissions.
    • 404 Not Found: Verify that the namespace and environment ID exist.
    • 400 Bad Request: Ensure the JSON body is correctly formatted and contains valid fields for namespace updates.
    • Deprecated warning: Since this operation is marked deprecated, consider migrating to a newer supported method if available.

Links and References

Discussion