Event-driven application platform for Kubernetes
Go to file
Knative Automation 7a5486b8a6
[main] Upgrade to latest dependencies (#8590)
upgrade to latest dependencies

bumping knative.dev/reconciler-test 10479dd...f46fa65:
  > f46fa65 upgrade to latest dependencies (# 796)
bumping google.golang.org/grpc a43eba6...4cf3cf7:
  > 4cf3cf7 Change version to 1.72.1 (# 8319)
  > 537fe8d transport: Propagate status code on receiving RST_STREAM during message read (# 8289) (# 8317)
  > f32eab3 cherry-pick # 8302 and # 8304 to v1.72.x branch (# 8303)
  > 7fcfc87 internal/delegatingresolver: avoid proxy if networktype of target address is not tcp (# 8215) (# 8296)
  > ad1e120 Change version to 1.72.1-dev (# 8219)
bumping knative.dev/pkg 19a1383...44579e9:
  > 44579e9 Bump google.golang.org/grpc from 1.72.0 to 1.72.1 (# 3180)
  > 873230f upgrade to latest dependencies (# 3179)

Signed-off-by: Knative Automation <automation@knative.team>
2025-05-21 12:31:31 +00:00
.github Update k8s version in e2e tests (#8503) 2025-02-25 12:15:21 +00:00
cmd Event Transform JSONata TLS (#8515) 2025-03-10 11:39:04 +00:00
config Allow setting finalizers for EventTransform reconciler (#8534) 2025-03-19 14:05:15 +00:00
docs fix a typo in broker readme: kantive (#8573) 2025-04-25 14:02:25 +00:00
hack Prevent knative-nightly integrations image references from being released (#8521) 2025-03-19 17:57:15 +00:00
pkg Try to ensure ordering of referenced source CMs, by name (#8589) 2025-05-16 14:38:49 +00:00
sample Update the link of the sample code.(#6374) (#6375) 2022-05-11 13:55:34 +00:00
support Update support rotation (#6351) 2022-04-28 15:42:53 +00:00
test Fix EventTransform with TLS Sink test (#8537) 2025-03-21 06:41:17 +00:00
third_party [Automated] Update eventing-eventing-integrations nightly (#8571) 2025-04-24 12:09:26 +00:00
vendor [main] Upgrade to latest dependencies (#8590) 2025-05-21 12:31:31 +00:00
.codecov.yaml 🐛 Codecov reject any coverage drop (#8065) 2024-07-03 14:58:20 +00:00
.gitattributes Removing PubSub contrib (#1598) 2019-08-07 13:06:56 -07:00
.gitignore Added .env files to the gitignore (#7162) 2023-08-10 13:24:40 +00:00
.golangci.yaml Migrate golanglint-ci config to v2 (#8557) 2025-04-11 20:09:14 +00:00
.ko.yaml Adopt the :nonroot base image (#2429) 2020-01-23 09:00:24 -08:00
AUTHORS Adding VMware to AUTHORS. (#2295) 2019-12-10 10:21:47 -08:00
CODE-OF-CONDUCT.md Adding code of conduct to reference knative/community's CoC (#6281) 2022-03-21 07:20:47 -07:00
CONTRIBUTING.md Format markdown (#2612) 2020-02-20 07:00:06 -08:00
DEVELOPMENT.md chore: fix lint errors (#8089) 2024-07-10 05:35:20 +00:00
LICENSE Initial commit 2018-03-12 14:08:30 -07:00
OWNERS Add knative-release-leads to OWNERS (#5405) 2021-05-18 08:35:15 -07:00
OWNERS_ALIASES [main] Update community files (#8570) 2025-04-24 01:37:25 +00:00
README.md Added clotributor link to readme (#7252) 2023-09-13 05:05:32 +00:00
SECURITY.md Make SECURITY.md consistent (#7460) 2023-11-20 17:58:41 +00:00
go.mod [main] Upgrade to latest dependencies (#8590) 2025-05-21 12:31:31 +00:00
go.sum [main] Upgrade to latest dependencies (#8590) 2025-05-21 12:31:31 +00:00

README.md

Knative Eventing - The Event-driven application platform for Kubernetes

Secure event processing and discovery with CloudEvents

go.dev reference Go Report Card Releases LICENSE codecov TestGrid Slack Slack CII Best Practices

What is Knative Eventing?

Knative Eventing is a collection of APIs that enable you to use an event-driven architecture with your applications. You can use these APIs to create components that route events from event producers (known as sources) to event consumers (known as sinks) that receive events. Sinks can also be configured to respond to HTTP requests by sending a response event.

Knative Eventing is a standalone platform that provides support for various types of workloads, including standard Kubernetes Services and Knative Serving Services.

Knative Eventing uses standard HTTP requests to route events from event producers to event consumers, following the rules set by the CloudEvents specification. This is a standard set up by the CNCF that has wide support for many programming languages, making it easy to create, understand, send, and receive events.

Knative Eventing components are loosely coupled, and can be developed and deployed independently of each other. Any producer can generate events before there are active event consumers that are listening for those events. Any event consumer can express interest in a class of events before there are producers that are creating those events.

What to expect here?

This repository contains an eventing system that is designed to address a common need for cloud native development:

  1. Services are loosely coupled during development and deployed independently
  2. A producer can generate events before a consumer is listening, and a consumer can express an interest in an event or class of events that is not yet being produced.
  3. Services can be connected to create new applications
    • without modifying producer or consumer, and
    • with the ability to select a specific subset of events from a particular producer.

More on Knative Eventing

The high level mission of Knative Eventing is: Enable asynchronous application development through event delivery from anywhere.

For the full mission of Knative Eventing see docs/mission.md.

For complete Knative Eventing documentation, see Knative eventing or Knative docs to learn about Knative.

If you are interested in contributing, see the ready to work issues, CONTRIBUTING.md, DEVELOPMENT.md and Knative working groups.

Interested users should join knative-users.