Dear product owners and engineering team leads, this is an update on the progress of removal of the legacy private DNS zone we've announced 2 months ago. Completion of this initiative will unblock switch to Multi-Account Infrastructure and increase agility of all engineering product teams. For more info see project document and timeline.
As part of stage (I-A) teams in 3 out of 35 product domains have identified 6 old private zone records their applications depend on. Product teams had 2 months to find and stop use of old DNS records in their apps and make a couple of consequent releases to prevent regressions during rollbacks. With the absence of information to the contrary, we believe this stage of the project has been successfully completed.
Stage (I-B) was started 4 weeks late, however TechOps are actively working with the owners of these MongoDB instances to rlconfigure them in the coming weeks [1]. We couldn't start this labour intensive stage until last week, but we expect to complete it in 2-3 weeks. Since none of the product teams listed MongoDB hostnames as their application dependencies, we believe all applications already using new private zone records (e.g. data-mongod-01.main.tvlk.cloud) instead of old (e.g. mongodata01.traveloka.com) and will not be impacted by the removal of old DNS records after replica set reconfiguration is complete.
Stage (II-A) - the removal of known orphaned records have already been completed by TechOps [2],[3], leaving only the following records remaining. Most of these are MongoDB records, known application dependencies and some records we are not yet sure are safe to remove.
Stage (II-B) - the removal of remaining records will begin immediately after stage (I-B) is complete. We believe that product team have done the due diligence in identifying and removing these from their applications and thus are safe to delete. We strongly advise that each product team double check these records before they are deleted from production environment.
Stage (III) - deletion of the old private DNS zone will be executed after stage (II-B).
Thank you for your assistance in removing this large and complex technical debt and helping TechOps create a much better decentralized infrastructure platform for all.