Actions90
- Jobs Actions
- Namespaces Actions
- Pods Actions
- Services Actions
- Deployments Actions
- ReplicaSets Actions
- StatefulSets Actions
- DaemonSets Actions
- CronJobs Actions
Overview
This node enables interaction with Kubernetes clusters by performing various operations on Kubernetes resources. Specifically, for the Namespaces resource with the Patch operation, it allows users to modify existing namespace objects in a Kubernetes cluster.
Common scenarios where this node is beneficial include:
- Updating metadata or labels of a namespace.
- Modifying configuration aspects of namespaces without deleting and recreating them.
- Automating namespace management as part of CI/CD pipelines or infrastructure automation.
For example, you might patch a namespace to add a new label that triggers specific monitoring or quota policies.
Properties
| Name | Meaning |
|---|---|
| Image | The container image name used when running or restarting pods; relevant for some operations including patch. |
| Namespace | The Kubernetes namespace context in which the operation is performed (default is "default"). For Namespaces resource, this typically refers to the cluster-wide scope but must be provided due to UI consistency. |
| Resource Name | The name of the specific namespace resource to patch. |
Note: Although the bundled code shows many properties, for the Namespaces - Patch operation, these are the relevant inputs based on your provided JSON and code context.
Output
The node outputs JSON data representing the result of the patch operation on the namespace resource. This typically includes the updated namespace object returned from the Kubernetes API after applying the patch.
The output JSON structure corresponds to the Kubernetes API response for the patched namespace, containing fields such as metadata, spec, status, and any changes applied.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to a Kubernetes cluster via credentials that provide API access (e.g., an API token or kubeconfig).
- The node depends on a Kubernetes client utility (
K8SClient) internally to communicate with the Kubernetes API. - Proper permissions are needed on the Kubernetes cluster to perform patch operations on namespaces.
Troubleshooting
No credentials got returned!
This error occurs if the node cannot retrieve the required Kubernetes API credentials. Ensure that valid credentials are configured and selected in the node.Command must be an array!
While not directly related to patching namespaces, this error appears if thecommandproperty is incorrectly formatted for operations that require commands (like run). For patch, ensure no irrelevant command input is provided.API permission errors
If the Kubernetes API returns authorization errors, verify that the credentials have sufficient RBAC permissions to patch namespaces.Invalid patch format
Since the patch operation details are not fully shown in the code snippet, ensure that the patch payload (not detailed here) conforms to Kubernetes patch specifications (e.g., JSON Merge Patch or Strategic Merge Patch).
Links and References
- Kubernetes Namespaces API: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
- Kubernetes Patch Documentation: https://kubernetes.io/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch/
- Kubernetes Field Selectors: https://kubernetes.io/docs/concepts/overview/working-with-objects/field-selectors/
- Kubernetes Label Selectors: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/