You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
epp: generalize endpoint identity and add endpoint type
Rename EndpointMetadata.PodName to Name -- the endpoint model is not
Kubernetes-only (file-discovered endpoints have no pod) and NamespacedName is the
identity. Name is always set, so classifying an endpoint no longer requires
blanking its identity.
Add EndpointMetadata.Type (EndpointTypeEngine, EndpointTypeEPP): what an endpoint
is, independent of how it was discovered. Engines are discovered from Pod objects
or from a file and are still engines; an EPP endpoint publishes aggregates over
the servers it schedules rather than engine metrics. The Kubernetes pod path sets
engine, and file-discovery parses the entry's type field, defaulting to engine and
rejecting unknown values.
The type is an attribute set at creation rather than a label, and the metrics
extractor is unchanged: EPP metrics warrant their own extractor rather than
overloading engine type.
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
0 commit comments