# ADR 0008 — Helm + Kubernetes Server-Side Apply Deployment

**Status:** Accepted

## Context

AWP needs a Kubernetes deployment provider without rebuilding reconciliation mechanics. It must preserve explicit release/deployment state, approvals, health and rollback.

## Decision

Baseline `DeploymentProvider` renders Helm/manifests, performs server-side dry-run/diff, applies via Kubernetes Server-Side Apply with an AWP field manager, observes rollout/health, persists Deployment result and rolls back to a known-good Release when policy requires.

## Consequences

AWP owns release/deployment meaning and policy; Kubernetes owns apply/rollout mechanics. Flux/Flagger are optional only for explicit independent GitOps/progressive-delivery requirements.

## Rejected Alternatives

- custom Kubernetes controller/reconciler as baseline;
- mutable environment-specific rebuilds as normal promotion;
- Flux/Flagger mandatory for every project.

## Increment Realization

Target seam specified now; product activation in I6, with earlier CI/artifact identities designed to fit it.