Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adding for docs for insecureEdgeTerminatePolicy in reencrypt and passthrough routes #3244

Merged
merged 1 commit into from
Dec 5, 2016
Merged

adding for docs for insecureEdgeTerminatePolicy in reencrypt and passthrough routes #3244

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions architecture/core_concepts/routes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -640,6 +640,12 @@ The destination pod is responsible for serving certificates for the
traffic at the endpoint. This is currently the only method that can support
requiring client certificates (also known as two-way authentication).

[NOTE]
====
passthrough routes can also have an `insecureEdgeTerminationPolicy` the only valid values are
`None` or empty (for disabled) or `Redirect`.
====

[[re-encryption-termination]]
*Re-encryption Termination*

Expand Down Expand Up @@ -683,6 +689,11 @@ validate the endpoint certificate, securing the connection from the router to
the destination. This field is required, but only for re-encryption.
====

[NOTE]
====
Reencrypt routes can have an insecureEdgeTerminationPolicy with all of the same values as for edge-terminated routes.
====


[[router-sharding]]
== Router Sharding
Expand Down