-
Notifications
You must be signed in to change notification settings - Fork 213
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
document Linkerd and Gateway HTTPRoute API groups #1667
Conversation
As of Linkerd 2.14, we now support HTTPRoutes with both the `policy.linkerd.io` and `gateway.networking.k8s.io` API groups. This branch adds documentation discussing the differences between these two API groups, and notes in the docs stating that both are supported.
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.
LGTM 👍
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 great. 🙂 Do you think it's worth calling out the need to fully qualify one or the other HTTPRoute when using kubectl
?
Approving irrespective of the above. 🙂
This is a great point. It appears |
i'll add something about that, good call. |
As of Linkerd 2.14, we now support HTTPRoutes with both the `policy.linkerd.io` and `gateway.networking.k8s.io` API groups. This branch adds documentation discussing the differences between these two API groups, and notes in the docs stating that both are supported.
As of Linkerd 2.14, we now support HTTPRoutes with both the `policy.linkerd.io` and `gateway.networking.k8s.io` API groups. This branch adds documentation discussing the differences between these two API groups, and notes in the docs stating that both are supported.
As of Linkerd 2.14, we now support HTTPRoutes with both the
policy.linkerd.io
andgateway.networking.k8s.io
API groups. This branch adds documentation discussing the differences between these two API groups, and notes in the docs stating that both are supported.