You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: update Helm chart reference to v2.2.1 (#199)
## Summary
- Update the `.mdx` Helm chart reference to v2.2.1: version badge, info
callout, and `image.tag` default (empty string, not hardcoded CLI
version)
- Fix misleading OpenShift `securityContext` guidance — users must
explicitly set `runAsUser: null`, not omit it (Helm deep-merges the
default `1000` back in)
The auto-generated `.md` file remains unchanged. Upstream fix to make it
Mintlify-compatible (remove `{.command}` fences, escape
`<instance_name>`) is tracked in kosli-dev/cli#853.
## Test plan
- [ ] Verify `helm/k8s_reporter` renders correctly at
http://localhost:3000/helm/k8s_reporter
- [ ] Check version badge shows 2.2.1
The security context for the reporter cronjob. Set to null or `{}` to disable security context entirely (not recommended). For OpenShift, you can omit `runAsUser` to let OpenShift assign the UID.
233
+
The security context for the reporter cronjob. Set to null or `{}` to disable security context entirely (not recommended). For OpenShift with SCC, explicitly set `runAsUser: null` to let OpenShift assign the UID from the allowed range. Simply omitting `runAsUser` from your values override will not work because Helm deep-merges with the chart defaults.
236
234
237
235
Default:
238
236
```json
@@ -253,7 +251,7 @@ If you already run [cert-manager's trust-manager](https://cert-manager.io/docs/t
The user id to run as. Omit this field for OpenShift environments to allow automatic UID assignment.
254
+
The user id to run as. For OpenShift environments with SCC, set to `null` (`runAsUser: null`) to allow automatic UID assignment. Simply omitting this field will not work due to Helm's deep merge with chart defaults.
0 commit comments