Knative Eventing Kafka Broker release v1.4.0

Changes by Kind

Features

• Handle host headers in dataplane for identification of channel instances (#1990, @aliok)
• There is now auto-migration from old consolidated KafkaChannel to the new KafkaChannel. Low level configuration options such as Sarama settings are not migrated to the new channel. However, channel url and auth settings are migrated. (#2004, @aliok)
• Discard Consumer records that are not CloudEvents (#2066, @aavarghese)
• Dynamically set max.poll.interval.ms based on the delivery spec (#2058, @pierDipi)
• The default request timeout is 10 minutes now, it was previously set to 10 seconds.
  It can be overridden using spec.delivery.timeout on Broker, Trigger, KafkaChannel and Subscription. (#2057, @pierDipi)
• Add new new-trigger-filters experimental feature. When enabled, Triggers support a new filters field that conforms to the filters API field defined in the CloudEvents Subscriptions API. It allows you to specify a set of powerful filter expressions, where each expression evaluates to either true or false for each event. (#1922, @devguyio)

Knative Eventing Kafka Broker release v1.3.2

Enhancements

• Show error in Broker and Channel status when resolving sink fails (#1833, @pierDipi)
• Add KafkaSource migration logic as a post-install job (eventing-kafka-post-install.yaml). (#1889, @pierDipi)
• Adding Storage-Version-Migrator for KafkaSource and KafkaChannel (#1869, @matzew)
• KafkaChannel becomes conformant with spec. Conformance tests are now run with every code change. (#1825, @aliok)

Bug fixes

• Support brokers with long namespace and name values. (#1971, @pierDipi)
• KafkaChannel reconciler checks for empty subscriber URI. (#1905, @pierDipi)

Known issues

• The reference information for metrics is not built successfully for Kafka channels. (#1824, @aliok)

Knative Eventing Kafka Broker release v1.2.4

• An HTTP header will be supplied to your event consumers when the broker it is communicating with supports reply events. This will always be sent while using this Kafka broker since it supports handling reply events. (#1771, @jhill072)

• Apply back-pressure by limiting the number of in-flight dispatch requests in the unordered event consumption (#1750, @pierDipi)

• Support TLS for the metrics server.

  Now, the receiver and the dispatcher accept the following env
  variables:

  • METRICS_PEM_CERT_PATH: TLS cert path
  • METRICS_PEM_KEY_PATH: TLS key path
  • METRICS_HOST: metrics server host (#1707, @pierDipi)

New Contributors

• @snowwolf007cn made their first contribution in #1546
• @aavarghese made their first contribution in #1569
• @jhill072 made their first contribution in #1771

Full Changelog: v0.27.0...knative-v1.2.0

Knative Eventing Kafka Broker release v1.3.1

Enhancements

• Show error in Broker and Channel status when resolving sink fails (#1833, @pierDipi)
• Add KafkaSource migration logic as a post-install job (eventing-kafka-post-install.yaml). (#1889, @pierDipi)
• Adding Storage-Version-Migrator for KafkaSource and KafkaChannel (#1869, @matzew)
• KafkaChannel becomes conformant with spec. Conformance tests are now run with every code change. (#1825, @aliok)

Bug fixes

• Support brokers with long namespace and name values. (#1971, @pierDipi)
• KafkaChannel reconciler checks for empty subscriber URI. (#1905, @pierDipi)

Known issues

• The reference information for metrics is not built successfully for Kafka channels. (#1824, @aliok)

Knative Eventing Kafka Broker release v1.3.0

Enhancements

• Show error in Broker and Channel status when resolving sink fails (#1833, @pierDipi)
• Add KafkaSource migration logic as a post-install job (eventing-kafka-post-install.yaml). (#1889, @pierDipi)
• Adding Storage-Version-Migrator for KafkaSource and KafkaChannel (#1869, @matzew)
• KafkaChannel becomes conformant with spec. Conformance tests are now run with every code change. (#1825, @aliok)

Bug fixes

• Support brokers with long namespace and name values. (#1971, @pierDipi)
• KafkaChannel reconciler checks for empty subscriber URI. (#1905, @pierDipi)

Known issues

• The reference information for metrics is not built successfully for Kafka channels. (#1824, @aliok)

Knative Eventing Kafka Broker release v1.2.3

• An HTTP header will be supplied to your event consumers when the broker it is communicating with supports reply events. This will always be sent while using this Kafka broker since it supports handling reply events. (#1771, @jhill072)

• Apply back-pressure by limiting the number of in-flight dispatch requests in the unordered event consumption (#1750, @pierDipi)

• Support TLS for the metrics server.

  Now, the receiver and the dispatcher accept the following env
  variables:

  • METRICS_PEM_CERT_PATH: TLS cert path
  • METRICS_PEM_KEY_PATH: TLS key path
  • METRICS_HOST: metrics server host (#1707, @pierDipi)

New Contributors

• @snowwolf007cn made their first contribution in #1546
• @aavarghese made their first contribution in #1569
• @jhill072 made their first contribution in #1771

Full Changelog: v0.27.0...knative-v1.2.0

Knative Eventing Kafka Broker release v1.1.6

Changes by Kind

🚨 Breaking or Notable

• Add a new implementation of the KafkaSource API (#1415, @pierDipi)
• Kafka Broker event delivery is hundreds of times faster (#1405, @pierDipi)
• broker.spec.config is now required. (#1555, @pierDipi)

💫 New Features & Changes

• The kafka-controller deployment emits probe requests against the data plane (kafka-sink-receiver and kafka-broker-receiver) to determine Kafka Broker and KafkaSink readiness. (#1495, @pierDipi)
• 🎁 you can now config which header format(b3 multi header, b3 single header, and w3c trace-context) to be used while using Zipkin backend (#1546, @snowwolf007cn)
• Handle non-retryable HTTP status codes as reported in the spec:
  For more information: https://github.com/knative/specs/blob/c348f501de9eb998b4fd010c54d9127033ee41be/specs/eventing/data-plane.md#event-acknowledgement-and-delivery-retry (#1574, @pierDipi)

🐞 Bug Fixes

• Commit offset on consumer close. (#1463, @pierDipi)
• Properly handle events without the data field. (#1460, @pierDipi)
• Fix deleting the Broker ConfigMap prevents the Broker from being finalized (#1589, @pierDipi)

New Contributors

• @snowwolf007cn made their first contribution in #1546
• @aavarghese made their first contribution in #1569

Full Changelog: v0.27.0...knative-v1.1.0

Knative Eventing Kafka Broker release v1.2.2

• An HTTP header will be supplied to your event consumers when the broker it is communicating with supports reply events. This will always be sent while using this Kafka broker since it supports handling reply events. (#1771, @jhill072)

• Apply back-pressure by limiting the number of in-flight dispatch requests in the unordered event consumption (#1750, @pierDipi)

• Support TLS for the metrics server.

  Now, the receiver and the dispatcher accept the following env
  variables:

  • METRICS_PEM_CERT_PATH: TLS cert path
  • METRICS_PEM_KEY_PATH: TLS key path
  • METRICS_HOST: metrics server host (#1707, @pierDipi)

New Contributors

• @snowwolf007cn made their first contribution in #1546
• @aavarghese made their first contribution in #1569
• @jhill072 made their first contribution in #1771

Full Changelog: v0.27.0...knative-v1.2.0

Knative Eventing Kafka Broker release v1.1.5

Changes by Kind

🚨 Breaking or Notable

• Add a new implementation of the KafkaSource API (#1415, @pierDipi)
• Kafka Broker event delivery is hundreds of times faster (#1405, @pierDipi)
• broker.spec.config is now required. (#1555, @pierDipi)

💫 New Features & Changes

• The kafka-controller deployment emits probe requests against the data plane (kafka-sink-receiver and kafka-broker-receiver) to determine Kafka Broker and KafkaSink readiness. (#1495, @pierDipi)
• 🎁 you can now config which header format(b3 multi header, b3 single header, and w3c trace-context) to be used while using Zipkin backend (#1546, @snowwolf007cn)
• Handle non-retryable HTTP status codes as reported in the spec:
  For more information: https://github.com/knative/specs/blob/c348f501de9eb998b4fd010c54d9127033ee41be/specs/eventing/data-plane.md#event-acknowledgement-and-delivery-retry (#1574, @pierDipi)

🐞 Bug Fixes

• Commit offset on consumer close. (#1463, @pierDipi)
• Properly handle events without the data field. (#1460, @pierDipi)
• Fix deleting the Broker ConfigMap prevents the Broker from being finalized (#1589, @pierDipi)

New Contributors

• @snowwolf007cn made their first contribution in #1546
• @aavarghese made their first contribution in #1569

Full Changelog: v0.27.0...knative-v1.1.0

Knative Eventing Kafka Broker release v1.1.4

Changes by Kind

🚨 Breaking or Notable

• Add a new implementation of the KafkaSource API (#1415, @pierDipi)
• Kafka Broker event delivery is hundreds of times faster (#1405, @pierDipi)
• broker.spec.config is now required. (#1555, @pierDipi)

💫 New Features & Changes

• The kafka-controller deployment emits probe requests against the data plane (kafka-sink-receiver and kafka-broker-receiver) to determine Kafka Broker and KafkaSink readiness. (#1495, @pierDipi)
• 🎁 you can now config which header format(b3 multi header, b3 single header, and w3c trace-context) to be used while using Zipkin backend (#1546, @snowwolf007cn)
• Handle non-retryable HTTP status codes as reported in the spec:
  For more information: https://github.com/knative/specs/blob/c348f501de9eb998b4fd010c54d9127033ee41be/specs/eventing/data-plane.md#event-acknowledgement-and-delivery-retry (#1574, @pierDipi)

🐞 Bug Fixes

• Commit offset on consumer close. (#1463, @pierDipi)
• Properly handle events without the data field. (#1460, @pierDipi)
• Fix deleting the Broker ConfigMap prevents the Broker from being finalized (#1589, @pierDipi)

New Contributors

• @snowwolf007cn made their first contribution in #1546
• @aavarghese made their first contribution in #1569

Full Changelog: v0.27.0...knative-v1.1.0