0015. Create by default and orphan by default¶
Status: accepted. Date: 2026-11-14.
Supersedes the defaults of ADR 0004.
Context¶
ADR 0004 chose creationPolicy: CreateOrAdopt, so a typo in a name silently adopts an unrelated
object, and two CRs on one path both adopt it. It chose per-kind deletion defaults, later changed
to Orphan everywhere. Adoption and deletion change what the operator owns and should be explicit.
Decision¶
creationPolicydefaults toCreate: an existing object that is not ours givesConflict.AdoptandCreateOrAdoptare explicit. Bulk adoption goes through the import tool (ADR 0016).deletionPolicydefaults toOrphanfor every kind through a CRD default.Deleteis opt-in; destructive kinds also need the guard annotation (ADR 0013).
Consequences¶
- Importing existing configuration needs
AdoptorCreateOrAdoptper object. - Config paths that always read back with defaults (for example
KVConfig,PKIConfig) can never be created and needAdoptorCreateOrAdopt. - A CR removed from Git leaves its OpenBao object; stale policies and roles must be cleaned up deliberately.
- Status: implemented (CRD defaults in
api/common/v1alpha1).