Skip to content

Updated traffic management concept guide#5014

Merged
istio-testing merged 43 commits intoistio:masterfrom
LisaFC:master
Sep 20, 2019
Merged

Updated traffic management concept guide#5014
istio-testing merged 43 commits intoistio:masterfrom
LisaFC:master

Conversation

@LisaFC
Copy link
Copy Markdown
Contributor

@LisaFC LisaFC commented Sep 18, 2019

Updated traffic management concept guide to make it more feature-focused, per my proposal:
https://docs.google.com/document/d/1PnT1P6dHjYqkZv-cx1qg2JH4x8dVdPsRv1IvYx6wFlw/edit

[ ] Configuration Infrastructure
[X] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@LisaFC LisaFC requested a review from a team as a code owner September 18, 2019 15:25
@googlebot googlebot added the cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. label Sep 18, 2019
@istio-testing
Copy link
Copy Markdown
Contributor

Hi @LisaFC. 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.

Details

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.

@istio-testing istio-testing added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Sep 18, 2019
@geeknoid
Copy link
Copy Markdown
Contributor

/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 Sep 18, 2019
@geeknoid geeknoid requested review from a team September 18, 2019 15:39
Copy link
Copy Markdown
Member

@howardjohn howardjohn left a comment

Choose a reason for hiding this comment

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

Looks great, left a few nitpick comments

LisaFC and others added 2 commits September 18, 2019 20:12
Co-Authored-By: John Howard <howardjohn@google.com>
Co-Authored-By: John Howard <howardjohn@google.com>
@LisaFC
Copy link
Copy Markdown
Contributor Author

LisaFC commented Sep 19, 2019

/retest

@sdake
Copy link
Copy Markdown
Member

sdake commented Sep 20, 2019

@LisaFC - linting errors:

