Skip to content
Proud to collaborate with Microsoft for Startups

kubernetes.target_availability.verify ​

Prove deny-test targets are present and available before treating access-denied as evidence

Read-only check that each named target used in a deny test is actually present and available. A NetworkPolicy "denied" result is only evidence when the destination existed and was ready.

Each target is {namespace, kind, name}. Supported kinds: Service, Endpoints, Deployment, Pod, StatefulSet.

The workflow always completes successfully and reports all_available plus per-target available / reason. Missing or unready targets are not a workflow failure.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-kubernetes
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
connection_uuiduuidYes——
targetslistYes—List of {namespace, kind, name} objects to probe.
organization_uuiduuidNo——

Output Schema ​

FieldTypeRequiredDefaultDescription
connection_uuiduuidNo——
organization_uuiduuidNo——
targetslistNo——
all_availablebooleanNo——
available_countintegerNo——
unavailable_countintegerNo——
itemsjsonNo——
observed_atstringNo——
failure_reasonstringNo——
failure_typestringNo——
failed_actionstringNo——
failed_at_statestringNo——
failed_stepstringNo——
failed_layerstringNo——
errorstringNo——
error_typestringNo——

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—execute—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
pendingexecutecompleted—
* (any state)failfailed—

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "kubernetes.target_availability.verify",
  "initial_data": {
    "connection_uuid": "value",
    "targets": "value"
  }
}