reference existing adrs

cloudoperators · Jul 8, 2024 · dbf8875 · dbf8875
1 parent e375abb
commit dbf8875
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/architecture-decision-records/Greenhouse-ADR-3-location_of_plugins.md b/architecture-decision-records/Greenhouse-ADR-3-location_of_plugins.md
@@ -35,6 +35,10 @@ During developement the question got raised whatever it is a good decision/archi
 > User story: Customer onboards a newly created cluster and requires an Ingress to expose applications. Via Greenhouse the Ingress Plugin can be configured which results in a deployment of the ingress controller within the customer cluster.
 > The PluginConfig, dashboard reflects the  current status of relevant underlying resources.
 
+## Related Decision Records
+
+Superseded by [Greenhouse-ADR-6-central_cluster.md](Greenhouse-ADR-6-central_cluster.md)
+
 ## Decision Drivers
 
 * Should work with/ focus on the for MVP in scope Applications

diff --git a/architecture-decision-records/Greenhouse-ADR-6-central_cluster.md b/architecture-decision-records/Greenhouse-ADR-6-central_cluster.md
@@ -44,7 +44,7 @@ Use cases being:
 
 ## Related Decision Records
 
-N/A
+Supersedes [Greenhouse-ADR-3-location_of_plugins.md](Greenhouse-ADR-3-location_of_plugins.md)
 
 ## Decision Drivers
-Original file line number
+Diff line change
@@ Expand Up / @@ -44,7 +44,7 @@ Use cases being: @@
     ## Related Decision Records
-    N/A
+    Supersedes [Greenhouse-ADR-3-location_of_plugins.md](Greenhouse-ADR-3-location_of_plugins.md)
     ## Decision Drivers
@@ Expand Down @@