fix: Escape Markdown pipes

[z63d]

Description

There is a display problem because pipe is used in the Markdown table. The string after pipe is not displayed.
https://tetragon.io/docs/reference/helm-chart/
https://github.com/cilium/tetragon/blob/main/install/kubernetes/tetragon/README.md
Fix it by escaping pipe.

Also, if you escape pipe, the second half of the string will be recognized, and asterisk will make the following part bold.

**". For more control, you can select which binary or binaries should have their arguments redacted with the `binary_regex` field. NOTE: This feature uses RE2 as its regular expression library. Make sure that you follow RE2 regular expression guidelines as you may observe unexpected results otherwise. More information on RE2 syntax can be found [here](https://github.com/google/re2/wiki/Syntax). NOTE: When writing regular expressions in JSON, it is important to escape backslash characters. For instance `\Wpasswd\W?` would be written as `{"redact": "\\Wpasswd\\W?"}`. As a concrete example, the following will redact all passwords passed to processes with the "--password" argument: {"redact": ["--password(?:\\s+|=)(\\S*)"]} Now, an event which contains the string "--password=foo" would have that string replaced with "--password=**

So escape asterisk.

[netlify]

✅ Deploy Preview for tetragon ready!

Name	Link
🔨 Latest commit	b883533
🔍 Latest deploy log	https://app.netlify.com/sites/tetragon/deploys/67933b3047c8df0008376b30
😎 Deploy Preview	https://deploy-preview-3332--tetragon.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mtardy]

Oh, both those files are generated from the values, you could modify the comment there or fix the genrator.

[mtardy]

well this is not ideal since it eventually modify these regex (binary_regex) so that docs looks better but the direct docs on values isn't exact anymore. I'm afraid you'll have to fix the thing we use for the generation, it seems the issue already exists :/. This is a complete different task than just fixing this docs so don't feel like you have to fix this!

See:

• can helm-docs handle | in comments properly? norwoodj/helm-docs#118
• Pipe | breaks table output of values.yml norwoodj/helm-docs#171

[z63d]

Thanks! You are right.
Should I add this to the Issue?

[mtardy]

as you wish! if you don't consider fixing this other project's issue I might take a look eventually, tell me