IncrementalMeshConfigRequest are be sent in 2 situations: 1.

IncrementalMeshConfigResponses do not need to include a full snapshot of the tracked resources.

A MeshConfigRequest requests a set of versioned resources of the same type for a given client.

A MeshConfigResponse delivers a set of versioned resources of the same type in response to a MeshConfigRequest.

Metadata information that all resources within the Mesh Configuration Protocol must have.

A RequestResource can be sent in two situations: Initial message in an MCP bidirectional change stream as an ACK or NACK response to a previous Resources.

Resource as transferred via the Mesh Configuration Protocol.

Resources do not need to include a full snapshot of the tracked resources.

Identifies a specific MCP sink node instance.

AggregatedMeshConfigServiceClient is the client API for AggregatedMeshConfigService service.

AggregatedMeshConfigServiceServer is the server API for AggregatedMeshConfigService service.

ResourceSinkClient is the client API for ResourceSink service.

ResourceSinkServer is the server API for ResourceSink service.

ResourceSourceClient is the client API for ResourceSource service.

ResourceSourceServer is the server API for ResourceSource service.