Skip to content

docs(oci): preserve Argo transport owner #101

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
syscod3 merged 1 commit into from
Sep 9, 2026
Merged

docs(oci): preserve Argo transport owner #101

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/deploy/runbook.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,16 @@ After the oci-lab cluster is up and reachable over the private path

Never commit the token or CA; they travel only through Bitwarden.

## Argo transport ownership invariant

For the remote OCI reconciliation path, the GitOps-owned `argocd/omni-kubernetes-proxy`
Service and its `ProxyGroup` egress manifest are a single transport unit. Keep
that owning egress manifest applied until Argo has a separately deployed,
verified replacement path; removing it first breaks Argo's DNS/reachability
path. Recovery order is: restore/reconcile the owner, verify proxy resolution
and the registered OCI cluster, then verify Application sync. Do not delete the
manifest as cleanup while OCI Applications still depend on this transport.

## 5. Pre-merge gate

Do not merge #17 until both pass:
Expand Down
Loading