Skip to content
For LLMsView as Markdown·

Kubernetes ​

Manage pods, deployments, services, and cluster resources via the Kubernetes API.

DetailValue
CategoryDevOps
Base URLhttps://kubernetes.default.svc
AuthenticationBearer Token
Endpoints8
Connector keykubernetes

Using Kubernetes in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick Kubernetes from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints ​

EndpointSummary
GET /api/v1/namespacesList namespaces
GET /api/v1/namespaces/{namespace}/podsList pods
GET /api/v1/namespaces/{namespace}/pods/{name}Read a pod
GET /api/v1/namespaces/{namespace}/pods/{name}/logRead pod logs
GET /apis/apps/v1/namespaces/{namespace}/deploymentsList deployments
POST /apis/apps/v1/namespaces/{namespace}/deploymentsCreate a deployment
PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scaleScale a deployment
GET /api/v1/nodesList 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

DetailValue
Operation IDdevops.listNamespaces
MethodGET
Path/api/v1/namespaces

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Kubernetes connection from the Connection dropdown.
  3. In the Operation dropdown, select devops.listNamespaces.
  4. 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

DetailValue
Operation IDdevops.listNamespacedPods
MethodGET
Path/api/v1/namespaces/{namespace}/pods

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Kubernetes connection from the Connection dropdown.
  3. In the Operation dropdown, select devops.listNamespacedPods.
  4. 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

DetailValue
Operation IDdevops.readNamespacedPod
MethodGET
Path/api/v1/namespaces/{namespace}/pods/{name}

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Kubernetes connection from the Connection dropdown.
  3. In the Operation dropdown, select devops.readNamespacedPod.
  4. 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

DetailValue
Operation IDdevops.readNamespacedPodLog
MethodGET
Path/api/v1/namespaces/{namespace}/pods/{name}/log

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Kubernetes connection from the Connection dropdown.
  3. In the Operation dropdown, select devops.readNamespacedPodLog.
  4. 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

DetailValue
Operation IDdevops.listNamespacedDeployments
MethodGET
Path/apis/apps/v1/namespaces/{namespace}/deployments

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Kubernetes connection from the Connection dropdown.
  3. In the Operation dropdown, select devops.listNamespacedDeployments.
  4. 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

DetailValue
Operation IDdevops.createNamespacedDeployment
MethodPOST
Path/apis/apps/v1/namespaces/{namespace}/deployments

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Kubernetes connection from the Connection dropdown.
  3. In the Operation dropdown, select devops.createNamespacedDeployment.
  4. 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

DetailValue
Operation IDdevops.patchNamespacedDeploymentScale
MethodPATCH
Path/apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Kubernetes connection from the Connection dropdown.
  3. In the Operation dropdown, select devops.patchNamespacedDeploymentScale.
  4. 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

DetailValue
Operation IDdevops.listNodes
MethodGET
Path/api/v1/nodes

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Kubernetes connection from the Connection dropdown.
  3. In the Operation dropdown, select devops.listNodes.
  4. 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.