Skip to content

Releases: tektoncd/triggers

Tekton Triggers release v0.16.1

18 Oct 18:13
Compare
Choose a tag to compare

πŸŽ‰ Tekton Triggers release v0.16.1 πŸŽ‰

-Docs @ v0.16.1
-Examples @ v0.16.1

Installation one-liner

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.16.1/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.16.1/interceptors.yaml

Upgrade Notices

To upgrade from v0.16.0

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.16.1/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.16.1/interceptors.yaml

Changes

Fixes

  • πŸ› Fix validation failure issue for Knative service (#1240)

Thanks

Thanks to these contributors who contributed to v0.16.1!

Extra shout-out for awesome release notes:

Tekton Triggers release v0.16.0

01 Sep 10:37
Compare
Choose a tag to compare

πŸŽ‰ Tekton Triggers release v0.16.0 πŸŽ‰

-Docs @ v0.16.0
-Examples @ v0.16.0

Installation one-liner

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.16.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.16.0/interceptors.yaml

Upgrade Notices

Release supports v1beta1 API version and contains a few backwards incompatible changes. Please check the Backwards Incompatible Changes section before upgrading.

To upgrade from v0.15.2

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.16.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.16.0/interceptors.yaml

Changes

Features

  • ✨ Port FeatureGates to Triggers (#1110)
    Now Triggers support FeatureGates feature:

    • It introduces a feature-flags ConfigMap to configure feature flags.
    • It adds an enable-api-fields feature flag to control that can be set to alpha or stable (default).
    • It adds a test helper called requireGate to allow an integration test to be skipped if enable-api-fields is not "alpha".
  • ✨ Packages ClusterRoles with Triggers deployment for eventlistener (#1158)
    Triggers packages 2 clusterroles for eventlisteners which can be used by users for their eventlistener deployment which will provide eventlistener required access in a particular namespace.
    user will have to create following resources

    • a serviceaccount which would be used with eventlistener
    • a rolebinding with above sa and tekton-triggers-eventlistener-roles clusterrole
    • a clusterrolebinding with above sa and tekton-triggers-eventlistener-clusterroles clusterrole
  • ✨ Add Event Count for EventListener Metrics (#1160)
    Added a new metrics called event_count for events received at EventListener Sink

  • ✨ Add probes to custom resources(Knative Service) (#1171)

    • Add Readiness and Liveness Probes for Knative service
    • EventListener pod runs on 8080 instead of 8000 port
  • ✨ Mark webhook and controller as safe-to-evict (#1179)
    The safe-to-evict annotation tells the cluster autoscaler whether the pod can be evicted to allow the node it's on to scale down.

    Unfortunately, blocking node eviction means the node that the pod(s) get scheduled to can't be scaled down. Furthermore, the nodes can't be fully drained when updating the cluster. This can leave a cluster in a mid-upgrade state that can make issues difficult to diagnose and reason about.

    With this change, a cluster scale-down event might cause temporary service unreliability with the default single-replica configuration.

    By default, controller components are now marked as safe-to-evict by the cluster autoscaler.

  • ✨ Add config-defaults configmap to set default values (#1182)
    Triggers now support config-defaults configmap to set default values and as of now serviceAccountName added to config-defaults.

  • ✨ Add Status Tag to Event Count Metrics (#1188)
    EventListener metrics event_count status which can determine whether received event failed before processing.

  • ✨ Adds annotation to disable payload validation in eventlistener (#1189)
    This adds an annotation support tekton.dev/payload-validation for eventlistener. If it is added to el with value as false then the payload from events will not be validated and will be directly passed to interceptors.
    By default the payload validation is enabled. Only if annotation is defined and its value is false then it will be disabled for that particular el.
    User can define an annotation on eventlistener tekton.dev/payload-validation: "false" to disable the payload validation in that event listener.

  • ✨ Add Metrics Port to EventListener service (#1191)
    Metrics port in service is needed by metering serices like prometheus servicemonitor. It's already there for controller and webhook but not EventListener which is created.
    Service Port for EventListener is accessible as http-metrics.

Backwards incompatible changes

In current release:

  • 🚨 Remove Redundant Status Tag from EventListener Metrics (#1166)
    Breaking Change:
    Status label has been removed from metric eventlistener_http_duration_seconds_*. Please remove querying base on status label.

Fixes

  • πŸ› Fix a type error (#1165)
  • πŸ› Patch vendor/ apimachinery to work on 1.22 (#1197)
    Backport adding Subresource field to ManagedField entries in our vendor/ folder to make tektoncd/pipeline work on k8s 1.22.
  • πŸ› Return the correct error (#1200)
  • πŸ› Leverage network.GetServiceHostname (#1202)

Misc

  • πŸ”¨ Adds curl test in e2e tests for examples (#1155)
  • πŸ”¨ Add links to versioned docs for v0.15.0 & v0.14.2 (#1157)
  • πŸ”¨ Add SetSecuritycontext for EventListener in Controller.yaml (#1175)
    SetSecuritycontext for EventListener in controller deployment can be configured now.
  • πŸ”¨ Fix typo in release cheatsheet (#1190)
  • πŸ”¨ Bump tektoncd/pipeline to v0.27.1 (#1196)
  • πŸ”¨ Take advantage of knative helpers. (#1199)
  • πŸ”¨ Use kmeta.UnionMaps helper (#1201)
  • πŸ”¨ Move off of deprecated sharedmain methods (#1203)
  • πŸ”¨ Simplify helper method signatures, leverage ctx (#1204)
  • πŸ”¨ Refactor the way Triggers creates child resources to follow Knative conventions (#1205)
  • πŸ”¨ Next pass refactoring EventListener reconciler towards best-practices. (#1206)
    EventListener is more aggressive about reconciling its child resources, so changes to their spec should be done through the EventListener object itself. Autoscaling of the EventListener Deployment is allowed if replicas: is omitted.
  • πŸ”¨ Raise the resync period to something more reasonable. (#1208)
  • πŸ”¨ Renames examples rolebinding & clusterrolebinding (#1210)

Docs

  • πŸ“– Update docs for clusterroles packaged for eventlistener (#1163)
  • πŸ“– Update Trigger Flow image and add it to the docs. (#1167)
  • πŸ“– Fix formatting of md so list display in HTML (#1186)
  • πŸ“– Update readme with proper servicename (#1193)
  • πŸ“– Updates docs for payload validation annotation (#1194)

Thanks

Thanks to these contributors who contributed to v0.16.0!

Extra shout-out for awesome release notes:

Tekton Triggers release v0.15.2

31 Aug 20:41
Compare
Choose a tag to compare

πŸŽ‰ Tekton Triggers release v0.15.2 πŸŽ‰

-Docs @ v0.15.2
-Examples @ v0.15.2

Installation one-liner

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.15.2/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.15.2/interceptors.yaml

Upgrade Notices

This release contains fixes for Triggers to operate on Kubernetes version 1.22

Changes

Fixes

  • Patch vendor/ apimachinery to work on 1.22 (#1197)
  • Fix GitHub EL name in port forward command. (#1192)

Thanks

Thanks to these contributors who contributed to v0.15.2!

Tekton Triggers release v0.15.1

17 Aug 19:40
Compare
Choose a tag to compare

πŸŽ‰ Tekton Triggers v0.15.1 πŸŽ‰

-Docs @ v0.15.1
-Examples @ v0.15.1

Installation one-liner

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.15.1/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.15.1/interceptors.yaml

Fixes

  • Fix status reconcilation for Knative service (#1170)

  • Update default branch for getting-started template (#1176)

  • Upate gjson to v1.6.5 (#1164)

Updates to address CVE-2020-36066 and CVE-2020-35380.

Thanks

Thanks to these contributors who contributed to v0.15.1!

Tekton Triggers release v0.15.0

19 Jul 20:36
Compare
Choose a tag to compare

Upgrade Notices

This release introduces a new v1beta1 API version and contains a few backwards incompatible changes. Please check the Backwards Incompatible Changes section before upgrading.

To upgrade from v0.14.2

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.15.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.15.0/interceptors.yaml

Changes

Features

  • ✨ Add ConfigMap which can contain triggers info (#1114)

Add ConfigMap which will contains Triggers info such as version and some RBAC rules which will give access to this ConfigMap to all the system:authenticated users.

  • ✨ Add v1beta1 Go API types (#1103)

Triggers now supports a new apiVersion - v1beta1. The v1beta1 apiVersion will follow the beta deprecation policy i.e. features will have a 9 month deprecation period.

  • ✨ Send EL response before Triggers finish processing (#1132)

BREAKING CHANGE: With this change the EventListener will stop responding with 201 Created status code when it creates resources. Instead it will always respond with a 202 Accepted response code.

  • ✨ Switch reconciler & sink to using v1beta1 types (#1125)

The Triggers Reconciler and EventListeners now use v1beta1 API types internally. This is a fully backwards compatible change. Users can still use the v1alpha1 API version as they were before.

  • ✨ Updates Interceptors to use Lister to access secrets (#1122)

The packaged interceptors now use a Lister to cache access to secrets used for payload verification

  • ✨ Adds readiness probe in core-interceptors deployment (#1107)

Backwards incompatible changes

In current release:

  • 🚨 Send EL response before Triggers finish processing (#1132)

BREAKING CHANGE: With this change the EventListener will stop responding with 201 Created status code when it creates resources. Instead it will always respond with a 202 Accepted response code.

  • 🚨 Removes podTemplate field from EventListener (#1118)

BREAKING CHANGE: The podTemplate filed which was deprecated as part of #1100 has now been removed.

  • 🚨 Removes the replicas field (#1113)

BREAKING CHANGE: The deprecated replicas field has now been removed.

Fixes

  • πŸ› Fix the cp command in the release publish task (#1134)

  • πŸ› Fixes namespace in clusterrolebinding in getting-started (#1106)

Misc

  • πŸ”¨ Migrate reconcilers to unversioned packages (#1096)
  • πŸ”¨ Adds E2E tests for Examples (#1142)
  • πŸ”¨ fix typo for release and interceptors name (#1108)
  • πŸ”¨ Fix typo and add versioning for 0.14.0 (#1093)
  • πŸ”¨ Update examples readme to use valid port 8000 (#1071)
  • πŸ”¨ Fix a typo in release-cheatsheet (#1144)

Docs

  • πŸ“– Add details to Interceptor docs. (#1130)
  • πŸ“– Add description for compareSecret parameters (#1129)
  • πŸ“– Fix a broken link in interceptors.md (#1116)
  • πŸ“– Update examples for consistency (#1140)
  • πŸ“– Fix small documentation issue (#1112)
  • πŸ“– docs: fix formatting of code examples (#1148)
  • πŸ“– Update getting started guide with github enterprise config(#1151)

Thanks

Thanks to these contributors who contributed to v0.15.0!

Extra shout-out for awesome release notes:

Tekton Triggers release v0.15.0-rc1 "Tekton Triggers"

15 Jul 20:00
Compare
Choose a tag to compare

Upgrade Notices

This is a release candidate for v0.15. This release introduces a new v1beta1 apiVersion and contains a few backwards incompatible changes. Please check the Backwards Incompatible Changes section before upgrading.

To upgrade from v0.14.2

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.15.0-rc1/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.15.0-rc1/interceptors.yaml

Changes

Features

  • ✨ Add ConfigMap which can contain triggers info (#1114)

Add ConfigMap which will contains Triggers info such as version and some RBAC rules which will give access to this ConfigMap to all the system:authenticated users.

  • ✨ Add v1beta1 Go API types (#1103)

Triggers now supports a new apiVersion - v1beta1. The v1beta1 apiVersion will follow the beta deprecation policy i.e. features will have a 9 month deprecation period.

  • ✨ Send EL response before Triggers finish processing (#1132)

BREAKING CHANGE: With this change the EventListener will stop responding with 201 Created status code when it creates resources. Instead it will always respond with a 202 Accepted response code.

  • ✨ Switch reconciler & sink to using v1beta1 types (#1125)

The Triggers Reconciler and EventListeners now use v1beta1 API types internally. This is a fully backwards compatible change. Users can still use the v1alpha1 API version as they were before.

  • ✨ Updates Interceptors to use Lister to access secrets (#1122)

The packaged interceptors now use a Lister to cache access to secrets used for payload verification

  • ✨ Adds readiness probe in core-interceptors deployment (#1107)

Backwards incompatible changes

In current release:

  • 🚨 Send EL response before Triggers finish processing (#1132)

BREAKING CHANGE: With this change the EventListener will stop responding with 201 Created status code when it creates resources. Instead it will always respond with a 202 Accepted response code.

  • 🚨 Removes podTemplate field from EventListener (#1118)

BREAKING CHANGE: The podTemplate filed which was deprecated as part of #1100 has now been removed.

  • 🚨 Removes the replicas field (#1113)

BREAKING CHANGE: The deprecated replicas field has now been removed.

Fixes

  • πŸ› Fix the cp command in the release publish task (#1134)

  • πŸ› Fixes namespace in clusterrolebinding in getting-started (#1106)

Misc

  • πŸ”¨ Migrate reconcilers to unversioned packages (#1096)
  • πŸ”¨ Adds E2E tests for Examples (#1142)
  • πŸ”¨ fix typo for release and interceptors name (#1108)
  • πŸ”¨ Fix typo and add versioning for 0.14.0 (#1093)
  • πŸ”¨ Update examples readme to use valid port 8000 (#1071)

Docs

  • πŸ“– Add details to Interceptor docs. (#1130)
  • πŸ“– Add description for compareSecret parameters (#1129)
  • πŸ“– Fix a broken link in interceptors.md (#1116)
  • πŸ“– Update examples for consistency (#1140)
  • πŸ“– Fix small documentation issue (#1112)

Thanks

Thanks to these contributors who contributed to v0.15.0-rc1!

Extra shout-out for awesome release notes:

Tekton Triggers release v0.14.2

04 Jun 17:07
Compare
Choose a tag to compare

-Docs @ v0.14.2
-Examples @ v0.14.2

Installation one-liner

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.2/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.2/interceptors.yaml

Upgrade Notices

  1. As of this release, the Triggers release will contain two YAML files. release.yaml contains the core release artifacts while interceptors.yaml contain the 4 core interceptors (GitHub, GitLab, BitBucket, and CEL).

How to upgrade from v0.14.1 :up_arrow:

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.2/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.2/interceptors.yaml

Changes

Fixes

  • πŸ› Add Clusterrole Aggregate View and Edit for ClusterInterceptor CRD (#1123)

Docs

  • πŸ“– Update title fields in docs/README.md (release-v0.14.x patch) (#1109)

Thanks

Thanks to these contributors who contributed to v0.14.2!

Extra shout-out for awesome release notes:

Tekton Triggers release v0.14.1

21 May 09:13
Compare
Choose a tag to compare

-Docs @ v0.14.1
-Examples @ v0.14.1

Installation one-liner

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.1/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.1/interceptors.yaml

Upgrade Notices

  1. As of this release, the Triggers release will contain two YAML files. release.yaml contains the core release artifacts while interceptors.yaml contain the 4 core interceptors (GitHub, GitLab, BitBucket, and CEL).

How to upgrade from v0.14.0 :up_arrow:

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.1/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.1/interceptors.yaml

Changes

Deprecation Notices

  • 🚨 Deprecate podTemplate field (#1102)
    Handled deprecation of podTemplate properly so that there won't be any issue with Upgrade which we faced as part of 0.14.0.
    Reference Issue #1098

Misc

  • πŸ”¨ Upgrade plumbing version. (#1104)

Thanks

Thanks to these contributors who contributed to v0.14.1!

Extra shout-out for awesome release notes:

Tekton Triggers v0.14.0

17 May 19:57
Compare
Choose a tag to compare

-Docs @ v0.14.0
-Examples @ v0.14.0

Installation

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.0/interceptors.yaml

Upgrade Notices

  1. As of this release, the Triggers release will contain two YAML files. release.yaml contains the core release artifacts while interceptors.yaml contain the 4 core interceptors (GitHub, GitLab, BitBucket, and CEL).

How to upgrade from v0.13.0 :up_arrow:

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.0/interceptors.yaml

Changes

Features

  • ✨ Provide error for invalid bindings (#1049)

TriggerBinding produces error on providing invalid Tekton template values.

  • ✨ Adding opencensus metrics (#1061)

Added Eventlistener OpenCensus metrics which captures metrics at process level.

  • ✨ Add validation check for triggers (#1072)

User cannot specify both TriggerRef and (TriggerTemplate, TriggerBindings, Interceptors) as part of eventlistener spec.

  • ✨ Add a Ready StatusCondition for EventListener (#1082)

The EventListener Status now has a new Condition called Ready. Ready is set to True when the other status conditions are also true (i.e. the EventListener is ready to serve traffic). It is false if any of the other statuses are false.

Deprecation Notices

  • 🚨 Add a Ready StatusCondition for EventListener (#1082)

The EventListener Status now has a new Condition called Ready. Ready is set to True when the other status conditions are also true (i.e. the EventListener is ready to serve traffic). It is false if any of the other statuses are false.

DEPRECATION NOTICE: In the future, we plan to deprecate the other status conditions in favor of the Ready status condition.

  • 🚨 Add EventListener UID to sink response, mark name/namespace as deprecated (#1087)

eventListener and namespace fields in EventListener response are now deprecated. Use eventListenerUID instead.

Backwards incompatible changes

  • 🚨 Removed deprecated fields (#1040)

As part of this release we have removed deprecated fields ServiceType and PodTemplate from the EventListener Spec.

Fixes

  • πŸ› Skip heavy validation on deletion πŸ™ƒ (#1085)

Skip heavy validation on deletion in the webhook.

  • πŸ› Fix metrics port expose issue for triggers eventlistener (#1086)

Triggers exposes metrics on 9000 port.

  • πŸ› Add EventListener UID to sink response, mark name/namespace as deprecated (#1087)

eventListener and namespace fields in EventListener response are now deprecated. Use eventListenerUID instead.

Misc

  • πŸ”¨ Update roadmap for 2021 (#1053)
  • πŸ”¨ Add links to versioned docs for v0.13.0 (#1058)
  • πŸ”¨ Updating to latest version of plumbing (#1064)
  • πŸ”¨ refactor: move list of allowed ResourceTemplate types to its own package (#1068)
  • πŸ”¨ Resolving build test issues in PRs (#1078)
  • πŸ”¨ Migrate from test builders to structs (#1080)
  • πŸ”¨ Bump CEL version to latest version. (#1088)

The CEL interceptor is updated to the latest version of CEL, this brings in the CEL base64 decoding functions.
These are documented here https://github.com/google/cel-go/tree/master/ext#base64decode
Note: the CEL base64 decoding function decodes to a CEL byte array, which is not a string, it uses the b'hello' syntax to represent a string of bytes "hello".
The triggers decodeb64 CEL function is now deprecated in favour of the upstream encoders package, you can replace body.value.decodeb64 with string(base64.decode(body.value))

  • πŸ”¨ Bump pipeline to 0.24.1 and knative pkg to 0.22 (#1091)

Docs

  • πŸ“– Add the new Interceptors Page (#1035)
  • πŸ“– Rewrite the ClusterInterceptors page for clarity and flow (#1048)
  • πŸ“– Capitalization consistency for resourcetemplates (#1050)
  • πŸ“– Update README.md and Release Cheat Sheet (#1051)
  • πŸ“– Update install documentation (#1054)
  • πŸ“– Rewrite the EventListeners Page (#1060)
  • πŸ“– Delete obsolete page exposing-eventlisteners.md (#1066)
  • πŸ“– Update link to interceptors doc (#1073)
  • πŸ“– Add link between cluster interceptor docs and interceptor docs (#1074)

Thanks

Thanks to these contributors who contributed to v0.14.0!

Extra shout-out for awesome release notes:

Tekton Triggers v0.13.0

14 Apr 18:54
Compare
Choose a tag to compare

Tekton Triggers v0.13.0

-Docs @ v0.13.0
-Examples @ v0.13.0

Installation

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.13.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.13.0/interceptors.yaml

Upgrade Notices

  1. As of this release, the Triggers release will contain two YAML files. release.yaml contains the core release artifacts while interceptors.yaml contain the 4 core interceptors (GitHub, GitLab, BitBucket, and CEL).

  2. The EventListener ServiceAccount will now need a ClusterRole (and corresponding ClusterRoleBinding) to use the new ClusterInterceptor types (example)

How to upgrade from v0.12.1 :up_arrow:

  • Apply the new releases
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.13.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.13.0/interceptors.yaml
  • Update your EventListener's ServiceAccount so that it can access ClusterInterceptors:
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: tekton-triggers-example-clusterrole
rules:
  # EventListeners need to be able to fetch any clustertriggerbindings
- apiGroups: ["triggers.tekton.dev"]
  resources: ["clustertriggerbindings", "clusterinterceptors"]
  verbs: ["get", "list", "watch"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: tekton-triggers-example-clusterbinding
subjects:
- kind: ServiceAccount
  name: tekton-triggers-example-sa
  namespace: default
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: tekton-triggers-example-clusterrole

Changes

Features

  • ✨ Adding label selector for triggers (#970)

    Users can now configure triggers for an EventListener using labels

  • ✨ Added URL field to WebhookInterceptor (#1002)

    Users can now configure webhook interceptors by referencing a URL

  • ✨ Add ClusterInterceptor CRD for registering interceptors (#960)

    A new CRD called ClusterInterceptor has been added that allows for users to register new pluggable Interceptor types

  • ✨ Add API to configure Interceptors from a Trigger (#1001)

    Trigger spec authors can now configure interceptors using a new API that includes a ref field to refer to a ClusterInterceptor, and
    a params field to add parameters to pass on to the interceptor for processing

  • ✨ Migrate core interceptors to use InterceptorType CRD (#976)

    The four bundled interceptors (CEL, GitHub, GitLab, BitBucket) are now implemented using the new ClusterInterceptor CRD

  • ✨ Migrate core interceptors to new format (#1029)

    Any new Triggers created using the old style syntax for core interceptors is now automatically switched to the new refs/params
    based syntax.

Deprecation Notices

  • 🚨 Move replicas to KubernetesResource from eventlistener spec (#1021)

    Deprecated replicas from EventListener spec level and added replicas to KubernetesResource.

  • 🚨 Migrate core interceptors to new format (#1029)

    Interceptors in a Trigger are now configured using a new ref and params based syntax as described in #1001, and in #976 we
    have implemented the core interceptors using the new ClusterInterceptor CRD. So, these core interceptors can now be configured
    using the new syntax. The old way of configuring these interceptors is now deprecated but it will continue to work until it is removed
    in a future release. The defaulting webhook will automatically switch any usages of the old syntax to the new for any new Triggers.

Fixes

  • πŸ› Forcing eventlistener sink to resolve eventlistener before startup (#977)
  • πŸ› resources: Fail on non-string template labels. (#1030)
  • πŸ› Resolving file read issue with binding-eval (#1039)
  • πŸ› Resolving cache sync issues (#1037)
  • πŸ› Fixes Triggers release pipeline and tasks (#1024)
  • πŸ› Cleanup existing k8s resources after updating to customeResources (#1022)
  • πŸ› Update selector RBAC to include ClusterInterceptor (#1016)
  • πŸ› Sync lister informers before serving traffic (#1013)
  • πŸ› fix: Cron task needs to post json body (#989)

Misc

  • πŸ”¨ Update triggers, community and cli reference to use main… (#987)
  • πŸ”¨ Use v1 API for RoleBinding 🦝 (#1046)
  • πŸ”¨ Add separate interceptors file result to release pipeline (#1044)
  • πŸ”¨ Update publish task to include core interceptors (#1007)
  • πŸ”¨ Update Release Pipeline and associated Task πŸ§‘β€πŸ’» 😺 (#1000)
  • πŸ”¨ Add links to versioned docs for v0.12.1 (#999)

Docs

  • πŸ“– Rewrite the Triggers tutorial for clarity and flow (#1018)
  • πŸ“– Delete obsolete file (#1011)
  • πŸ“– Replace debugging-eventlisteners.md with the new Troubleshooting page (#1010)
  • πŸ“– Rewrite debugging-eventlisteners.md for clarity and flow (#1004)
  • πŸ“– Rewrite triggers.md for clarity and flow (#992)
  • πŸ“– Update descriptions for TriggerTemplates and TriggerBindings (#991)
  • πŸ“– Rewrite triggerbindings.md for clarity and flow (#988)
  • πŸ“– Rewrite triggertemplates.md for clarity and flow (#981)
  • πŸ“– Update examples to use both old and new syntax (#1028)
  • πŸ“– Update eventlisteners.md (#993)
  • πŸ“– Correct eventlistener docs to properly set service account for a trigger (#984)
  • πŸ“– Add link to versioned docs for v0.12.0 (#982)
  • πŸ“– fix a typo (#979)
  • πŸ“– Fix broken link to Getting Started (#978)

Thanks

Thanks to these contributors who contributed to v0.13.0!

Extra shout-out for awesome release notes:

To Be Done: Deprecation Notices, Backward Incompatible Changes