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
Update Service Mesh docs #27231
Update Service Mesh docs #27231
Conversation
b9f31ce
to
e5d6c48
Compare
ff43490
to
d361770
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.
Small nit and a suggestion but overall an LGTM for me
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.
Well done! Really well written! I just have a couple of small nits and suggestions for you.
create multiple CECs that modify the same parts of Envoy's config, the results | ||
may be unpredictable. | ||
* In addition to this minimal validation, ``CiliumEnvoyConfig`` has minimal | ||
feedback to the user about the correctness of the configuration. So in the |
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.
Small grammar nit
feedback to the user about the correctness of the configuration. So in the | |
feedback to the user about the correctness of the configuration. In the |
95631e7
to
b55ecdb
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.
Awesome looks good!
Hey @youngnick, two questions for you:
|
Yes, no problem about squashing (although I'll keep another branch with the individual commits to make those backports easier). And yes, I can handle backporting. |
b55ecdb
to
8a4941b
Compare
Update Service Mesh landing page with extra explanation of what Service Mesh is. Add CiliumEnvoyConfig caveats to docs. Update details about Ingress annotation copying. Add Gateway API basic explanation to docs. Add Operators role in service mesh features to docs Signed-off-by: Nick Young <nick@isovalent.com>
8a4941b
to
a0296c3
Compare
/test |
Updates Service mesh docs to add some more explanation and cover some features more correctly. Each change is in a separate commit.
I was fixing #27167 when I noticed some other things that were missing, so I've hit all the ones I can find while I'm at it.
Fixes: #27167