Total in 13807 ms
    ./en/docs/concepts/traffic-management/index.md
      326 | [HTTPMatchRequest reference](/docs/reference/co 
      356 | [HTTPRoute reference](/docs/reference/co 

>> 2 spelling errors found in 466 files
To learn how to address spelling errors, please see https://istio.io/about/contribute/creating-and-editing-pages/#linting
Running ["OpenGraphCheck", "ScriptCheck", "HtmlCheck", "LinkCheck", "ImageCheck"] on ["./public"] on *.html... 

To fix these, place HTTPMatchRequest and HTTPRoute in backticks. Its annoying that our infrastructure requires backticks for links.

Copy link
Copy Markdown
Member

@sdake sdake left a comment

Choose a reason for hiding this comment

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

@LisaFC - thanks for the stellar contribution! I left a bunch of semi-nitpicky comments. I am not finished with the review. I have a meeting now and will conclude my review once my meetings clear up for the day.

All service meshes and, by extension, Istio seeks to automate complex infrastructure operations, like networking and security. That means there will always be complexity in its APIs, but Istio will always aim to solve the needs of operators, while continuing to evolve the API to provide robust building blocks and prioritize flexibility through role-centric abstractions.

We can't wait for you to join our [community](/about/community/join/) to see what you build with Istio next! No newline at end of file
We can't wait for you to join our [community](/about/community/join/) to see what you build with Istio next!
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Please revert this change. At some point we may make the blogs autodate based upon git timestamps - and the timestamp would be incorrect.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Ah, sorry, I think this got sucked in from an old copy. Will fix.

[observability](/docs/concepts/observability/) features, helps make your application
more robust against failures of dependent services or the network.

Istio’s traffic management model relies on the {{< gloss >}}Envoy{{</ gloss >}}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

along with your services is a little vague, but I'm not sure how to add enough detail without blowing people up with too much detail.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

"as sidecars to your services"?


Istio’s traffic management model relies on the {{< gloss >}}Envoy{{</ gloss >}}
proxies that are deployed along with your services. All traffic that your mesh
services send and receive ({{< gloss >}}data plane{{</ gloss >}} traffic) is proxied through Envoy, making
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

parenthesis in the docs is generally discouraged. Perhaps a better approach would be to rework this sentence a bit such as All data-plane traffic within your service mesh is proxied through Envoy. This proxy model makes it easy for you to direct and control traffic within your mesh without making any changes to your services.

this simplifies the sentence a bit and makes it less complex to understand.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Will what "data plane traffic" means be obvious to all readers? The main reason for the parenthesized bit is to convey "this traffic is also referred to as data plane traffic" (though I have just added data plane to the glossary, so that might mitigate)


If you’re interested in the details of how the features described in this guide
work, you can find out more about Istio’s traffic management architecture in the
[Architecture](#architecture) section at the end of this document. The rest of
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This wording is a little clunky for a link. How about something like "If you are interested in the details of traffic management, please reference the architecture(link).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I think that loses a little of the meaning - it's less the details of traffic management, more the details of how traffic management works (ie the implementation part). How about:

If you're interested in the details of how Istio's traffic management works, you can find out more in the Architecture section.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Don't lose the emphasis in the sentence that this guide is focused on "features", not architecture.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

How about:

If you're interested in the details of how the features described in this guide work, you can find out more in....

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Yes, remove the "about Istio’s traffic management architecture" part. That works.

Istio service registry, they are simply virtual destinations. This lets you model
traffic for virtual hosts that don't have routable entries inside the mesh.

#### Routing rules {#routing-rules}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

note to self - review from here forward.

@frankbu
Copy link
Copy Markdown
Collaborator

frankbu commented Sep 20, 2019

@LisaFC, @sdake: I think we're getting far too picky with grammatical details now. Unless somebody spots any more technical inaccuracies, I would like to merge this now. We can always improve it further in future iterations.

I'll approve/merge this today if there are no serious objections.

@sdake
Copy link
Copy Markdown
Member

sdake commented Sep 20, 2019

@frankbu understood. I didn't intend to be difficult, I just wanted the best content possible.

@LisaFC apologies if I came across too strong :)

Cheers
-steve

Copy link
Copy Markdown
Collaborator

@frankbu frankbu left a comment

Choose a reason for hiding this comment

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

This looks good to merge now. Further improvements can be made in followup PRs.

@istio-testing istio-testing merged commit 1ecc6cf into istio:master Sep 20, 2019
@frankbu
Copy link
Copy Markdown
Collaborator

frankbu commented Sep 20, 2019

/cherrypick release-1.3

@istio-testing
Copy link
Copy Markdown
Contributor

@frankbu: #5014 failed to apply on top of branch "release-1.3":

Applying: Updated traffic management guide
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	content/en/blog/2019/evolving-istios-apis/index.md
Falling back to patching base and 3-way merge...
Auto-merging content/en/blog/2019/evolving-istios-apis/index.md
CONFLICT (content): Merge conflict in content/en/blog/2019/evolving-istios-apis/index.md
Patch failed at 0002 Updated traffic management guide

Details

In response to this:

/cherrypick release-1.3

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.

@LisaFC
Copy link
Copy Markdown
Contributor Author

LisaFC commented Sep 23, 2019

Is there anything I can do to fix the not-mergeable-with-1.3 thing?

@frankbu
Copy link
Copy Markdown
Collaborator

frankbu commented Sep 23, 2019

@LisaFC It looks like the change to content/en/blog/2019/evolving-istios-apis/index.md (which ironically isn't really a change at all) breaks the automatic cherrypick to the release-1.3 branch. If you send another PR to branch release-1.3 manually (with just the 6 changed files), that would be great.

@LisaFC
Copy link
Copy Markdown
Contributor Author

LisaFC commented Sep 23, 2019

Will do.

@LisaFC
Copy link
Copy Markdown
Contributor Author

LisaFC commented Sep 23, 2019

#5042

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/networking cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. kind/docs ok-to-test Set this label allow normal testing to take place for a PR not submitted by an Istio org member. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants