Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

Document support for different application traffic types #82

Closed
shashankram opened this issue Jan 22, 2021 · 2 comments
Closed

Document support for different application traffic types #82

shashankram opened this issue Jan 22, 2021 · 2 comments
Assignees
Milestone

Comments

@shashankram
Copy link
Member

shashankram commented Jan 22, 2021

**Please describe what should be documented
The different supported application traffic types should be documented. Currently, HTTP, TCP, and gRPC applications have been tested. Document how the application protocol is inferred by OSM to allow traffic filtering and routing.

**Please suggest where in the repo the document should be located
Possibly: https://docs.openservicemesh.io/docs/tasks_usage/traffic_management/

However, this could also be under a folder that describes application requirements and feature support.

@shashankram shashankram self-assigned this Feb 1, 2021
@bridgetkromhout bridgetkromhout transferred this issue from openservicemesh/osm May 21, 2021
@shashankram
Copy link
Member Author

Partly documented at https://docs.openservicemesh.io/docs/guides/app_onboarding/app_protocol_selection/.

Issue is open to track documentation for how policies and services need to be configured for different application protocols.

@shashankram shashankram added this to the v1.0.0 milestone Sep 23, 2021
@shashankram shashankram removed their assignment Oct 5, 2021
@shashankram
Copy link
Member Author

App protocol selection is documented at https://main--osm-docs.netlify.app/docs/guides/app_onboarding/app_protocol_selection/, which describes support for different application traffic protocols.

Additionally, TCP traffic demo has been added at https://main--osm-docs.netlify.app/docs/demos/tcp_traffic_routing/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants