kubernetes.manifest.validate ​
Server-side schema validation of a manifest with strict field checking (no mutation)
Server-side schema validation of a Kubernetes manifest with strict field checking (no mutation).
Issues a kubectl apply --dry-run=server --validate=strict equivalent via the raw REST API:
Content-Type: application/apply-patch+json?dryRun=All&fieldValidation=Strict
The call is non-mutating: the dryRun=All query parameter tells the API server to validate and admit the request through every admission webhook but not to persist any changes.
Inputs:
- connection_uuid: Cloud connection UUID (required)
- manifest: Single-resource manifest dict with at least
apiVersion,kind,metadata.nameand optionallymetadata.namespace(required)
Outputs:
- valid: True if the manifest passed strict validation, False otherwise
- errors: List of
{field, message}dicts; empty when valid=True
Plugin required: context.get_plugin("connection").kubernetes_runner_clients(connection_uuid, organization_uuid) must expose api_client (a kubernetes.client.ApiClient instance).
Overview ​
| Property | Value |
|---|---|
| Workflow type | Atomic |
| Library | App-kubernetes |
| Version | 1.0 |
Input Schema ​
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
connection_uuid | uuid | Yes | — | — |
manifest | json | Yes | — | — |
organization_uuid | uuid | No | — | — |
Output Schema ​
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
connection_uuid | uuid | No | — | — |
organization_uuid | uuid | No | — | — |
manifest | json | No | — | — |
valid | boolean | No | — | — |
errors | json | No | — | — |
failure_reason | string | No | — | — |
failure_type | string | No | — | — |
failed_action | string | No | — | — |
failed_at_state | string | No | — | — |
failed_step | string | No | — | — |
failed_layer | string | No | — | — |
error | string | No | — | — |
error_type | string | No | — | — |
States ​
| State | Initial | Terminal | Success | Auto-advance | Description |
|---|---|---|---|---|---|
pending | Yes | No | — | execute | — |
completed | No | Yes | Yes | — | — |
failed | No | Yes | No | — | — |
State Diagram ​
Transitions ​
| From | Action | To | Description |
|---|---|---|---|
pending | execute | completed | — |
* (any state) | fail | failed | — |
API Usage ​
bash
POST /api/workflows/start
Content-Type: application/json
{
"workflow_type": "kubernetes.manifest.validate",
"initial_data": {
"connection_uuid": "value",
"manifest": "value"
}
}