merge feat/olly-teardown (799c24df6e) #258

Open
pipeline-bot wants to merge 2 commits from feat/olly-teardown into trunk
Collaborator
No description provided.
Milestone F (1/2): observability collapsed to the olly-platform singleton
(argocd-platform + sean/olly), so the per-tenant XMetrics/XLogs/XTraces/XGrafana
claims in the Stack composition are redundant. Removing them makes Crossplane
delete xmetrics/xlogs/xtraces/xgrafana 'alice' -> deletes olly-alice's
VM/Loki/Tempo/Grafana. komoplane + tekton-dashboard claims are UNTOUCHED (they
stay in olly-alice). Compositions/XRDs deleted in a follow-up ship once the
composites are gone (avoids XRD-removed-while-composite-terminating race).
Orphaned olly-alice PVCs + alice-* MinIO buckets are intentionally left as a
grace-period data safety net.
Milestone F (2/2), completing the observability collapse:
- Delete the 4 now-unused per-tenant obs compositions+XRDs (apis/{metrics,logs,
  traces,grafana}) + their apis/kustomization refs. Their composites (xmetrics/
  xlogs/xtraces/xgrafana alice) were already GC'd by Ship 1 (claims removed),
  so removing the XRDs is now race-free.
- FIX the namespace-ownership landmine Ship 1 exposed: XMetrics implicitly owned
  the olly-{tenant} Namespace, so deleting obs cascade-deleted it and took
  komoplane + tekton-dashboard down (recovered live by recreating the ns). Give
  the komoplane composition explicit ownership of olly-{tenant} as resource #0,
  deletionPolicy: Orphan so it can never again cascade the ns out from under
  tekton. Adopts the existing ns on a running cluster; creates it on rebuild.
This pull request has changes conflicting with the target branch.
  • apis/komoplane/composition.yaml
  • apis/kustomization.yaml
  • apis/stack/composition.yaml
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/olly-teardown:feat/olly-teardown
git switch feat/olly-teardown
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/platform-seanfarm!258
No description provided.