General
Affinity rules for scheduling the reporter pod. Supports nodeAffinity, podAffinity and podAntiAffinity.
Specifies how to treat concurrent executions of a Job that is created by this CronJob.
Overrides the fullname used for the created k8s resources. It has higher precedence than
nameOverride.Existing Secrets in the same namespace used to pull the reporter image, e.g. from a private registry mirror.
Overrides the name used for the created k8s resources. If
fullnameOverride is provided, it has higher precedence than this one.Node labels for scheduling the reporter pod. On EKS with Karpenter, use this to pin the reporter to a stable managed node group (e.g.
eks.amazonaws.com/nodegroup: <name>) so it does not interfere with node consolidation. See Running on EKS with Karpenter.Annotations to add to the CronJob object itself. For pod-level annotations (added to each reporter pod), use
podTemplateAnnotations instead.The pod-level security context for the reporter, rendered verbatim, for pod-only fields such as
fsGroup or supplementalGroups.Annotations to add to the reporter pod template (applied to each Job pod that the CronJob creates).
Tolerations for scheduling the reporter pod, e.g. to run on a dedicated or tainted node group.
Image
The kosli reporter image tag, overrides the image tag whose default is the chart appVersion.
Reporter configuration
Create each Kosli environment (type K8S) if it does not already exist, before reporting the snapshot.
Whether the dry run mode is enabled or not. In dry run mode, the reporter logs the reports to stdout and does not send them to kosli.
Description applied to every environment auto-created in this run. Only used when
autoEnvironment is true; existing environments are never modified. Note: a single value is shared by all environments created during the run.List of Kosli environments to report to. Each entry has required ‘name’ and optional namespace selectors. Use one entry to report a single environment; use multiple entries to report to multiple environments with different selectors. Per entry: name (required), namespaces, namespacesRegex, excludeNamespaces, excludeNamespacesRegex (optional). Leave namespace fields unset for an entry to report the entire cluster to that environment.
Deprecated and ignored — used to control whether scaling (replica count) changes were recorded for environments auto-created in this run. Scaling events no longer trigger new snapshots and an environment can no longer have scaling capture turned on, so the
--include-scaling / --exclude-scaling flags this passed to the CLI had stopped having any effect. As of chart version 2.7.0 the flags are no longer passed. Setting this value does nothing; remove it from your values.The container-level security context for the reporter, rendered verbatim. Set to null to disable security context entirely (not recommended). Pod-only fields such as
supplementalGroups belong in podSecurityContext. For OpenShift with SCC, explicitly set runAsUser to 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 these defaults. Example OpenShift override: securityContext: allowPrivilegeEscalation: false runAsNonRoot: true runAsUser: null Example for a namespace enforcing the restricted Pod Security Standard: securityContext: capabilities: drop: [ALL] seccompProfile: type: RuntimeDefault.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.
Kosli API token
Environment variables
Map of plain environment variables to inject into the reporter container. For a single-tenant Kosli instance, set
KOSLI_HOST to https://INSTANCE_NAME.kosli.com.Additional environment variables to inject into the reporter container. List of
{name, value} or {name, valueFrom} entries, rendered verbatim into the container env. Supports plain values and valueFrom (secretKeyRef / configMapKeyRef). Note: entries here are appended after the chart’s own env entries; on duplicate names the later entry wins.Volumes
Additional container-level volumeMounts for the reporter container. Rendered verbatim into the container spec alongside the chart’s own mounts.
Additional Pod-level volumes to attach to the reporter pod. Rendered verbatim into the Pod spec alongside the chart’s own volumes. Use together with
extraVolumeMounts to mount Secrets, ConfigMaps, or other volumes into the container.Custom CA
Convenience wrapper for mounting a corporate / custom CA bundle. See Running behind a TLS-inspecting proxy for usage.
Key within the Secret that holds the PEM-formatted CA certificate (single cert or multi-cert PEM bundle).
Resources
Service account
The name of the service account to use. If not set and create is true, a name is generated using the fullname template.
Specifies whether to create cluster-wide permissions for the service account or namespace-scoped permissions. Allowed values are:
cluster or namespace.Autogenerated from chart metadata using helm-docs v1.14.2.