Skip to content

Knative Eventing release v1.0.0

Compare
Choose a tag to compare
@knative-prow-releaser-robot knative-prow-releaser-robot released this 02 Nov 11:37
· 6 commits to release-1.0 since this release
1e4fa35

🚨 Breaking or Notable

  • If the "strict-subscriber" feature flag is set, Subscriptions will require spec.subscriber to be set. Previously, a bare spec.reply would be accepted by Subscriptions. This feature will be enabled in the 1.1 release; it breaks compatibility with previous versions in order to track the eventing spec and improve the user experience when using Subscriptions. (#5762, @salaboy)

πŸ’« New Features & Changes

  • By default, the Prefer: reply header is forwarded to Broker Triggers' subscribers (#5773, @salaboy)
  • The Header Prefer: reply is added to the request sent to a Subscription Subscriber if the spec.reply field is set. (#5764, @salaboy)
  • The field spec.delivery.deadLetterSink.ref.namespace for Broker, Trigger, Channel and Subscription if not specified is defaulted to metadata.namespace. (#5748, @pierDipi)
  • Adds deadLetterSinkUri to the Channel status.
  • Channel and Subscription will now enforce validation of the "delivery" field. (#5777, @travis-minke-sap)
  • Next generation Multi-Tenant Scheduler and Descheduler: uses a plugin interface to specify a Scheduler profile with predicates and priorities that run filtering and scoring of pods, respectively to compute the best vreplica placements. When the autoscaler adds new pods, scheduler performs a rebalancing of the already placed vreplicas along with the new vreplicas. A Descheduler profile must be installed when vreplicas need to be scaled down and placements removed. (#5818, @aavarghese)
  • Add UID to the available Kreference mapping resolver template field (#5810, @lionelvillard)

🐞 Bug Fixes

  • Fix issue with Parallel updates leaked resources. In order for the fix to work the provided Channel must include the delete verb at the ClusterRole labeled duck.knative.dev/channelable. (#5775, @odacremolbap)
  • Fix issue with Sequence updates leaked resources. In order for the fix to work the provided Channel must include the delete verb at the ClusterRole labeled duck.knative.dev/channelable. (#5718, @odacremolbap)

Dependencies

Added

  • github.com/cespare/xxhash/v2: v2.1.1
  • google.golang.org/grpc/cmd/protoc-gen-go-grpc: v1.1.0

Changed

  • cloud.google.com/go/storage: v1.10.0 β†’ v1.18.2
  • cloud.google.com/go: v0.72.0 β†’ v0.97.0
  • github.com/cncf/xds/go: fbca930 β†’ aa0b789
  • github.com/envoyproxy/go-control-plane: 63b5d3c β†’ cf90f65
  • github.com/golang/mock: v1.4.4 β†’ v1.6.0
  • github.com/golang/snappy: 2e65f85 β†’ v0.0.3
  • github.com/google/martian/v3: v3.1.0 β†’ v3.2.1
  • github.com/google/pprof: 3e6fc7f β†’ 4bb14d4
  • github.com/googleapis/gax-go/v2: v2.0.5 β†’ v2.1.1
  • github.com/influxdata/tdigest: 5d87a75 β†’ bf2b5ad
  • github.com/prometheus/common: v0.30.0 β†’ v0.31.1
  • github.com/yuin/goldmark: v1.3.5 β†’ v1.4.0
  • go.uber.org/goleak: v1.1.10 β†’ 6911603
  • go.uber.org/zap: v1.19.0 β†’ v1.19.1
  • golang.org/x/lint: 83fdc39 β†’ 6edffad
  • golang.org/x/net: e898025 β†’ 4f30a5c
  • golang.org/x/oauth2: 2bc19b1 β†’ 6b3c2da
  • golang.org/x/sys: 665e8c7 β†’ d61c044
  • golang.org/x/tools: v0.1.5 β†’ v0.1.7
  • google.golang.org/api: v0.36.0 β†’ v0.58.0
  • google.golang.org/genproto: 9910b6c β†’ 37fc393
  • google.golang.org/grpc: v1.40.0 β†’ v1.41.0
  • k8s.io/gengo: de9496d β†’ 39e73c8
  • knative.dev/hack/schema: 815cd31 β†’ b96d65a
  • knative.dev/hack: 815cd31 β†’ b96d65a
  • knative.dev/pkg: 5ae4821 β†’ 5d9d300
  • knative.dev/reconciler-test: 49fac75 β†’ cff9b53
  • sigs.k8s.io/yaml: v1.2.0 β†’ v1.3.0

Removed

Nothing has changed.