Kubernetes Agent v1.9.30

Includes Java Agent v2.2.68

October 2, 2026

Caution

Update both the master agent and node agent to 1.9.30. There are no additional configuration or RBAC changes.

• Changed Aligned pod container aggregation with the actual collection targets

  • Aggregates container identifiers, names, counts, and states over the same set as the actual container collection targets.
  • Includes regular containers, native sidecars, and pods with no containers.

• Changed Added a Yard version check when connecting to the collection server

  • Uses the new pod container aggregation format only on projects confirmed to run Yard 3.1.9 or later.
  • Keeps the existing transmission format on older Yard versions, and when the version query is unsupported, fails, or times out.
  • On reconnection, pending data is also sent in the format that matches the server version of the current connection.
  • The version query runs once per connection for each of the node agent and master agent, and isn't retried periodically.

• Fixed Improved the stability of abnormal version response handling and connection recovery after communication failures

Upgrade note for on-premises deployments: [Y106] logs on older Yard versions

If you use Kubernetes Agent 1.9.30 with Yard 3.1.8 or earlier, those versions don't support the collection server version query, so [Y106] errors and stack traces may appear in the Yard log.

Logs caused by the unsupported version query don't affect existing data collection, and the agent keeps the existing transmission format. Updating to Yard 3.1.9 or later, which includes the version query, resolves logs from this cause.

Because the version query runs only once per connection, the logs may appear again whenever a new connection is created.

• The agent pod restarts or is redeployed
• The proxy restarts
• The agent reconnects after a network outage

In environments that go through a proxy, if the connection between the agent and the proxy is kept, restarting only Yard doesn't make the agent query the version again.

Caution

[Y106] is also used for other exceptions. Don't ignore every [Y106] log. Check whether the exception recorded with it corresponds to the unsupported version query.

How to upgrade and scope

• Update both the master agent and node agent to 1.9.30. There are no additional configuration or RBAC changes.
• To use the new pod container aggregation, Yard 3.1.9 or later, which includes the version query and pod aggregation preservation, must be in place first. After updating Yard, reconnect or restart the agent so that it checks the version again.
• If only Yard is replaced behind the same proxy connection, the agent doesn't detect the version change. An upgrade with mixed Yard versions requires separate coordination.
• The existing transmission format is kept for namespace or child projects whose version hasn't been separately confirmed.

Note

This release doesn't imply that the server update and the actual collection and screen verification have been completed for any particular customer environment.

Info

Agent download: kube_mon_1.9.30.tar