-
Notifications
You must be signed in to change notification settings - Fork 504
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.
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 proxy configuration #20231107 #20230503 in 4314 issue #6952
Conversation
Signed-off-by: AntonEliatra <[email protected]>
Signed-off-by: AntonEliatra <[email protected]>
Signed-off-by: AntonEliatra <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks reasonable, but I don't know anything about cross cluster search of the proxy configuration being discussed so let's just make sure we are extra confident in what is shared.
Thanks @scrawfor99 I tested this fully, using 2 separate clusters prior to raising the PR, therefore can confirm this does indeed works as described |
Thanks, @scrawfor99. Let's have someone from the cluster team take a look. I'll ping @rohiwali. |
Hi @natebower , when we come across a proper noun that is getting flagged by Vale, do we always add it to our approved list or handle some other way? This is the name getting flagged: https://www.nginx.com/. Thanks! Update: I just checked our style guide and this is already included as an accepted term, just capitalized. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @AntonEliatra . Here are some wording suggestions and fixes to the Vale errors.
Co-authored-by: Heather Halter <[email protected]> Signed-off-by: AntonEliatra <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few minor comments. Rest LGTM!
Signed-off-by: AntonEliatra <[email protected]>
Signed-off-by: AntonEliatra <[email protected]>
Thank you @ankitkala, that's been updated now |
Thanks for your thorough review, @ankitkala ! I'll push this through to doc review. |
Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: AntonEliatra <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small comment but otherwise LGTM
Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: AntonEliatra <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AntonEliatra @Naarcha-AWS Please see my comments and changes and let me know if you have any questions. Thanks!
Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: AntonEliatra <[email protected]>
Signed-off-by: AntonEliatra <[email protected]>
Signed-off-by: Naarcha-AWS <[email protected]>
* adding proxy configuration #20231107 #20230503 in 4314 issue Signed-off-by: AntonEliatra <[email protected]> * adding proxy configuration #20231107 #20230503 in 4314 issue Signed-off-by: AntonEliatra <[email protected]> * Update cross-cluster-search.md Signed-off-by: AntonEliatra <[email protected]> * Apply suggestions from code review Co-authored-by: Heather Halter <[email protected]> Signed-off-by: AntonEliatra <[email protected]> * adding prerequisite to cross-cluster page Signed-off-by: AntonEliatra <[email protected]> * typo on cross-cluster page Signed-off-by: AntonEliatra <[email protected]> * Apply suggestions from code review Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: AntonEliatra <[email protected]> * Update _search-plugins/cross-cluster-search.md Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: AntonEliatra <[email protected]> * Apply suggestions from code review Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: AntonEliatra <[email protected]> * updating proxy details as per comments Signed-off-by: AntonEliatra <[email protected]> * Update cross-cluster-search.md Signed-off-by: Naarcha-AWS <[email protected]> --------- Signed-off-by: AntonEliatra <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> Co-authored-by: Heather Halter <[email protected]> Co-authored-by: Stephen Crawford <[email protected]> Co-authored-by: Naarcha-AWS <[email protected]> Co-authored-by: Nathan Bower <[email protected]> (cherry picked from commit 00fa73e) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Description
Adding details on proxy configuration for cross cluster search and basic details for proxy configuration itself using Nginx
Issues Resolved
#20231107 - /docs/latest/security/authentication-backends/proxy/ | Even though everything is set, I am still facing 401 error
#20230503 - /docs/latest/security/access-control/cross-cluster-search/ |What about other details? What if my port is proxied?
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.