Release Guide

This guide has details about the current and planned releases of Stackdriver Kubernetes Monitoring during the Beta period.

Release versions

The current releases and updates of Stackdriver Kubernetes Monitoring are listed below with the most recent release listed first:

  • Beta Update (Kubernetes 1.10.6 / 1.11.2): This update is strongly recommended for all users. To upgrade to this release, see Installing Kubernetes Monitoring. More details are provided in Beta update 1.10.6 on this page.

  • Original Beta (Kubernetes 1.10.2): Due to a number of known issues, this release is not recommended for any purpose.

    If you must use Kubernetes versions 1.10.2 through 1.10.5, then you must use the Manual Installation instructions to install an updated version of this release.

Features and known issues

This section lists the known issues in the current Beta release versions.

Beta update 1.10.6

This is the current recommended release, available on GKE with Kubernetes version 1.10.6 and 1.11.2 (when available). To upgrade to this release, see Installing Kubernetes Monitoring.

Specifically, the release:

  • Fixes most of the known issues with the 1.10.2 release.
  • Restores the ability to install the managed support for Stackdriver Kubernetes Monitoring.
  • Lets you upgrade existing clusters with Stackdriver Kubernetes Monitoring.
  • Removes the need for any manual installation on GKE.

The following issues remain as of August 15, 2018:

  1. "Unscheduled pods" are not displayed.

    The Containers UI does not display unscheduled pods. Unscheduled pods can be identified by the following metadata label:

    "node_name" = ""
    

    Schedule: Not yet available. This is a feature addition.

  2. Stackdriver metadata agent restarts

    In the Beta release, the metadata agent can restart once per hour in normal operation, and might restart several times in succession.

    Schedule: Not yet available.

    Workaround: Do not worry about restart counts for the metadata agent.

Beta release 1.10.2

These issues are current as of August 10, 2018.

  1. Missing resource entries

    You might not see all your namespaces, workloads, pods, or other entities in Stackdriver Kubernetes Monitoring. This is due to a problem in gathering metadata. It can take up to 30 minutes for the missing entities to be found. They appear after refreshing the display.

    Fixed in Kubernetes versions 1.10.6 and 1.11.2.. You can also use the Manual Installation steps to install newer versions of Heapster and the Stackdriver agents in a new cluster.

  2. Regional and multi-zonal clusters

    Entities belonging to regional and multi-zonal clusters are not displayed correctly. The Infrastructure, Workload, and Service tabs do not expand to the node/pod level for these clusters.

    Fixed in Kubernetes versions 1.10.6 and 1.11.2.. You can also use the Manual Installation steps to install newer versions of Heapster and the Stackdriver agents in a new cluster.

  3. Severity missing in log entries

    Log entries ingested by the logging agent are missing the severity field, which causes all log entries to show up with default severity (a gray star), breaking Error Reporting integration.

    Fixed in Kubernetes versions 1.10.6 and 1.11.2.. You can also use the Manual Installation steps to install newer versions of Heapster and the Stackdriver agents in a new cluster.

  4. Exception stack trace detection is broken

    Multi-line exception stack traces are split into multiple separate log entries, breaking Error Reporting integration.

    Fixed in Kubernetes versions 1.10.6 and 1.11.2.. You can also use the Manual Installation steps to install newer versions of Heapster and the Stackdriver agents in a new cluster.

  5. Irrelevant error messages from agents

    The metadata agent can write irrelevant error log messages after a previous instance of the agent shuts down incorrectly. The messages are:

    terminate called after throwing an instance of 'boost::exception_ ...'
    what():  Error listening on provided port.
    terminate called recursively
    Aborted (core dumped)
    

    Also, the logging agent will log Error calling Metadata Agent after the metadata agent terminates.

    Fixed in Kubernetes versions 1.10.6 and 1.11.2.. You can also use the Manual Installation steps to install newer versions of Heapster and the Stackdriver agents in a new cluster.

  6. Stackdriver agents don't work behind Compute Engine firewalls

    Stackdriver Kubernetes Monitoring does not work with clusters that are behind certain Compute Engine firewalls. In those situations, your metadata agent issues the following error message:

    Metadata request unsuccessful: Address family not supported by protocol.
    

    Fixed in Kubernetes versions 1.10.6 and 1.11.2.. You can also use the Manual Installation steps to install newer versions of Heapster and the Stackdriver agents in a new cluster.

  7. "Unscheduled pods" are not displayed.

    The Containers UI does not display unscheduled pods. Unscheduled pods can be identified by the following metadata label:

    "node_name" = ""
    

    Schedule: Not yet available. This is a feature addition.

  8. Stackdriver metadata agent restarts

    In the Beta release, the metadata agent can restart once per hour in normal operation, and might restart several times in succession.

    Schedule: Not yet available.

    Workaround: Do not worry about restart counts for the metadata agent.

Was this page helpful? Let us know how we did:

Send feedback about...

Stackdriver Monitoring