Event adapter

As explained in Google Anthos in Action

An event adapter is a component that understands a source-specific event format and translates it into CloudEvents.

An event adapter understands a source-specific event format and translates it into the common CloudEvents format. Knative Eventing then makes the normalized event available for a Broker. section 9.3.3

Adapters participate in event-source delivery as follows:

• Receive events through push or pull operations, depending on the source capability. section 9.3.3
• Validate and convert source data into CloudEvents before handing it to the Broker. section 9.3.3
• Operate within a data plane configured by the event source’s control plane, which creates subscriptions or webhooks and handles cleanup. section 9.3.3

Google Cloud Pub/Sub source

A CloudPubSubSource can watch the testing topic and send published messages to a Kubernetes Service. Its adapter converts the Pub/Sub payload into CloudEvents for downstream Broker processing. section 9.3.3

Figure 9.7 How an event source works

Trace the path from an event source through its adapter and into the Broker. section 9.3.3

How Google Anthos in Action covers it

How deep it goes

Explains push and pull delivery, validation, conversion, and control/data-plane responsibilities without detailing adapter implementation.

Examples

Uses a Google Cloud Pub/Sub topic, CloudPubSubSource, Kubernetes Service sink, and Broker delivery path.

What it assumes

Assumes familiarity with Kubernetes services and event sources while defining adapter, control-plane, and data-plane roles.

What you can do after

Operate Knative Eventing sources that deliver normalized CloudEvents to Brokers and downstream services.

How it connects

Connects event sources, CloudEvents, Brokers, control planes, data planes, and Knative Triggers.

liveBookmanning.com

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

Related concepts

• CloudEventsproduces · CloudEvents is an open standard for describing event data in a common, interoperable format independent of transport, technology, or platform.

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.