Repository navigation
Enable read-only Teleport access to production PostgreSQL - #35
Merged
Merged
Conversation
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
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.
Enable certificate-only Teleport access to the production PostgreSQL database using the passwordless
teleportrole withpg_read_all_data. Existing managed tailnet services, server certificate names, and application authentication remain intact.The client CA Secret and restricted Teleport endpoint are owned by the companion darkmatter/gitops change. Deploy that Secret before merging this PR.
Validation: production overlay rendered with the deployed Argo Kustomize/KSOPS tools and passed Kubernetes server-side dry run; verified managed services and serverAltDNSNames are preserved. Changed YAML formatted with oxfmt. Live authenticated SQL validation follows rollout.
Tracking: darkmatter/gitops Beads gitops-hzl.