OSSM 9894_DNS capture#110676
Conversation
|
Skipping CI for Draft Pull Request. |
|
🤖 Fri Apr 24 12:48:32 - Prow CI generated the docs preview: |
4965aba to
1c4de2c
Compare
rh-tokeefe
left a comment
There was a problem hiding this comment.
Overall, looks pretty good, @lhite8041. You might want to consider updating the short description.
https://redhat-documentation.github.io/supplementary-style-guide/#shortdesc
Added new module documenting the requirement to explicitly configure DNS capture when migrating from Service Mesh 2.6 to 3.0 if using ServiceEntry resources for external services. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
df5465f to
11b14de
Compare
|
@lhite8041: all tests passed! Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
OSSM-9894: behavior change between OSSM 2.x and 3.x
PEER REVIEWER: Please note that this new module follows an established pattern in a migration guide that probably doesn't have a very long shelf life.
Version(s):
service-mesh-docs-3.0
Issue:
https://redhat.atlassian.net/browse/OSSM-9894
Link to docs preview:
https://110676--ocpdocs-pr.netlify.app/openshift-service-mesh/latest/migrating/checklists/ossm-migrating-read-me.html#ossm-migrating-read-me-dns-capture-configuration_ossm-migrating-read-me
QE review: