Document explicit Envoy annotations and gRPC routing - #10
Merged
Merged
Conversation
prayujt
changed the title
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.
Update the routing documentation and sample configuration for the Envoy server migration in rayman-tech/nimbus#43.
Use explicit
envoy.nimbus.dev/*annotations for auth and gRPC settings. Document gRPC timeouts, service/method matching, opt-in retries, server prerequisites, and deprecated NGINX aliases with conflict validation.The action already submits configuration to Nimbus without creating Kubernetes resources, so its inputs, requests, and URL outputs need no code changes. Existing services migrate on redeploy through the updated server.
Validation: sample YAML parses and
git diff --checkpasses. Documentation only; nothing deployed.