Expose staging identity service on tailnet#48
Merged
Merged
Conversation
Add a Tailscale Ingress resource for the staging environment so the identity service is accessible over the tailnet. Update the JWT issuer in the staging configmap to use the tailnet domain (identity-staging.tailc06f30.ts.net) and register the new manifest in kustomization.yaml. Co-Authored-By: Claude Opus 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
k8s/staging/tailscale-ingress.yaml) so the identity staging service is reachable over the tailnet atidentity-staging.tailc06f30.ts.net.JWT_ISSUERin the staging configmap from the publicethanswan.comdomain to the tailnet domain.kustomization.yaml.Test plan
identity-stagingnamespace.identity-staging.tailc06f30.ts.netis accessible from a device on the tailnet.🤖 Generated with Claude Code