Appearance
Kubernetes
Manage pods, deployments, services, and cluster resources via the Kubernetes API.
| Detail | Value |
|---|---|
| Category | DevOps |
| Base URL | https://kubernetes.default.svc |
| Authentication | Bearer Token |
| Endpoints | 8 |
| Connector key | kubernetes |
Using Kubernetes in a workflow
- Go to Connections and click New Connection.
- Pick Kubernetes from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /api/v1/namespaces | List namespaces |
GET /api/v1/namespaces/{namespace}/pods | List pods |
GET /api/v1/namespaces/{namespace}/pods/{name} | Read a pod |
GET /api/v1/namespaces/{namespace}/pods/{name}/log | Read pod logs |
GET /apis/apps/v1/namespaces/{namespace}/deployments | List deployments |
POST /apis/apps/v1/namespaces/{namespace}/deployments | Create a deployment |
PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale | Scale a deployment |
GET /api/v1/nodes | List cluster nodes |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /api/v1/namespaces
List namespaces
| Detail | Value |
|---|---|
| Operation ID | devops.listNamespaces |
| Method | GET |
| Path | /api/v1/namespaces |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Kubernetes connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listNamespaces. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kubernetes API reference.
GET /api/v1/namespaces/{namespace}/pods
List pods
| Detail | Value |
|---|---|
| Operation ID | devops.listNamespacedPods |
| Method | GET |
| Path | /api/v1/namespaces/{namespace}/pods |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Kubernetes connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listNamespacedPods. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kubernetes API reference.
GET /api/v1/namespaces/{namespace}/pods/{name}
Read a pod
| Detail | Value |
|---|---|
| Operation ID | devops.readNamespacedPod |
| Method | GET |
| Path | /api/v1/namespaces/{namespace}/pods/{name} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Kubernetes connection from the Connection dropdown.
- In the Operation dropdown, select
devops.readNamespacedPod. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kubernetes API reference.
GET /api/v1/namespaces/{namespace}/pods/{name}/log
Read pod logs
| Detail | Value |
|---|---|
| Operation ID | devops.readNamespacedPodLog |
| Method | GET |
| Path | /api/v1/namespaces/{namespace}/pods/{name}/log |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Kubernetes connection from the Connection dropdown.
- In the Operation dropdown, select
devops.readNamespacedPodLog. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kubernetes API reference.
GET /apis/apps/v1/namespaces/{namespace}/deployments
List deployments
| Detail | Value |
|---|---|
| Operation ID | devops.listNamespacedDeployments |
| Method | GET |
| Path | /apis/apps/v1/namespaces/{namespace}/deployments |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Kubernetes connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listNamespacedDeployments. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kubernetes API reference.
POST /apis/apps/v1/namespaces/{namespace}/deployments
Create a deployment
| Detail | Value |
|---|---|
| Operation ID | devops.createNamespacedDeployment |
| Method | POST |
| Path | /apis/apps/v1/namespaces/{namespace}/deployments |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Kubernetes connection from the Connection dropdown.
- In the Operation dropdown, select
devops.createNamespacedDeployment. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kubernetes API reference.
PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale
Scale a deployment
| Detail | Value |
|---|---|
| Operation ID | devops.patchNamespacedDeploymentScale |
| Method | PATCH |
| Path | /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Kubernetes connection from the Connection dropdown.
- In the Operation dropdown, select
devops.patchNamespacedDeploymentScale. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kubernetes API reference.
GET /api/v1/nodes
List cluster nodes
| Detail | Value |
|---|---|
| Operation ID | devops.listNodes |
| Method | GET |
| Path | /api/v1/nodes |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Kubernetes connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listNodes. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kubernetes API reference.