DNS Management Service

[davidffrench]

Context

DNS management is a common concern for all fleet managers to ensure a consistent format of the service URL exposed for all separate managed service instances. A shared service will also reduce the shared code across managed services.

User Narrative

Samantha is a development lead working for Corporate Inc. She is building a new managed service and needs to follow the company guidelines on URL naming for managed service instance URLs. Samantha onboards with the DNS management service and integrates the new managed service to it, ensuring that there is a record created in the company DNS service Route53 for each new service instance.

Liam is a developer working for Customer Inc and has started using 3 different managed services from Coporate Inc. Liam has noticed that the same domain name is used for each of the managed services with a different subdomain for each of the managed service. This strengthens Liams professional opinion on Corporate Inc.

Job Stories

• As a managed service developer, I want clear onboarding documentation for the DNS management service, so that I know what information is required from my team.
• As a managed service developer, I want clear authentication and authorisation documentation for the DNS management service, so that I know what prerequisites I need to complete.
• As a managed service developer, I want API documentation for the DNS management service, so that I know how to integrate with the service.

Analysis

(links to analysis docs containing architecture design work, requirements gathering, etc)

Task List

• [ ]

[miguelsorianod]

I've been taking a look at the tasks related to DNS that KAS Fleet Manager performs. It is basically one task:

• Create CNAME records in a Route53's hosted zone. Those CNAME records point to some routes belonging to the data plane. Those routes are reported from the Data Plane to KAS Fleet Manager.

The interaction with Route53 is done through a wrapper that there is in KAS Fleet Manager on top of AWS Route53. As of now, can't see a clear advantage of having a whole new DNS service vs just using the library to interact with the DNS service in Fleet Manager. In both cases fleet manager code has to interact with an API that manages DNS. In the case multiple providers are needed another implementation of the interface could be written or even converted to a library. At the moment I think having a whole new service/api for this would be over-engineering at this point. Let's let people design their fleet manager and if we are reported new real use cases or pain points around this we can reevaluate / explore further this possibility.

[machi1990]

At the moment I think having a whole new service/api for this would be over-engineering at this point. Let's let people design their fleet manager and if we are reported new real use cases or pain points around this we can reevaluate / explore further this possibility.

+1