Kubernetes Agent v1.9.31

Includes Java Agent v2.2.68

October 6, 2026

Caution

Update the node agent and master agent images, including node helper, to 1.9.31 together. Don't update only the node agent and leave node helper on an older version. This improvement requires no separate operator upgrade or RBAC change.

• Changed Links Java APM with the container ID even when WHATAP_JAVA_AGENT_PATH is set through a ConfigMap

  • node helper now links Java APM with the container ID even when the application container sets WHATAP_JAVA_AGENT_PATH through env[].valueFrom.configMapKeyRef.
  • Uses the environment variable as resolved when the container started, so it isn't confused with a ConfigMap value changed after startup.
  • The existing fallbacks, such as setting value directly and automatic path detection, remain unchanged.
  • No ConfigMap or Secret read permissions are added.
  Note

  The supported form is an individual env[].valueFrom.configMapKeyRef. Bulk imports through envFrom.configMapRef and other valueFrom forms aren't included, and this is separate from the Java APM auto-install feature.

How to apply

Set the ConfigMap value to the absolute path of the actual Java agent JAR inside the application container.

env:
  - name: WHATAP_JAVA_AGENT_PATH
    valueFrom:
      configMapKeyRef:
        name: whatap-configmap
        key: WHATAP_JAVA_AGENT_PATH

• Keep the existing integration settings such as POD_NAME, along with the JAR and Java execution permissions and the directory write permission.
• Applications already running with a correct ConfigMap reference don't need the environment variable changed to a direct value.
• If you change the ConfigMap value, recreate the application pod for the environment variable to pick it up.
• After applying it, check the actual APM container ID mapping and the container CPU metrics.

Note for on-premises deployments

This feature itself doesn't require a Yard update. However, the Yard version check introduced in 1.9.30 still applies.

A [Y106] caused by an older Yard not supporting the version query doesn't stop existing collection, but you need to distinguish it from a [Y106] with a different cause. Logs from this cause are resolved once you update to Yard 3.1.9 or later, which supports the version query, and the agent establishes a new connection.

Info

Agent download: kube_mon_1.9.31.tar