openshift-docs
openshift-docs copied to clipboard
openshift
[WIP] OSSM-8268: Getting traffic into the mesh
Affects:
service-mesh-docs-main service-mesh-docs-3.0.0tp1
This PR is part of the standalone doc set for the Service Mesh 3.0 project. Kathryn is aware that this content applies for a product that is part of a Technology Preview release. The project is seeking feedback from early adopters.
PR must be CP'd back to the tp1 branch.
Version(s): Tech Preview
Issue: https://issues.redhat.com/browse/OSSM-8268
Link to docs preview: https://83901--ocpdocs-pr.netlify.app/openshift-service-mesh/latest/gateways/ossm-getting-traffic-into-a-mesh.html
QE review:
- [ ] QE has approved this change.
Additional information:
@rh-tokeefe: This pull request references OSSM-8268 which is a valid jira issue.
In response to this:
Version(s):
Issue: https://issues.redhat.com/browse/OSSM-8268
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Additional information:
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 openshift-eng/jira-lifecycle-plugin repository.
🤖 Thu Oct 31 19:20:43 - Prow CI generated the docs preview:
https://83901--ocpdocs-pr.netlify.app/openshift-service-mesh/latest/gateways/ossm-getting-traffic-into-a-mesh.html
@rh-tokeefe: This pull request references OSSM-8268 which is a valid jira issue.
In response to this:
Affects:
service-mesh-docs-main service-mesh-docs-3.0.0tp1
This PR is part of the standalone doc set for the Service Mesh 3.0 project. Kathryn is aware that this content applies for a product that is part of a Technology Preview release. The project is seeking feedback from early adopters.
PR must be CP'd back to the tp1 branch.
Version(s): Tech Preview
Issue: https://issues.redhat.com/browse/OSSM-8268
Link to docs preview: https://83901--ocpdocs-pr.netlify.app/openshift-service-mesh/latest/gateways/ossm-getting-traffic-into-a-mesh.html
QE review:
- [ ] QE has approved this change.
Additional information:
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 openshift-eng/jira-lifecycle-plugin repository.
@rh-tokeefe: This pull request references OSSM-8268 which is a valid jira issue.
In response to this:
Affects:
service-mesh-docs-main service-mesh-docs-3.0.0tp1
This PR is part of the standalone doc set for the Service Mesh 3.0 project. Kathryn is aware that this content applies for a product that is part of a Technology Preview release. The project is seeking feedback from early adopters.
PR must be CP'd back to the tp1 branch.
Version(s): Tech Preview
Issue: https://issues.redhat.com/browse/OSSM-8268
Link to docs preview: https://83901--ocpdocs-pr.netlify.app/openshift-service-mesh/latest/gateways/ossm-getting-traffic-into-a-mesh.html
QE review:
- [x] QE has approved this change.
Additional information:
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 openshift-eng/jira-lifecycle-plugin repository.
@rh-tokeefe: all tests passed!
Full PR test history. Your PR dashboard.
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-sigs/prow repository. I understand the commands that are listed here.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@rh-tokeefe I have a few comments, formatting things. I don't think any of them are enough to stop the merge, especially as this is TP. Maybe make any changes in a follow-up PR.
@mburke5678: new pull request created: #84346
In response to this:
/cherrypick service-mesh-docs-3.0.0tp1
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-sigs/prow repository.
