Skip to content

Knative Eventing release v0.21.3

Pre-release
Pre-release
Compare
Choose a tag to compare
@knative-prow-releaser-robot knative-prow-releaser-robot released this 23 Mar 11:11
· 1 commit to release-0.21 since this release
v0.21.3
418df62
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Required Actions

  • BREAKING CHANGE: PingSource binary mode now sends the actual binary data in event body instead of base64-encoded form. (#4851, @eclipselu)
  • You need to run the storage migration tool after the upgrade to migrate from v1beta1 to v1beta2 pingsources.sources.knative.dev resources. (#4750, @eclipselu)

Enhancement

  • 🎁 Adding HorizontalPodAutoscaler and PodDisruptionBudget for the eventing webhook (#4792, @matzew)
  • 🎁 Add event reply header contract to the spec (#4560, @zhongduo)
  • 🎁 Cloudevent traces available for PingSource (#4877, @Shashankft9)
  • 🎁 CloudEvents send to dead-letter endpoints include extension attribute called ce-knativedispatcherr which contains encoded HTTP Response error information from final dispatch attempt. (#4760, @travis-minke-sap)
  • 🎁 Message receiver supports customized liveness and readiness check (#4730, @grac3gao)
  • 🎁 The imc-dispatcher service adds new trace span attributes to be consistent with broker-ingress.knative-eventing & broker-filter.knative-eventing services. The new attributes are messaging.destination, messaging.message_id, messaging.protocol and messaging.system (#4659, @xtreme-sameer-vohra)

API Change

  • 🎁 Add Trigger.Delivery field which allows configuration of Delivery per Trigger. (#4654, @slinkydeveloper)

Bug or Regression

  • Fix availability of zipkin traces for APIServerSource (#4842, @Shashankft9)
  • 🐛 Fix bug where sometimes the pods were not deemed up during setup. #4725 (#4741, @vaikas)
  • 🐛 Fix bug where v1beta1 would allow mutations to immutable fields. v1beta1 trigger.spec.broker is immutable. (#4843, @vaikas)

Clean up

  • 🗑️ Now the config-imc-event-dispatcher values are not configurable on-fly anymore, that is, if you need to configure such values, you need to redeploy the dispatcher deployment (#4543, @slinkydeveloper)
  • 🗑️ PingSource: remove special handling of JSON data since events are always sent in binary mode. (#4858, @lionelvillard)
  • 🗑️ Cleanup channel duck types internals (#4749, @slinkydeveloper)
Assets 9
Loading