Why do I get a
not found error when adding an endpoint?
If you find yourself getting 404 errors when adding services or endpoints, ensure that you have created both the namespace and the service (in that order) before adding an endpoint. The service must exist before you can add additional endpoints.
When I look up a service, why don't I get any of my endpoints?
Ensure that the project, region, namespace name, and service name are all correct in your request and match where you registered the endpoints. All Service Directory services live in a regional namespace so services registered with one region will not match data in a separate region.
I granted someone access to a service but they continue to get
This could be for a couple of reasons. First, check that the region is correct.
If you set a policy on a namespace or service, it only applies for that
particular region. If the user is trying to register or lookup the same service
in another region, they won't have access unless you grant them IAM access to
that regional service as well. To debug access issues, try the
TestIamPermissions method for services and registries.
I added some endpoints and then removed the service backend. Why are the endpoints still there?
Service Directory does not do automatic health-checking or heartbeating and will not remove endpoints unless you explicitly remove them. Ensure that you add code to your service backends/orchestrators that will remove the endpoint from Service Directory once it no longer exists. We encourage the use of time-to-live metadata fields on endpoints to record the last time an endpoint was registered or updated.
I am able to look up endpoints but everytime I try to connect to them, it fails
Service Directory does not ensure the reachability from the client. Services register their endpoints directly with Service Directory. However, the address registered with Service Directory may not be routable (especially if both the client and the server are on separate private networks). If the endpoint is routable from the client, then it could be due to an unhealthy endpoint. Please see the next question below.
How can I add health data for endpoints so my clients know which one to connect to?
When using client-side load balancing, we recommend service backends occasionally update a metadata field on the endpoint that clients can use to make decisions on which backend to connect to. Service Directory does not inspect or evaluate this data.
I've created a namespace. Why can't I assign a Cloud DNS private zone to it?
Ensure that you have the
permission for the namespace as this is what allows you to create the associated
private zone. By default, the Project Editor, Project Owner, Service Directory
Admin and Service Directory Editor roles have this permission.
When I do a DNS lookup of a service, why don't I get any of my endpoints?
There could be a number of reasons, such as the following:
- The associated namespace has been deleted. You can check this by doing a
get on the private zone. If the
serviceDirectoryConfig.deletionTimeis set, then the associated namespace has been deleted, and so have all of its endpoints.
- Confirm you are issuing the request from a network that is allowed to query the private zone. You can find the network list by doing a get on the private zone.
- There are no (valid) endpoints for the service. Do a resolve on the service through the Service Directory API to ensure that the service is not empty and has at least one valid endpoint IP. DNS support is only available for endpoints with valid ipv4 or ipv6 IP addresses.
- Make sure you're querying the correct zone. For example, suppose you create a Service Directory zone called example.com and you have another (standard) private zone named billing.example.com. Then any DNS query to billing.example.com will return resource records that belong to the billing.example.com zone, and not the billing service in the Service Directory namespace that is associated with example.com. For more information, see VPC name resolution order.