Skip to main content

GCP Service Directory Endpoint

A GCP Service Directory Endpoint represents the concrete network location (IP address and optional port) where a Service Directory Service can be reached. Each endpoint is registered within a namespace and service, allowing clients and service-discovery tooling to resolve the actual back-end instance that fulfils a request. Endpoints can point at resources inside or outside Google Cloud, and may include additional metadata such as network, annotations or health information.
For full details see the official documentation: https://cloud.google.com/service-directory/docs/reference/rest/v1/projects.locations.namespaces.services.endpoints

Terrafrom Mappings:

  • google_service_directory_endpoint.id

Supported Methods​

  • GET: Get a gcp-service-directory-endpoint by its "locations|namespaces|services|endpoints"
  • LIST
  • SEARCH: Search for endpoints by "location|namespace_id|service_id" or "projects/[project_id]/locations/[location]/namespaces/[namespace_id]/services/[service_id]/endpoints/[endpoint_id]" which is supported for terraform mappings.

ip​

An endpoint ultimately resolves to a specific IP address (and optional port). This link exposes the underlying IP object so that Overmind can correlate the endpoint with other infrastructure and detect conflicts, overlaps or missing routes.

gcp-compute-network​

If the endpoint’s IP resides inside a Google Cloud VPC, it is associated with a particular Compute Network. Linking to gcp-compute-network allows Overmind to trace how traffic flows to the endpoint, analyse firewall rules, and surface risks such as network isolation or mis-configured routing.