Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

Knative-GCP release v0.15.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@knative-prow-releaser-robot knative-prow-releaser-robot released this 27 May 03:48
v0.15.0
d3ddec0
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release notes for 0.15

Changes by Kind

Breaking Changes

None

Deprecation Notices

  • spec.googleServiceAccount is deprecated. It has not been promoted to v1beta1 and is expected to be removed from v1alpha1 in the 0.16 release.
  • PullSubscription and Topic in the pubsub.cloud.google.com API group are deprecated and will be removed in the 0.16 release.

GCP Broker

The new GCP-based Broker is ready for usage. See the documentation for instructions.

Observability

  • The GCP Broker now emits broker and trigger trace spans named broker:. and trigger:. respectively. (#1064, @ian-mi)

Workload Identity

  • status.ServiceAccountName has been removed from the last reconcile circle in Identity reconciler. (#884, @grac3gao)
  • CloudPubSubSource, CloudBuildSource, and PullSubscription have a five minute reconciliation loop. (#884, @grac3gao)

Sources

  • Add spec.serviceAccountName, which represents the Kubernetes Service Account to run all data plane components as. (#1128, @grac3gao)

  • CloudAuditLogsSource, CloudPubSubSource, CloudSchedulerSource, and CloudStorageSource now exist in both v1alpha1 and v1beta1 versions. Except for the removal of spec.googleServiceAccount, the versions are identical. All existing objects will continue to work. All valid configurations for the objects will continue to be valid.

    If you wish, you may start using the v1beta1 API surface. If you choose not to, then everything will continue to work as-is. (#827, @Harwayne)

  • CloudAuditLogsSource, CloudPubSubSource, CloudSchedulerSource, CloudStorageSource, and CloudBuildSource will aggressively remove unknown fields. (#824, @Harwayne) (#921, @Harwayne)

  • Your sources can now send events to a sink in another namespace using spec.sink.ref, instead of just spec.sink.uri. (#1099, @nachocano)

pubsub.cloud.google.com

  • PullSubscription and Topic now exist in the internal.events.cloud.google.com API group. (#951, @Harwayne)
  • All Topic and PullSubscription objects in the pubsub.cloud.google.com API group will have deprecation warnings in their status. Those objects will no longer exist in the 0.16 release. All Topic and PullSubscription objects created by other reconcilers within knative-gcp will automatically migrate to the replacements without user interaction. Migration may cause back logged events to be lost. (#980, @Harwayne)
  • Channels and Sources use the PullSubscription and Topic CRDs in the internal.events.cloud.google.com API group. (#1050, @Harwayne)
  • Sources and Channels will delete deprecated Topics and PullSubscriptions. Channels may become unavailable during the upgrade, but should quickly reconcile back to being healthy. Sources will continue sending events and may for a short period of time send the same events multiple times. Any old events in the PullSubscription will be lost (e.g. an event from four hours ago that has not yet been acknowledge by the Source's sink). (#1066, @Harwayne)

Channel

  • Channel now exists in both v1alpha1 and v1beta1 versions. The v1beta1 version lacks Dead Letter queues. It also removes a layer of nesting:
    spec.subscribable.subscribers -> spec.subscribers
    status.subscribableStatus.subscribers -> status.subscribers

    All existing objects will continue to work. All valid configurations for the objects will continue to be valid.

    If you wish, you may start using the v1beta1 API surface. If you choose not to, then everything will continue to work as-is. (#871, @Harwayne) (#959, @Harwayne)

  • Channel will aggressively remove unknown fields. (#849, @Harwayne)

Policy

Assets 4
Loading