docs: clarify OpenShift runAsUser must be explicitly set to null

[AlexKantor87]

Summary

• Clarifies that for OpenShift environments with SCC, runAsUser must be explicitly set to null in the values override
• Simply omitting the field does not work because Helm deep-merges with chart defaults, so runAsUser: 1000 always survives
• Adds a concrete example in the values.yaml comments showing the correct OpenShift override
• Regenerated README.md and docs site Helm page via helm-docs

Verified with helm template:

• Omitting runAsUser from override → runAsUser: 1000 still rendered ❌
• Setting runAsUser: null in override → runAsUser absent from output ✅

Prompted by customer feedback from Erik Weber.

Test plan

• helm template with runAsUser: null produces spec without runAsUser
• helm template with default values still renders runAsUser: 1000
• Docs site renders updated description for reporterConfig.securityContext.runAsUser

🤖 Generated with Claude Code

[claude]

Claude finished @AlexKantor87's task in 2m 42s —— View job

---

PR Review: docs: clarify OpenShift runAsUser must be explicitly set to null

• Run static analysis (build, vet, mod tidy)
• Read and review changed files
• Post review feedback

---

Static Analysis

All checks pass — go build ./..., go vet ./..., and go mod tidy produced no issues. This is expected for a docs-only change.

Review Summary

This PR looks good. The core fix is accurate and addresses a real user pain point.

Why it's correct: The template in cronjob.yaml:64 uses hasKey to conditionally render runAsUser. In Helm 3, setting a value to null in the override removes the key from the merged map during coalesceTables, so hasKey returns false and the field is omitted from the rendered output. Simply omitting runAsUser from the override does not remove it — Helm deep-merges with chart defaults, keeping runAsUser: 1000. The docs now correctly explain this distinction.

What's good:

• The values.yaml comment block (lines 73–82) includes a concrete, copy-pasteable OpenShift override example — exactly what a user hitting this issue needs
• The explanation of why omitting doesn't work (Helm deep-merge) is valuable and prevents users from re-discovering this the hard way
• README.md and docs.kosli.com/content/helm/_index.md are identical, confirming proper helm-docs regeneration
• Bonus: the dryRun field now has a description (was previously empty in the README table)

Minor observations (not blocking):

• The securityContext row in the README table is quite dense after the description expanded. This is a helm-docs limitation (flattens multi-line comments into a single cell). The source of truth (values.yaml) reads well, which matters most.
• The helm-docs version bumped from v1.5.0 to v1.14.2 — this is fine and expected if a newer version was used to regenerate.

No bugs, security issues, or correctness concerns found.

[claude]

Nice improvement. The example block (lines 79–82) is a great addition — it makes the correct override instantly copy-pasteable for OpenShift users.

[claude]

Nit: The securityContext description in this table cell is quite dense now that it includes the full example. This is a limitation of helm-docs flattening multi-line comments into a single cell, so there's not much to do here — just flagging for awareness. The source of truth (values.yaml) reads well, which is what matters most.