-
Notifications
You must be signed in to change notification settings - Fork 101
feat: Add a landing page for NGINX Gateway Fabric #911
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
base: main
Are you sure you want to change the base?
Conversation
This commit adds a landing page for NGINX Gateway Fabric. Custom landing pages allow us to draw a reader's attention towards the documentation they would find most useful as both a prospective or returning user, such as evergreen reference material.
✅ Deploy Preview will be available once build job completes!
|
Co-authored-by: yar <y82@users.noreply.github.com>
Added some detail from the design page to the design section of the landing page, linking to the page itself. Took the pull request out of draft since this is now a MVP. I don't want to treat the conversation around the design information for NGINX Gateway Fabric to become a blocker for this landing page when we can iterate on it relatively quickly. |
{{</card>}} | ||
{{<card title="Secure backend traffic" titleUrl="/nginx-gateway-fabric/traffic-security/secure-backend/">}} | ||
Encrypt traffic between pods using a BackendTLSPolicy. |
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.
I think https://docs.nginx.com/nginx-gateway-fabric/traffic-security/integrate-cert-manager/ is going to be the more common use case than backend traffic. I believe users care more about securing traffic from the client to nginx (ingress traffic), versus traffic from nginx to the backend (which is already in the cluster).
Proposed changes
This commit adds a landing page for NGINX Gateway Fabric. Custom landing pages allow us to draw a reader's attention towards the documentation they would find most useful as both a prospective or returning user, such as evergreen reference material.
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