Event source

As explained in Google Anthos in Action

An event source is a component that obtains events from an authoritative system and delivers them to Knative Eventing.

An event source obtains events from an authoritative system and delivers them to Knative Eventing. It acts as the control-plane component that sends events to a Broker, separating event acquisition from filtering and routing. section 9.3.3

Event sources support these deployment patterns:

• Use one of roughly 20 predefined sources for common external or in-cluster systems. section 9.3.3
• Develop a custom source when the required authoritative system is not already supported. section 9.3.3
• Deliver events into a Broker, where Triggers filter and route them to Knative or Kubernetes Services. section 9.3.3

Cloud Pub/Sub source

A CloudPubSubSource reads the testing topic and sends events to the event-display Service through its sink reference.

Figure 9.7 How an event source works

Trace how an event source obtains events and delivers them into the Knative Eventing pipeline. section 9.3.3

How Google Anthos in Action covers it

How deep it goes

Explains source responsibility and pipeline placement, but defers detailed source implementation.

Examples

Uses a CloudPubSubSource configured with a topic and event-display Service sink.

What it assumes

Assumes an authoritative event system and Knative Eventing resources, while distinguishing source, Broker, and Trigger responsibilities.

What you can do after

Build a custom source or configure a predefined source to deliver events to a Broker.

How it connects

Connects Brokers, Triggers, CloudEvents, Knative Services, and Kubernetes Services.

liveBookmanning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Platform Engineering on KubernetesAn event source is a component that produces events and exposes them for delivery to event consumers.

Compare how 2 books explain event source →

Related concepts

• reactor patternpart of · The reactor pattern is an event-driven concurrency pattern that demultiplexes readiness notifications and dispatches them to handlers, typically through a single event loop.
• control plane nodehas part · A control plane node is a Kubernetes cluster machine that hosts components managing cluster state, exposing the cluster API, scheduling workloads, and coordinating operations.
• Kubernetes resourcekind of · A Kubernetes resource is a persistent API-managed object representing the desired or observed state of a workload, configuration, or other cluster entity.
• Knative Eventinghas part · Knative Eventing is a Kubernetes-based system for obtaining, routing, and delivering events between sources, brokers, triggers, and targets.

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.