Release v2.4.0

• Add a new point tag called cluster_uuid to all our metrics, which reflects the UUID of the default namespace of the Kubernetes cluster.
• Enable faster Kubernetes Control Plane dashboard experience by using Operations for Applications histograms.

Component	Version
Wavefront Kubernetes Collector	1.16.0
Wavefront Proxy	12.1
Fluent Bit	2.0.8

Release v2.3.0

• Fix missing log message content
• Fix missing control plane metrics due to misconfigured RBAC access
• Update to use Go 1.18
• Control plane metrics can explicitly be enabled (default) and disabled

Component	Version
Wavefront Kubernetes Collector	1.15.0
Wavefront Proxy	12.1
Fluent Bit	2.0.8

Release v2.2.0

• Updates the logging agent to use Fluent Bit instead of Fluentd
  • Upgrading from older version of Wavefront Operator for Kubernetes to v2.2.0 will seamlessly upgrade your existing logging agents to Fluent Bit v2.0.8
  • For comparison see https://docs.fluentbit.io/manual/about/fluentd-and-fluent-bit
• Fixes a bug on collecting horizontal pod autoscaler metrics - kubernetes.hpa.*.
• Disables ServiceAccount token automounting. For more information, see Opts out of API credential automounting
• Adds GKE Arm 64 tolerations.
• Adds support for tolerations to data collection DaemonSet pods. For more information, see Defining data collection pod tolerations under Configuration.
• Adds support for custom logs shipper. For more information, see Bring Your Own Logs Shipper.
• Fixes a bug on sending logs to an external Wavefront proxy.
• Fixes OTLP documentation and configuration typo.
• Adds the level=ERROR label to Kubernetes logs from standard error.
• Adds the Integration=Kubernetes label to all logs collected by Wavefront Operator for Kubernetes logging agent.

Component	Version
Wavefront Kubernetes Collector	1.14.0
Wavefront Proxy	12.1
Fluent Bit	2.0.8

Release v2.1.1

• Fixes bug preventing the use of HTTP Proxy CA certificates.

Component	Version
Wavefront Kubernetes Collector	1.13.0
Wavefront Proxy	12.0

Release v2.1.0

• Adds internal logging metrics:
  • ~proxy.logs.*.received.messageLength: Size of log message fields before validation
  • ~proxy.logs.*.received.tagLength: Size of label per log message
  • ~proxy.logs.*.received.batches: Number of incoming batches of logs
• Adds new internal metrics tag hostname, with default tag value the FQDN of the proxy host.
• Adds support for forward slash ("/") in log tags (converts to underscore).
• Fixes a bug that prevented log tags with leading underscores from being accepted.
• Changes the default fields for hyperlogs to no longer include application, service, log level, and exception by default.
• Handles multiple API Server instances for the control plane
• In the case of multiple API Server instances for the control plane, the instance tag from the kubernetes.controlplane.apiserver.request.total.counter metric uniquely identifies the individual API Server instances with their IP addresses.
• Dropped tags to reduce the Too many point tags error. For more information, see Troubleshooting Dropped Metrics .

Component	Version
Wavefront Kubernetes Collector	1.13.0
Wavefront Proxy	12.0

Release v2.0.3

• User can enable OTLP support on the proxy

Release v2.0.2

• Report OOM crashes in health status (#275)
  • kubernetes.observability.status has message="OOMKilled in the last 5m" and status="Unhealthy"
  • kubernetes.observability.<resource name>.status has message="OOMKilled in the last 5m" and status="Unhealthy"

  •  $> kubectl get wavefront --namespace=observability-system
    
     NAME        STATUS        PROXY           CLUSTER-COLLECTOR   NODE-COLLECTOR   LOGGING         AGE   MESSAGE
     wavefront   Unhealthy     Running (1/1)   Unhealthy           Running (3/3)    Running (3/3)   2m4s  OOMKilled in the last 5m
    

• Split the component label to differentiate the node-collector / cluster-collector (#277)

Release v2.0.1

The operator simplifies operational aspects of managing the Wavefront integration

• Enhanced status reporting of the Wavefront integration so that users can ensure their cluster and Kubernetes resources are reporting data.
• Kubernetes Operator features provide a declarative mechanism for deploying the Wavefront Collector and proxy in a Kubernetes environment.
• Centralized configuration.
• Enhanced configuration validation to surface what needs to be corrected in order to deploy successfully.
• Efficient Kubernetes resource usage supports scaling out the cluster (leader) node and worker nodes independently.

To learn more or get started with the Operator, please visit our wavefront-operator-for-kubernetes repo.

For existing customers, please visit the migration doc.

Release v0.9.0

BETA release of the Wavefront operator for Kubernetes.