Add support for NGINX Service Mesh internal routes #1075
Merged
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.
Proposed changes
Add support for NGINX Service Mesh internal routes.
Adds command line flag
-enable-internal-routes
which requires-spire-agent-address
and-nginx-plus
.If internal routes are enabled an internal route server block is generated to terminate tls connections using the Spiffe certs fetched from the Spire agent. Internal routes are created for Ingress resources that are annotated with
nsm.nginx.com/internal-route: "true"
and can only be accessed by services in NGINX Service Mesh.Changes
-spire-agent-address
to require-nginx-plus
and removes SpiffeCerts config option from the oss templates.Checklist
Before creating a PR, run through this checklist and mark each as complete.