-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSSMDOC-147: Add troubleshooting page. #29410
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
Conversation
✔️ Deploy Preview for osdocs ready! 🔨 Explore the source changes: ff44190 🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/6143f28c362d5700071c8c2e 😎 Browse the preview: https://deploy-preview-29410--osdocs.netlify.app |
d80e127
to
2799178
Compare
e86cff1
to
cd52a1f
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.
This says OSSM is unlike the upstream, but the first heading mentions Istio, which might be confusing. I also notice that the paragraphs underneath both the istio and jaeger sidecar injection are broadly similar. Is it possible to just combine those into one paragraph. So instead of Troubleshooting sidecar injection with two subheads,
= Troubleshooting sidecar injection
Unlike how the upstream Istio community configures proxy sidecars using namespace labels, {ProductName} does not automatically inject proxy sidecars to pods. You must opt in to sidecar injection.
Check to see if automatic injection is enabled in the Deployment for your application. If automatic injection for the Envoy proxy is enabled, there should be a
sidecar.istio.io/inject:"true"
andsidecar.jaegertracing.io/inject:"true"
annotation in the Deployment resource underspec.template.metadata.annotations
.
I had one more thought here. This module has an explanation for what a sidecar injection is and how to fix it, but it doesn't mention the symptom. Many troubleshooting topics start with the symptom and then reveal the cure. What is the symptom? How do I know I have a sidecar injection problem?
a342401
to
a011b46
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.
It looks like some of these were accepted here but marked resolved without incorporating in the above topic; probably best to keep them consistent?
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.
I have no idea what this comment means. I've made these changes, are they not showing up for you? Maybe a caching issue?
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.
some additional comments
a011b46
to
288d8f7
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.
I think this is good as a first revision that we can build on over time.
288d8f7
to
077eb22
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.
Some comments, mostly minor nits and formatting things 🙂
Great job!
077eb22
to
42fa637
Compare
42fa637
to
ff44190
Compare
/cherry-pick enterprise-4.6 |
/cherry-pick enterprise-4.7 |
/cherry-pick enterprise-4.8 |
/cherry-pick enterprise-4.9 |
@JStickler: new pull request created: #36471 In 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. |
@JStickler: new pull request created: #36472 In 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. |
@JStickler: new pull request created: #36473 In 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. |
@JStickler: new pull request created: #36474 In 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. |
First draft for a Service Mesh troubleshooting page.
This is not intended to be exhaustive, but rather to start the page with a couple of basic scenarios that we can then add to over time.
Also moves the Support and Must Gather topics out of the Release Notes.
REVISION
Added topic about Service Mesh versioning (OSSMDOC-176 and OSSMDOC-201)
Added additional context around expected behavior (Validation topics).
Preview is here -> https://deploy-preview-29410--osdocs.netlify.app/openshift-enterprise/latest/service_mesh/v2x/ossm-troubleshooting-istio.html