Source File: github.com/solo-io/gloo/projects/gloo/api/v1/upstream.proto
Upstreams represent destination for routing HTTP requests. Upstreams can be compared to
clusters in Envoy terminology.
Each upstream in Gloo has a type. Supported types include
consul, and more.
Each upstream type is handled by a corresponding Gloo plugin.
"upstreamSpec": .gloo.solo.io.UpstreamSpec "status": .core.solo.io.Status "metadata": .core.solo.io.Metadata "discoveryMetadata": .gloo.solo.io.DiscoveryMetadata
||.gloo.solo.io.UpstreamSpec||Type-specific configuration. Examples include static, kubernetes, and aws. The type-specific config for the upstream is called a spec.|
||.core.solo.io.Status||Status indicates the validation status of the resource. Status is read-only by clients, and set by gloo during validation.|
||.core.solo.io.Metadata||Metadata contains the object metadata for this resource.|
||.gloo.solo.io.DiscoveryMetadata||Upstreams and their configuration can be automatically by Gloo Discovery if this upstream is created or modified by Discovery, metadata about the operation will be placed here.|
created by discovery services