Updated traffic management concept guide#5014
Conversation
|
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 Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
/ok-to-test |
howardjohn
left a comment
There was a problem hiding this comment.
Looks great, left a few nitpick comments
Co-Authored-By: John Howard <howardjohn@google.com>
Co-Authored-By: John Howard <howardjohn@google.com>
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
|
/retest |
Implementing Frank's suggestions
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
|
@LisaFC - linting errors: To fix these, place HTTPMatchRequest and HTTPRoute in backticks. Its annoying that our infrastructure requires backticks for links. |
| 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! |
There was a problem hiding this comment.
Please revert this change. At some point we may make the blogs autodate based upon git timestamps - and the timestamp would be incorrect.
There was a problem hiding this comment.
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 >}} |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
"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 |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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).
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Don't lose the emphasis in the sentence that this guide is focused on "features", not architecture.
There was a problem hiding this comment.
How about:
If you're interested in the details of how the features described in this guide work, you can find out more in....
There was a problem hiding this comment.
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} |
There was a problem hiding this comment.
note to self - review from here forward.
frankbu
left a comment
There was a problem hiding this comment.
This looks good to merge now. Further improvements can be made in followup PRs.
|
/cherrypick release-1.3 |
|
@frankbu: #5014 failed to apply on top of branch "release-1.3": DetailsIn response to this:
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. |
|
Is there anything I can do to fix the not-mergeable-with-1.3 thing? |
|
@LisaFC It looks like the change to |
|
Will do. |
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