Skip to content

Document GCP Private Service Connect DNS setup - #585

Open
ivanauth wants to merge 1 commit into
authzed:mainfrom
ivanauth:docs/gcp-psc-dns-setup
Open

Document GCP Private Service Connect DNS setup#585
ivanauth wants to merge 1 commit into
authzed:mainfrom
ivanauth:docs/gcp-psc-dns-setup

Conversation

@ivanauth

@ivanauth ivanauth commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Improve docs

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Preview deployment skipped — @ivanauth does not have write access to this repository.

A maintainer can trigger a preview deployment by re-running this workflow.

The GCP steps gave no shape for the Cloud DNS zone or record names, so
readers could not tell that the private zone belongs at the logical
region rather than the environment. A zone at the environment level is
authoritative for the whole subtree and hides the public management
console hostname inside the VPC.

Give the endpoint hostname shape, both record options and their
tradeoff, per-VPC endpoint and zone scoping, on-premises resolution, and
verification that does not rely on ping or nc. Move permission system
creation ahead of DNS so the hostname the zone is derived from exists.

Signed-off-by: ivanauth <ivan@authzed.com>
@ivanauth
ivanauth force-pushed the docs/gcp-psc-dns-setup branch from 9699772 to 1556447 Compare September 9, 2026 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant