docs: Conceptual Docs for Api Gateways, The Gateway Api & Envoy Proxy#5739
docs: Conceptual Docs for Api Gateways, The Gateway Api & Envoy Proxy#5739melsal13 wants to merge 0 commit intoenvoyproxy:mainfrom
Conversation
Codecov ReportAttention: Patch coverage is
❌ Your patch check has failed because the patch coverage (51.38%) is below the target coverage (60.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #5739 +/- ##
==========================================
- Coverage 65.40% 65.29% -0.12%
==========================================
Files 216 216
Lines 35767 35912 +145
==========================================
+ Hits 23392 23447 +55
- Misses 10925 11012 +87
- Partials 1450 1453 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
melsal13
changed the title
There was a problem hiding this comment.
Consider changing this section to be about Gateway vs Ingress and how Gateway is the evolution of Ingress. Maybe explain how someone coming from a background of using Kubernetes ingress can use and understand Gateway API
There was a problem hiding this comment.
Ingress here is the concept, not the resource
As you've pointed out, we also need to explain the Ingress in the Gateway API section, haha
There was a problem hiding this comment.
Added a section like this in API Gateways and the Gateway API doc!
melsal13
force-pushed
the
docs-eg-conceptual
branch
from
703d826 to
6300ac3
Compare
|
@melsal13 lint is failing, since linkinator cannot find the links |
missBerg
left a comment
missBerg
left a comment
There was a problem hiding this comment.
Left some suggestions, let me know if you disagree with any of them :)
There was a problem hiding this comment.
Consider putting this paragraph first in the section The Gateway API in Envoy Gateway
melsal13
force-pushed
the
docs-eg-conceptual
branch
from
56badac to
0752df1
Compare
3 participants
What type of PR is this?
Adds conceptual documentation for:
What this PR does / why we need it:
Introduces foundational conceptual docs to help onboard new users and improve documentation clarity.
Which issue(s) this PR fixes:
Fixes #5738
Fixes #5753
Fixes #5754
Release Notes: No