This document contains current content limits and request quotas for Service Directory. This page will be updated to reflect any changes to these restrictions and usage limits.
Service Directory has the following quotas:
- Namespaces per project per region
- Services per Namespace per resource per region
- Endpoints per Service per resource per region
- Registration requests per minute per region
- Lookup requests per minute per region
You can see your existing quotas and usage on the quotas page.
General Service Directory limitations:
- There is no health-status or health-checking for endpoints. There
are two alternatives:
- Use internal load balancers for integrated health-checking and register the load-balancer with Service Directory.
- Store individual endpoint health status as endpoint metadata in Service Directory.
Cloud DNS integration limits:
- The Cloud DNS integration only serves endpoints that are a valid IPv4 or IPv6 address. Any endpoints that are registered that do not have a valid IP address are ignored by DNS requests.
- SRV records cannot be customized. The symbolic service, protocol, TTL, weight, and priority are managed by Service Directory.
- Service and endpoint metadata is not served in DNS requests. If your service needs to make use of custom metadata, it should use HTTP support in Service Directory.
- You cannot add resource records to the Service Directory zone. Only resource records generated internally from existing Service Directory endpoints are allowed.