Skip to content
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

Ambient beta get started guide patch #14805

Open
wants to merge 29 commits into
base: master
Choose a base branch
from

Conversation

nauticalmike
Copy link
Contributor

Description

Adjusting removing the inpod from doc per @bleggett 's suggestion #14788 (comment)

Reviewers

  • Ambient
  • Docs
  • Installation
  • Networking
  • Performance and Scalability
  • Extensions and Telemetry
  • Security
  • Test and Release
  • User Experience
  • Developer Infrastructure
  • Localization/Translation

@nauticalmike nauticalmike requested a review from a team as a code owner March 29, 2024 01:27
@istio-testing istio-testing added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 29, 2024
@istio-testing
Copy link
Contributor

Hi @nauticalmike. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@ericvn
Copy link
Contributor

ericvn commented Mar 29, 2024

You will need to enable the tests, removing the -disabled on the test names in the https://github.com/istio/istio.io/tree/master/content/en/docs/ops/ambient/getting-started directory (and update the test: value to say yes in the index file (causing the snips file to be regenerated)). Since this page was not passing the tests with the latest istio builds, I had hoped that your earlier PR would have fixed the tests, I have disabled them so we could move up.

Pointer to Slack discussion on the test failure: https://istio.slack.com/archives/C049TCZMPCP/p1711387715045829

@ericvn
Copy link
Contributor

ericvn commented Mar 29, 2024

/ok-to-test

@istio-testing istio-testing added ok-to-test Set this label allow normal testing to take place for a PR not submitted by an Istio org member. and removed needs-ok-to-test labels Mar 29, 2024
Copy link
Contributor

@bleggett bleggett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TY! Wording SGTM, rest LGTM outside of @ericvn's comments

@nauticalmike
Copy link
Contributor Author

thanks @bleggett, @ericvn will do shortly

@nauticalmike
Copy link
Contributor Author

/retest

@nauticalmike
Copy link
Contributor Author

nauticalmike commented Mar 29, 2024

@ericvn I'm hitting an issue here:

VERIFY FAILED snip_layer_7_authorization_policy_4 (timeout after 120s):
received:
"<!doctype html>
<html lang=en>
<title>405 Method Not Allowed</title>
<h1>Method Not Allowed</h1>
<p>The method is not allowed for the requested URL.</p>"
expected:
"RBAC: access denied"

What should I do here? What I mean is on this step we are supposed to get an RBAC: access denied but the verify received something else. This test was working fine before and the previous run just timed out after 1h.

@nauticalmike
Copy link
Contributor Author

/retest

@ericvn
Copy link
Contributor

ericvn commented Apr 1, 2024

@ericvn I'm hitting an issue here:

VERIFY FAILED snip_layer_7_authorization_policy_4 (timeout after 120s):
received:
"<!doctype html>
<html lang=en>
<title>405 Method Not Allowed</title>
<h1>Method Not Allowed</h1>
<p>The method is not allowed for the requested URL.</p>"
expected:
"RBAC: access denied"

What should I do here? What I mean is on this step we are supposed to get an RBAC: access denied but the verify received something else. This test was working fine before and the previous run just timed out after 1h.

Correct. This is the problem that moving up istio references causes breaking the tests. I'm not sure what the resolution should be, but see the discussion in Slack mentioned above with @ilrudie

@nauticalmike
Copy link
Contributor Author

/retest

@bleggett
Copy link
Contributor

bleggett commented Apr 9, 2024

Since this is mostly a wording fix and doctests seem to need a rework in the wake of the waypoint attach changes, suggest we leave the tests disabled here, and raise an issue to fix+enable the doctests.

@ericvn
Copy link
Contributor

ericvn commented Apr 10, 2024

Since this is mostly a wording fix and doctests seem to need a rework in the wake of the waypoint attach changes, suggest we leave the tests disabled here, and raise an issue to fix+enable the doctests.

The tests are disabled and there already is a release blocker issue to enable and fix them: istio/istio#50145.

What you need to do in this PR would be to not rename the disabled test back so that we are trying to run it, and likely only include any index.md changes you desire. Note that the doc will need to be reworked and test rewritten in the next few weeks as I believe 1.22 is planned for release in a month or so.

@nauticalmike
Copy link
Contributor Author

/retest

@istio-testing
Copy link
Contributor

@nauticalmike: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
doc.test.profile-none_istio.io d5474b2 link true /test doc.test.profile-none

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. I understand the commands that are listed here.

@istio-testing istio-testing added the needs-rebase Indicates a PR needs to be rebased before being merged label Apr 22, 2024
@istio-testing
Copy link
Contributor

PR needs rebase.

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.

@@ -261,7 +261,7 @@ $ kubectl label namespace default istio.io/dataplane-mode=ambient
Congratulations! You have successfully added all pods in the default namespace
to the mesh. Note that you did not have to restart or redeploy anything!

Check once again the ztunnel logs for the proxy has received the network namespace (netns) information about an ambient application pod, and has started proxying for it:
Check the ztunnel logs for the proxy has received the network namespace (netns) information about an ambient application pod, and has started proxying for it:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Check the ztunnel logs for the proxy has received the network namespace (netns) information about an ambient application pod, and has started proxying for it:
Check the ztunnel logs to confirm the proxy has received the network namespace (netns) information about an application pod in ambient mode, and has started proxying for it:

@craigbox
Copy link
Contributor

craigbox commented May 2, 2024

@nauticalmike please rebase and we can get the wording changes in separately from the test changes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ambient kind/docs needs-rebase Indicates a PR needs to be rebased before being merged ok-to-test Set this label allow normal testing to take place for a PR not submitted by an Istio org member. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants