-
Notifications
You must be signed in to change notification settings - Fork 349
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
docs: Show GatewayAPI APIs in EG docs #2749
Comments
@zirain @Xunzhuo thoughts on the best way to do this ? |
that make sense |
When should we update the copied files? Each time we bump the gwapi version ? |
@Xunzhuo we could add the new make target that does the fetch + copy and add it into existing docs pipeline |
Yep, let me add it. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
Seems we can do something as in #3416, to link the GW-API type to relevant field. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
/unstaleify |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
hey @zirain can you hep with this one ? |
wait for upstream: kubernetes-sigs/gateway-api#3204 |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
@zirain looks like 3204 is probably not going to land anytime soon |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
Description:
Currently the API reference only shows Envoy Gateway extensions https://gateway.envoyproxy.io/latest/api/
We should also show Gateway API reference within Envoy Gateway to provide a better experience https://gateway-api.sigs.k8s.io/reference/spec/
[optional Relevant Links:]
The text was updated successfully, but these errors were encountered: