Skip to content

Knative Eventing release v0.3.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@evankanderson evankanderson released this 10 Jan 07:35
Artifact Description
eventing.yaml Just the core knative/eventing components without Sources or ChannelProvisioners
in-memory-channel.yaml Just the in-memory ChannelProvisioner
kafka.yaml Just the Kafka ChannelProvisioner
release.yaml Core components bundled with the in-memory ChannelProvisioner

Upgrade notes

  • Knative Eventing now requires Kubernetes 1.11, and provides the
    /status subresource. This causes metadata.generation to behave
    like other Kubernetes objects.
  • All conditions in Source statuses now have a Severity field
    indicating if the condition is terminal or non-terminal. See
    knative/serving#2394 (comment).

Eventing core

  • Channels now create VirtualServices using generateName, which should
    prevent collisions with similarly-named objects from other types
    (such as Knative Services).
  • Subscriptions now work with Knative 0.1 and 0.2.0 Services.
  • Defined and documented the ability to select a default
    ClusterChannelProvisioner if one is not specified by the Channel.
  • The legacy pre-0.2 routing resources have been removed.

In-memory channel

  • No substantial changes.

Kafka channel

  • Improved cleanup of finalizers to prevent Kafka channels from
    remaining stuck forever if provisioning fails.