fix(subdomain-catalog): database.0mpc.com is Adminer UI; fix /etc/hosts for extra-sites#16
Merged
Merged
Conversation
…edge_oidc), not postgres TCP - subdomain-catalog.json: fix database.example.com entry — exposure was "private-only/private_network" but the subdomain is actually the Adminer web UI on runtime-general-lv3:8082, published via nginx edge behind Keycloak oauth2-proxy (edge-published/edge_oidc) - certificate-catalog.json: add database-edge entry so the cert audit does not flag a CRITICAL missing coverage finding - subdomain-exposure-registry.json: regenerated after catalog fix - docker_runtime defaults: extend public_edge_host_aliases to include public_edge_extra_sites hostnames (changelog, docs, database, minio-console) and the apex domain so /etc/hosts is complete on all VMs — fixes cert-validator CONNECTION_FAILED for 5 domains that fell through to stale external DNS Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
config/subdomain-catalog.json: Fixeddatabase.example.com— entry wasprivate-only/private_network(describing the postgres TCP proxy), but the subdomain actually serves the Adminer web UI onruntime-general-lv3:8082, published via nginx edge + Keycloak oauth2-proxy. Corrected toedge-published/edge_oidc.config/certificate-catalog.json: Addeddatabase-edgeentry — cert audit was failing CRITICAL because the updated catalog entry had no corresponding cert coverage.config/subdomain-exposure-registry.json: Regenerated after catalog fix.docker_runtimerole defaults: Extendeddocker_runtime_public_edge_host_aliasesto includepublic_edge_extra_siteshostnames (changelog, docs, database, minio-console) and the apex domain (public_edge_apex_hostname). Previously these were missing from/etc/hostson all VMs, causing them to fall through to stale external DNS (51.89.70.16) and failing cert validation.Verification
subdomain_exposure_audit.py --validate→ exit 0 (was failing with CRITICAL before)make route-dns-assertion-ledger env=production→ ok=67, failed=0 (bypassed audit was needed before)runtime-control-lv3: 47/49 valid (was 41/49). Remaining 2 failures are intentional Tailscale-only services (proxmox UI port 8006, vaultwarden port 443) that use100.64.0.1targets by design.Test plan
make converge-api-gateway env=productionafter merge to apply updated/etc/hoststo all VMs