v0.30.4

This release contained no user-facing changes.

v0.30.3

New Features

• Add a new stat to each syncer which records the duration of each call to Sync(). This stat will be exposed as a histogram in the Prometheus metrics. Specifically under the name '<syncer_name>_sync_time_sec'. Additionally it will expose a label to drill down to the individual syncers as there may be multiple. This label is 'syncer_name'. The syncer itself will be exposed as the type name. (solo-io/gloo#6780)

Fixes

• Improve scalability of v2 status reporter by using k8s patch instead of read then write. Also updates the status written to render enums as strings rather than ints for readability. (solo-io/gloo#7076)

v0.30.2

Fixes

• AllowUnknownFields when unmarshalling a kube spec into a resource. Previously,
  unknown fields would cause an error. This is safe, because for the spec to be persisted
  in the first place, it must respect the CRD validation schema definition. (#505)

v0.24.8

Fixes

• AllowUnknownFields when unmarshalling a kube spec into a resource. Previously,
  unknown fields would cause an error. This is safe, because for the spec to be persisted
  in the first place, it must respect the CRD validation schema definition. (#505)

v0.22.3

New Features

• Add ExpressionSelector to ListOpts and WatchOpts.
  This adds support to set-based label selection on resource clients, allowing selection
  of resources with multiple values for the same key. Previously, only equality-based
  label selection was supported, which required a single key and value for all defined requirements. (solo-io/gloo#6406)

Fixes

• AllowUnknownFields when unmarshalling a kube spec into a resource. Previously,
  unknown fields would cause an error. This is safe, because for the spec to be persisted
  in the first place, it must respect the CRD validation schema definition. (#505)

v0.20.11

This release contained no user-facing changes.

v0.20.10

New Features

• Add ExpressionSelector to ListOpts and WatchOpts.
  This adds support to set-based label selection on resource clients, allowing selection
  of resources with multiple values for the same key. Previously, only equality-based
  label selection was supported, which required a single key and value for all defined requirements. (solo-io/gloo#6406)

Fixes

• AllowUnknownFields when unmarshalling a kube spec into a resource. Previously,
  unknown fields would cause an error. This is safe, because for the spec to be persisted
  in the first place, it must respect the CRD validation schema definition. (#505)

v0.24.7

Fixes

• Ensure that the emitter namespaced map is hydrated with the initial list data. (solo-io/gloo#5554)

v0.30.1

Fixes

• Ensure that the emitter namespaced map is hydrated with the initial list data. (solo-io/gloo#5554)

v0.30.0

Fixes

• Ensure that StatusUnmarshal never returns an error. Instead, if an error would occur, set an empty status on the resource. (#484)