Knative Eventing release v0.17.8
Pre-release
Pre-release
knative-prow-releaser-robot
released this
03 Nov 11:09
·
5 commits
to release-0.17
since this release
Action Required
-
High availability is now enabled by default on control-plane components; it can be disabled with --disable-ha for now. (#3564, @mattmoor)
-
You must manually delete the (previously scaled to 0) Deployment:
metadata: name: broker-controller namespace: knative-eventing
kubectl delete deployment -n knative-eventing broker-controller
New Features
- ContainerSource is now in v1beta1 (#3661, @bharattkukreja)
- SinkBinding is now in v1beta1 (#3577, @nachocano)
- Eventing conformance tests now can validate Sources status conformance (#3605, @devguyio)
- PingSource now supports setting the time zone. (#3607, @lionelvillard)
- The APIServerSource now sets
name
,kind
andnamespace
as extension attributes in the CloudEvent. (#3741, @danyinggu) - Add two flags to broker to control rest client QPS / Burst. Defaults to same as before. (#3632, @vaikas)
- In Memory Channel and Multi-Tenant Channel Based Broker retry sending events (#2932, @pierDipi)
Removed Features
- Do not emit k8s events for every successful reconcile of IMC (#3676, @vaikas)
- Remove the v1alpha1 CRD api versions. (#3494, @vaikas)
- Remove PingSource v1alpha1 API (#3837, @lionelvillard)
Bug Fixes
- Fixes issue where migration jobs would fail on Istio cluster with auto-inject enabled (#3534, @vayyappaneni)
- For ApiServerSource, the Kubernetes event "ApiServerSourceReconciled" is no longer produced for clean runs of the ReconcileKind method. (#3693, @n3wscott)
- For Channel, the Kubernetes event "ChannelReconciled" is no longer produced for clean runs of the ReconcileKind method. (#3694, @n3wscott)
- For EventType, the Kubernetes event "EventTypeReconciled" is no longer produced for clean runs of the ReconcileKind method. (#3696, @n3wscott)
- For MTBroker, the Kubernetes event "BrokerReconciled" is no longer produced for clean runs of the FinalizeKind method. (#3697, @n3wscott)
- For Parallel, the Kubernetes event "ParallelReconciled" is no longer produced for clean runs of the ReconcileKind method. (#3698, @n3wscott)
- For PingSource, the Kubernetes event "PingSourceReconciled" is no longer produced for clean runs of the ReconcileKind method.
For Sequence, the Kubernetes event "SequenceReconciled" is no longer produced for clean runs of the ReconcileKind method. (#3699, @n3wscott) - For Subscription, the Kubernetes event "SubscriptionReconciled" is no longer produced for clean runs of the ReconcileKind method. (#3695, @n3wscott)
- DeadLetterChannel was being dropped when converting between v1beta1<->v1 (#3574, @vaikas)
- Not all the conditions were being properly converted between v1beta1<->v1. Basically only the Ready was.
- Extend the terminationGracePeriod to fix issues shutting down the webhook. (#3596, @mattmoor)
v1
andv1beta1
DeliverySpec.BackoffDelay accept ISO8601 duration (#3619, @pierDipi)- PingSource does not lose events anymore when being shutdown close to the minute (#3831, @lionelvillard)
Other Changes
- Add missing "leases" RBAC to controller and webhook to support leader election. (#3562, @mattmoor)
- Control plane components now specify anti-affinity so that replicas will not be colocated. (#3795, @mattmoor)
- The multi-tenant PingSource adapter consumes less resources. (#3451, @lionelvillard)
- Reconcile eventing.{Broker,Trigger} using v1 api shape. Operate on dependent resources (Subscriptions, etc.) using their v1 shapes. (#3587, @vaikas)
- When Trigger is reconciled, do not emit an event for it (#3643, @vaikas)
- Fix bug which could cause flakiness in the IMC because IMC Dispatcher was configured for normal reconciler instead of readonly. This could cause races. (3686, @vaikas). (4280, @vaikas)
- Fix bug which could cause Trigger Dependency flakiness because we were incorrectly setting up the informer tracking the dependent sources. (4294, @vaikas). (4296, @vaikas)