Releases: solo-io/solo-kit
Releases · solo-io/solo-kit
v0.20.8
v0.22.1
New Features
- Add ordering to Response Watches so that the order sent to Envoy is in sync.
This would cause an issue in Envoy where the ClusterAssignmentLoad would update before
Clusters would. This caused the Clusters to stay in a warming state until Envoy timed
out, deleting the Endpoints on the cluster. (solo-io/gloo#6337)
v0.29.1
Dependency Bumps
- solo-io/go-list-licenses has been upgraded to v0.1.0.
- onsi/ginkgo has been upgraded to v1.16.5.
- onsi/gomega has been upgraded to v1.16.0.
v0.28.3
v0.24.5
Fixes
- Ordering left out V3Cluster. (solo-io/gloo#6337)
v0.20.7
Fixes
- Ordering left out V3Cluster. (solo-io/gloo#6337)
v0.29.0
Dependency Bumps
- solo-io/protoc-gen-openapi has been upgraded to v0.1.0.
Breaking Changes
- Removed v1 Reports (solo-io/solo-projects#3338)
New Features
- Add messages to status proto (for the immediate purpose of writing the stitched schema to the status field of gateway schema resources) (solo-io/solo-projects#3338)
Fixes
- Ordering left out V3Cluster. (solo-io/gloo#6337)
- Support injecting a set of message names to generate empty validation schema (solo-io/gloo#4789)
v0.24.4
New Features
- Add ordering to Response Watches so that the order sent to Envoy is in sync.
This would cause an issue in Envoy where the ClusterAssignmentLoad would update before
Clusters would. This caused the Clusters to stay in a warming state until Envoy timed
out, deleting the Endpoints on the cluster. (solo-io/gloo#6337)
v0.20.6
New Features
- Add ordering to Response Watches so that the order sent to Envoy is in sync.
This would cause an issue in Envoy where the ClusterAssignmentLoad would update before
Clusters would. This caused the Clusters to stay in a warming state until Envoy timed
out, deleting the Endpoints on the cluster. (solo-io/gloo#6337)
v0.28.0
Breaking changes
NewSnapshotCache
now requiresCacheSettings
- resources have moved to
pkg/api/v1/control-plane/types
NewStatusInfo
now hasprioritySet
added to it.
Breaking Changes
- Add ordering to Response Watches so that the order sent to Envoy is in sync.
This would cause an issue in Envoy where the ClusterAssignmentLoad would update before
Clusters would. This caused the Clusters to stay in a warming state until Envoy timed
out, deleting the Endpoints on the cluster. (solo-io/gloo#6337)