kubernetes.manifest.apply_ssa

Server-side apply (SSA) a single Kubernetes manifest

Server-side apply (SSA) a single Kubernetes manifest.

PATCHes the manifest to the apiserver with Content-Type: application/apply-patch+yaml and a stable fieldManager, persisting the change. This is the GitOps-correct apply: the apiserver tracks field ownership so re-applies are idempotent and (with force) the manager reclaims fields edited out-of-band — the mechanism behind self-heal.

Inputs:

• connection_uuid: Cloud connection UUID for the target cluster (required).
• manifest: Single resource manifest with apiVersion, kind, metadata.name, and metadata.namespace for namespaced kinds (required).
• field_manager: Field-manager name to apply as (optional, default "ltinteg-gitops"). GitOps callers pass a per-application manager so ownership is scoped to the application.
• force: Force-reclaim conflicting fields owned by other managers (optional, default True). True = self-heal manual drift.

Outputs:

• applied: The applied object body returned by the apiserver.
• resource_version: The new metadata.resourceVersion.
• uid: The object's metadata.uid.

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	—	Cloud connection UUID for the target cluster
manifest	json	Yes	—	Single resource manifest with apiVersion, kind, metadata.name, and optionally metadata.namespace
field_manager	string	No	—	Field-manager name (default ltinteg-gitops)
force	boolean	No	—	Force-reclaim conflicting fields (default True)
organization_uuid	uuid	No	—	—

Output Schema

Field	Type	Required	Default	Description
connection_uuid	uuid	No	—	—
organization_uuid	uuid	No	—	—
manifest	json	No	—	—
field_manager	string	No	—	—
force	boolean	No	—	—
api_version	string	No	—	—
kind	string	No	—	—
namespace	string	No	—	—
name	string	No	—	—
resource_version	string	No	—	metadata.resourceVersion of the applied object
uid	string	No	—	metadata.uid of the applied object
applied	json	No	—	The object body the apiserver returned after apply
failure_reason	string	No	—	—
failure_type	string	No	—	—
failed_action	string	No	—	—
failed_at_state	string	No	—	—
error	string	No	—	—
error_type	string	No	—	—
failed_layer	string	No	—	—
failed_step	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

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

{
  "workflow_type": "kubernetes.manifest.apply_ssa",
  "initial_data": {
    "connection_uuid": "value",
    "manifest": "value"
  }
}