knative/eventing knative-v1.0.3 on GitHub

🚨 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)

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.
- Deprecates deadLetterChannel with a 1-year timer. (#5746, @evankanderson)
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)

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)

Nothing has changed.