Configuration reference Innovation Release

Core configuration options:

ParameterDescriptionDefaultRequired
agentConfig.accessKeyHM machine user access key""Yes
agentConfig.projectIDHM project ID""Yes
agentConfig.beaconServer.hostHM server hostname""Yes
agentConfig.locationIDAgent location identifier"standalone-k8s"Yes
namespaceKubernetes namespace"upm-beacon"No
image.repositoryBeacon agent image""Yes
image.tagBeacon agent version""Yes
otelImage.repositoryOTEL collector image""Yes (if OTEL enabled)
otelImage.tagOTEL collector version""Yes (if OTEL enabled)
additionalCharts.cert-manager.installEnable cert-manager subchartfalseNo
additionalCharts.opentelemetry-collector.installEnable opentelemetry-collector subchartfalseNo
additionalCharts.kube-state-metrics.installEnable kube-state-metrics subchartfalseNo
additionalCharts.prometheus-node-exporter.installEnable prometheus-node-exporter subchartfalseNo
opentelemetry-collector.image.repositoryOTEL collector image repository""Yes (if OTEL enabled)
opentelemetry-collector.image.tagOTEL collector image tag""Yes (if OTEL enabled)
agentConfig.metrics.kubeStateMetrics.endpointCustom kube-state-metrics scrape target (host:port). Leave empty to use the bundled subchart. Set this when using a pre-existing installation, for example, OpenShift's openshift-monitoring.""No

TLS configuration options

These options control how the agent trusts the Hybrid Manager (HM) beacon server certificate. By default (rootCAEnabled: true), the agent mounts a Certificate Authority (CA) secret and verifies HM using that certificate.

ParameterDescriptionDefaultRequired
rootCAEnabledWhen true, mounts the CA secret and sets the agent's root_ca_path. Set to false to trust HM via the system CA pool (or skip verification) without mounting a CA secret.trueNo
rootCASecretNameName of the secret holding the HM root CA (ca.crt). Must exist when rootCAEnabled is true.beacon-server-caNo
rootCAPEM-encoded root CA. When set, the chart creates the CA secret for you instead of requiring a pre-existing one.""No
agentConfig.beaconServer.rootCAPathPath inside the pod where the CA certificate is mounted and read from. Only used when rootCAEnabled is true./etc/ssl/certs/ca-certificates.crtNo
agentConfig.beaconServer.tlsInsecureSkipVerifyWhen true, the agent skips TLS verification of the HM beacon server certificate. Typically paired with rootCAEnabled: false for testing.falseNo
agentConfig.beaconServer.plaintextWhen true, the agent connects to HM without TLS.falseNo
Note

When rootCAEnabled: false, you don't need to create the beacon-server-ca secret described in the requirements. The agent relies on the system CA pool (or skips verification when tlsInsecureSkipVerify: true), and the CA volume mount is not injected into the agent, OpenTelemetry (OTEL) collector, or CloudNativePG™ sidecar pods.