merge feat/olly-teardown (799c24df6e) #258
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/olly-teardown"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.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.