Knative Eventing release v0.6.0
Pre-release
Pre-release
knative-prow-releaser-robot
released this
14 May 20:34
·
2 commits
to release-0.6
since this release
Artifact | Description |
---|---|
eventing.yaml |
Just the core knative/eventing components without Sources or ChannelProvisioners |
gcp-pubsub.yaml |
Just the GCP PubSub ChannelProvisioner |
in-memory-channel.yaml |
Just the in-memory ChannelProvisioner |
kafka.yaml |
Just the Kafka ChannelProvisioner |
natss.yaml |
Just the NATS Streaming ChannelProvisioner |
release.yaml |
Core components bundled with the in-memory ChannelProvisioner |
Eventing
WARNING: Release 0.6.0 has a critical bug causing the Broker to drop messages. Please use 0.6.1 or later.
Action Required
- The
in-memory-channel
ClusterChannelProvisioner will be deleted in release 0.7, replaced by thein-memory
provisioner. Please migrate allin-memory-channel
Channels toin-memory
. #1044 #1057 - Trigger's
BrokerExists
condition is now calledBroker
. #1071 - The Kafka dispatcher StatefulSet has been scaled to 0 replicas and replaced with a Deployment. Please delete the StatefulSet
eventing-sources/kafka-channel-dispatcher
after upgrading to 0.6. #972 #1141 - CronJobSource and ContainerSource are now installed as part of the Eventing release instead of Eventing Sources. #1092 #1099
- The
in-memory
ClusterChannelProvisioner now depends on theconfig-tracing
ConfigMap installed by Eventing. Eventing should be installed first. If thein-memory
CCP is installed first, thein-memory
dispatcher will crashloop until Eventing is installed. #1199 - CronJobSource now uses
/apis/v1/namespaces//cronjobsources/
as the CloudEvents Source for all events. This replaces the previous/CronJob
value. #1209
New Features
- A new EventType CRD has been introduced to store the event types that can be consumed from the eventing mesh. #1105
- Upon creating a CronJobSource or ApiServerSource, its EventType will be added to the Registry. #1146 #1201
- Istio is no longer a dependency of Eventing components. Eventing will still work if Istio is present. #294
- A new ApiServerSource CRD has been introduced that emits events when Kubernetes objects change. #1108
- All Channels now support tracing. Tracing is configured by the
config-tracing
ConfigMap. #1199 #1203 #1204 #1231 - All controller reconcilers now expose metrics. #1200
- The ContainerSource now provides additional Kubernetes Events and resource Conditions to assist in debugging knative/eventing-contrib#186
Other Changes
- Triggers now use paths instead of hosts for routing to subscribers, removing the need to create Kubernetes Service and Istio VirtualService objects.
Existing Service and VirtualService objects owned by Triggers will not be deleted proactively. They will be cleaned up by Kubernetes GC when their owning Trigger is deleted. #1045 - Channels using the
in-memory-channel
provisioner will now have aDeprecated
condition. #1062 - All channels now use Kubernetes Service objects of type ExternalName instead of Istio VirtualService objects. #1044 #1058 #1074 #1099
- Eventing data plane components no longer force the Istio sidecar to be injected. #1119
Bug Fixes
- Broker's
Ready
condition is now onlyTrue
when its constituent pieces are alsoReady
. #1064 - Trigger's
Ready
condition is now onlyTrue
when its constituent pieces are alsoReady
. TheBroker
condition is now calledBrokerExists
. #1071 - Channel's
subscriber
array now usesuid
as a patch key. Theref
field is now deprecated. #1057 - Controllers now have the proper finalizer RBAC permissions. #1086 #1089 #1120
- Webhook Controller now binds to an unprivileged port. #1130
- Subscriptions and Triggers watch and track their subscribers so subscriber changes are noticed more quickly. #1149