From 8b895fee06421e6dd9eb4e36db2ddde5da92ef8a Mon Sep 17 00:00:00 2001
From: vincent <vincent@ducamps.win>
Date: Sun, 17 Mar 2024 11:04:56 +0100
Subject: [PATCH] docs: update ADR

---
 docs/ADR/004-DNS.md              | 15 +++++++++++++++
 docs/ADR/006-Docker-pull-through | 25 +++++++++++++++++++++++++
 2 files changed, 40 insertions(+)
 create mode 100644 docs/ADR/006-Docker-pull-through

diff --git a/docs/ADR/004-DNS.md b/docs/ADR/004-DNS.md
index deebfb2..0b79c27 100644
--- a/docs/ADR/004-DNS.md
+++ b/docs/ADR/004-DNS.md
@@ -100,3 +100,18 @@ agains:
 put one recursor on cluster over authority server and keep the recursor on gerard for better recundancy
 
 ### Consequences
+
+
+## 005 physical Recursor location
+
+### Status
+
+done
+
+### Context
+
+following NAS migration physical DNS Recursor was install directly on NAS this bring a SPOF when NAS failed Recursor on Nomad cluster are stopped because of volume dependance 
+
+### Decision
+
+Put physical Recursor on a cluster node like that to have a DNS issue we need to have NAS and this nomad down on same Time
diff --git a/docs/ADR/006-Docker-pull-through b/docs/ADR/006-Docker-pull-through
new file mode 100644
index 0000000..a1519cd
--- /dev/null
+++ b/docs/ADR/006-Docker-pull-through
@@ -0,0 +1,25 @@
+# Docker Pull throught
+
+# 001  architecture consideration
+
+## Status
+
+Accepted
+
+## Context
+
+docker hub get a pull limit if somebody go wrong on our infrastructure we can get quickyly this limit solution will be to implement a pull throught proxy.
+
+
+### Decision
+
+create two container task to create a dockerhub pull through and a ghcr one 
+
+we can add these registry to traefick to have both under the port 5000 but this will add a traefik dependancy on rebuild
+
+so to begin we will use one trafick service on two diferent static port
+
+## Consequences
+
+- this registry need to be start first on cluster creation
+- need to update all job image with local proxy url