knative-extensions/eventing-kafka-broker v0.18.3

Knative Eventing Kafka Broker release v0.18.3

on GitHub

New features

• You can stream HTTP CloudEvents into Apache Kafka using KafkaSink objects: (#177, #134, @pierDipi)
• Now you can configure the server options:, modifying the config map config-kafka-broker-data-plane (#151, @slinkydeveloper)
• Now you can configure the web client options, modifying the config map config-kafka-broker-data-plane (#149, @slinkydeveloper)

Actions required (pre-upgrade):

• Allow independent installation of components (#176, @pierDipi)
  • Remove kafka-broker-controller
    • kubectl delete -n knative-eventing deployment kafka-broker-controller
    • kubectl delete -n knative-eventing clusterrolebindings.rbac.authorization.k8s.io kafka-broker-controller
    • kubectl delete -n knative-eventing clusterrolebindings.rbac.authorization.k8s.io kafka-broker-addressable-resolver
    • kubectl delete -n knative-eventing clusterroles.rbac.authorization.k8s.io kafka-broker-controller
    • kubectl delete -n knative-eventing serviceaccounts kafka-broker-controller

Actions required (post-upgrade):

• Allow independent installation of components (#176, @pierDipi)
  • Remove kafka-broker-config-logging (post-upgrade)
    • kubectl delete -n knative-eventing cm kafka-broker-config-logging

Fix bug

• Update Broker and Trigger status when there is a failure. (#157, @pierDipi)

Row markdown ⬇️

## New features

- You can stream HTTP CloudEvents into Apache Kafka using `KafkaSink` objects: ([#177](https://github.com/knative-sandbox/eventing-kafka-broker/pull/177), [#134](https://github.com/knative-sandbox/eventing-kafka-broker/pull/134), [@pierDipi](https://github.com/pierDipi))
- Now you can configure the [server options:](https://vertx-web-site.github.io/docs/apidocs/io/vertx/core/http/HttpServerOptions.html), modifying the config map `config-kafka-broker-data-plane` ([#151](https://github.com/knative-sandbox/eventing-kafka-broker/pull/151), [@slinkydeveloper](https://github.com/slinkydeveloper))
- Now you can configure the [web client options](https://vertx-web-site.github.io/docs/apidocs/io/vertx/ext/web/client/WebClientOptions.html), modifying the config map `config-kafka-broker-data-plane` ([#149](https://github.com/knative-sandbox/eventing-kafka-broker/pull/149), [@slinkydeveloper](https://github.com/slinkydeveloper))

## Actions required (pre-upgrade): 

  - Allow independent installation of components ([#176](https://github.com/knative-sandbox/eventing-kafka-broker/pull/176), [@pierDipi](https://github.com/pierDipi))
    - Remove `kafka-broker-controller`
      - `kubectl delete -n knative-eventing deployment kafka-broker-controller`
      - `kubectl delete -n knative-eventing clusterrolebindings.rbac.authorization.k8s.io kafka-broker-controller`
      - `kubectl delete -n knative-eventing clusterrolebindings.rbac.authorization.k8s.io kafka-broker-addressable-resolver`
      - `kubectl delete -n knative-eventing clusterroles.rbac.authorization.k8s.io kafka-broker-controller`
      - `kubectl delete -n knative-eventing serviceaccounts kafka-broker-controller`
    
## Actions required (post-upgrade): 
  - Allow independent installation of components ([#176](https://github.com/knative-sandbox/eventing-kafka-broker/pull/176), [@pierDipi](https://github.com/pierDipi)) 
     - Remove `kafka-broker-config-logging` (post-upgrade) 
       - `kubectl delete -n knative-eventing cm kafka-broker-config-logging` 

## Fix bug 
  - Update Broker and Trigger status when there is a failure. ([#157](https://github.com/knative-sandbox/eventing-kafka-broker/pull/157), [@pierDipi](https://github.com/pierDipi))