This repository has been archived by the owner on Jun 19, 2022. It is now read-only.
Knative-GCP release v0.14.0
Pre-release
Pre-release
Artifact | Description |
---|---|
cloud-run-events-core.yaml |
All of the knative-gcp components bundled together: Channel, PullSubscription, Topic, CloudPubSubSource, CloudStorageSource, CloudSchedulerSource, CloudAuditLogsSource, and CloudBuildSource. |
cloud-run-events.yaml |
Identical to cloud-run-events-core.yaml . |
Action Required
-
spec.serviceAccount
has been renamed tospec.googleServiceAccount
for all sources. (#736, @grac3gao)- This is to emphasize that the field represents a Service Account in GCP, not a Kubernetes Service Account.
- This is a breaking change. All old sources using
spec.serviceAccount
must be deleted and new sources usingspec.googleServiceAccount
must be created to replace them.
-
Knative has updated the way Brokers determine which default Channel to use. Adding a ConfigMap that includes PubSub as the default.
Follow updated instructions to patch Knative's ConfigMap to point use this configuration. (#608, @zargarpur)
New Features
Workload Identity
- Workload identity can be used instead of a Kubernetes secret
containing a GCP Service Account's downloaded key. (#625, @grac3gao) - Workload identity can be activated for
Topics
andPullSubscriptions
independently of sources. (#728, @grac3gao)
Policy
- Added initial Istio policy binding implementation.
It requires Istio release >= 1.5.
Documentation: /docs/security/README.md (TODO now) (#656, @yolocs) - Added controller for EventPolicyBinding which leverages HTTPPolicy and HTTPPolicyBinding. (#696, @yolocs)
- Add mains and yamls for security apis and controllers (#711, @yolocs)
- Rename security.knative.dev -> policy.run.google.cloud.com (#732, @yolocs)
Other new features
- CloudBuildSource can be used to get events about Cloud Build builds. (#755, @capri-xiyue)
- HTTP Trace propagation using W3C tracecontext headers is now supported. In order to take advantage of trace propagation either use a cloudevents client with support for trace propagation or enable handling of W3C tracecontext headers in the cloudevents HTTP transport. (#734, @ian-mi)
PullSubscriptions
andTopics
now exist in both v1alpha1 and v1beta1 versions. The versions are almost identical. All existing objects will continue to work. All valid configurations for the objects will continue to be valid. (#784, @Harwayne)- If you wish, you may start using the v1beta1 API surface. If you choose not to, then everything will continue to work as-is.
- CloudEvents PubSub binding spec is now available (#633, @nachocano)