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
Updates Gateway Status Checking #12955
Conversation
Hi @danehans. Thanks for your PR. I'm waiting for a istio 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. |
xref: #12940 |
/ok-to-test But you will need to run the |
@danehans To fix the gencheck failure, run |
0e4eadd
to
4c14eba
Compare
Looking into why |
Job |
@howardjohn mentioned in the CI PR that failing to get the host address may be a bug. |
Signed-off-by: Daneyon Hansen <daneyon.hansen@solo.io>
For the
|
4c14eba
to
9931258
Compare
@@ -241,22 +241,22 @@ waypoint default/bookinfo-productpage applied | |||
View the `productpage` waypoint proxy status; you should see the details of the gateway | |||
resource with `Ready` status: | |||
|
|||
{{< text bash >}} | |||
{{< text syntax=bash snip_id=none >}} |
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.
No longer needed since test is now using Test is now using _wait_for_gateway
.
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.
Since the primary purpose of doc tests (with side benefit of testing Istio) is to test that the documented instructions work as documented, a general best practice is to call snips wherever we can. The util functions are intended for docs that don't include explicit instructions, e.g., docs that just say before-you-begin install bookinfo, or something like that.
Wait for the Gateway to be accepted: | ||
|
||
{{< text syntax=bash snip_id=none >}} | ||
$ kubectl wait --for=condition=accepted gtw mygateway |
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 correct semantics of gateway accepted vs programmed vs ready is still not agreed in the upstream gateway-api project, so I think we should wait for resolution before updating any docs.
kubernetes-sigs/gateway-api#1877
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.
@frankbu PTAL at #12955 (comment). The way that Gateway status is currently implemented, Programmed=True
can be surfaced when an address is unassigned. This is causing tests that set INGRESS_HOST
to fail. As you mention, kubernetes-sigs/gateway-api#1877 is attempting to resolve ambiguity in the conditions. Maybe the best path forward is to check for the presence of both status conditions until this is resolved?
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.
@danehans The problem is that there are 14 other docs that are broken by the current implementation. Fixing the implementation (to at least align with the best guess of where the spec is going) seems like a better approach than hacking all the docs temporarily. (Btw, the fact that the current impl has accepted not true until the address is assigned is an obvious bug since according to the spec accepted just means the config is syntactically valid.)
f53a2ad
to
924c591
Compare
/retest |
a86880d
to
66fb20e
Compare
Noting also that @howardjohn mentioned in Slack that the underlying change may be reverted so we may need to revert some of our changes as well. Biggest unknown is when and that drives when we can actually update the version of Istio we are testing against. |
a89a244
to
f18a5c9
Compare
xref: istio/istio#44139 to remove wait conditions for Gateway status. |
f18a5c9
to
79a6547
Compare
@@ -119,18 +119,6 @@ snip_l7_authorization_policy_3() { | |||
kubectl get gtw bookinfo-productpage -o yaml | |||
} | |||
|
|||
! read -r -d '' snip_l7_authorization_policy_4 <<\ENDSNIP |
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.
Note: This snip is not currently being used by the test.
Signed-off-by: Daneyon Hansen <daneyon.hansen@solo.io>
Signed-off-by: Daneyon Hansen <daneyon.hansen@solo.io>
79a6547
to
236afca
Compare
@@ -247,16 +247,16 @@ $ kubectl get gtw bookinfo-productpage -o yaml | |||
|
|||
Verify that the waypoint proxy status is ready: | |||
|
|||
{{< text plaintext >}} | |||
{{< text syntax=plaintext snip_id=none >}} |
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.
Note: This snip is not currently being used by the test.
Signed-off-by: Daneyon Hansen <daneyon.hansen@solo.io>
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
/test doc.test.profile_none |
* Updates Gateway Status Check for Ambient Guide Signed-off-by: Daneyon Hansen <daneyon.hansen@solo.io> * Updates status condition checking Signed-off-by: Daneyon Hansen <daneyon.hansen@solo.io> * Bumps istio dep Signed-off-by: Daneyon Hansen <daneyon.hansen@solo.io> * Generated changes from gen-check Signed-off-by: Daneyon Hansen <daneyon.hansen@solo.io> --------- Signed-off-by: Daneyon Hansen <daneyon.hansen@solo.io>
Please provide a description for what this PR is for.
Updates the Gateway status condition check for the ambient getting started guide due to istio/istio#43975.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.