merge cnpg/p05-wave4-gcp (e870e7f0c0) #417
Loading…
Reference in a new issue
No description provided.
Delete branch "cnpg/p05-wave4-gcp"
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?
The openbao CRs configuring vault (not the DB) move out of the cnpg-platform catchall into the OpenBao singleton ns, ahead of the postgres cutover. Wave 1 = the pure vault-config DNS trio: policies gcp-external-dns-{stack}, gcp-lease-cleanup-{stack} + auth-roles external-dns-{stack}, cert-manager-{stack}, gcp-lease-cleanup-{stack}. Placement now follows spec.openbaoNamespace (same knob as the server address) instead of cnpg-{vaultName}. Vault state is untouched: operators adopt existing paths; old CRs in cnpg-platform are orphaned (deletionPolicy=Retain) and deleted manually after the new ones go Ready.Transit backend transit-{platform} + policy cosign-signer-{platform} (XPlatform), auth-role build-pipeline-{stack} (XStack, policyRefs resolve same-ns so it moves with the cosign policy), and the forgejo instance-signing pair forgejo-signing-{tenant} / {tenant}-forgejo-signing (XForgejo, hardcoded ns literals). Vault paths (transit/*, kv/*) are ns-independent; operators adopt existing state — key versions unchanged.pki-root-{platform} backend + root cert, pki-internal-{platform} backend + intermediate CA, and the 3 PKI roles (cnpg-server/cnpg-client/bundle-export rsa-yellow). Controllers adopt existing vault mounts (read->exists->status-only) so root/intermediate serials are unchanged; the k8s trust materialization (OpenBaoPKICertificate internal-ca-bundle-source-platform + Bundles) lives in ns cert-manager and is untouched. The 2 OpenBaoPKIIssuers reference the backend by vault path string and stay with the postgres certs until the DB cutover.The clouddns-service-account connection secret (seed key for the OpenBao gcp mount, minted from the shared seanfarm-platform-iam SA) moves with its only reader: OpenBaoGCPSecretsBackend gcp-{stack} resolves credentialsSecretRef in its own ns, so secret + backend + the Object dependsOn gate + the external-dns-{stack} roleset all flip together. The secret is byte-copied to ns openbao before this lands so neither upjet state reconstruction nor the backend reconcile ever sees a missing key (no SA-key re-mint).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.