v0.31.0

Dependency Bumps

• solo-io/go-list-licenses has been upgraded to v0.1.4.
• solo-io/go-utils has been upgraded to v0.24.0.
• solo-io/k8s-utils has been upgraded to v0.3.0.
• solo-io/protoc-gen-ext has been upgraded to v0.0.18.
• onsi/ginkgo/v2 has been upgraded to v2.5.0.
• onsi/gomega has been upgraded to v1.24.1.
• k8s.io/apiextensions-apiserver has been upgraded to v0.25.4.
• k8s.io/apimachinery has been upgraded to v0.25.4.
• k8s.io/client-go has been upgraded to v0.25.4.
• k8s.io/api has been upgraded to v0.25.4.
• k8s.io/code-generator has been upgraded to v0.25.4.
• golang/go has been upgraded to v1.18.2.

Breaking Changes

• Remove multicluster package, as it was not used by any projects (solo-io/gloo#7222)

v0.30.9

Fixes

• Fix error that would occur if a resource contained statuses for multiple namespaces. GetJsonPatchData now checks the POD_NAMESPACE environment variable to determine which namespace to modify, instead of erroring. (#529)

v0.30.8

This release contained no user-facing changes.

v0.30.7

Fixes

• Add escape hatches via env var for any users depending on large statuses (#523)

v0.30.6

Fixes

• Skip the status patch if it's too large to protect etcd and k8s communication. (#523)

v0.30.5

Fixes

• Truncate size of statuses written to k8s / etcd to protect against large keys stored in k8s backend. (#523)

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)