-
Notifications
You must be signed in to change notification settings - Fork 492
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: update getting-started and httproute guides for v1alpha2 #786
docs: update getting-started and httproute guides for v1alpha2 #786
Conversation
Hi @shaneutt. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
ef39da7
to
5cafba8
Compare
/ok-to-test |
5cafba8
to
b23c84d
Compare
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 for the work on this @shaneutt!
@@ -33,7 +29,7 @@ Route labels and Gateway label selectors allow Routes and Gateways to be | |||
bound to each other by their respective owners. |
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.
The paragraph above this needs to be updated to match v1alpha2 route attachment.
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 ended up tearing it out and replacing this and the example yaml, the results are in c03ae32 lmkwyt 👍
b23c84d
to
d96f473
Compare
/assign @shaneutt |
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.
Just a few more nits, but otherwise LGTM.
!!! danger | ||
This page has not been updated for v1alpha2 yet. | ||
|
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 this needs to stay in place until the directions actually allow for installing v1alpha2 CRDs
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.
Right, because this is the landing page so this should be the last one to remove its banner, makes sense to me in retrospect.
Given that part of the context here seems to be that it's the pages this page links to that are not updated yet, I added this back in b6a39a6 but I changed the wording a bit, lmkwyt 👍
LGTM pending CI, nice work @shaneutt! |
4775c71
to
33d492b
Compare
@robscott I think you had asked earlier for the spec to be removed from an example |
@shaneutt sorry for the confusion there! I was actually just suggesting that the GatewayClass resource was unnecessary for that example. Most users won't be creating a new GatewayClass for each Gateway, Route, etc. In the text before and after the example, there's no mention of the GatewayClass, so I think it could safely be removed from that example. |
33d492b
to
85f8400
Compare
Sounds good, that's now removed. |
Thanks! /lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: robscott, shaneutt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
This updates the examples in the
HTTPRoute
guide forv1alpha2
, and does some spacing cleanup for the getting started guide (but that guide did not appear to need any special updating forv1alpha2
).Which issue(s) this PR fixes:
Resolves the first two tasks in #783