Merge pull request #54 from Kuadrant/issue-numbers

Add missing tracking issues to merged RFCs
Kuadrant · Feb 7, 2024 · e2732ff · e2732ff
2 parents b492d9d + 624ba35
commit e2732ff
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/rfcs/0002-well-known-attributes.md b/rfcs/0002-well-known-attributes.md
@@ -3,6 +3,7 @@
 - Feature Name: `well-known-attributes`
 - Start Date: 2023-06-13
 - RFC PR: [Kuadrant/architecture#17](https://github.com/Kuadrant/architecture/pull/17)
+- Issue tracking: [Kuadrant/architecture#53](https://github.com/Kuadrant/architecture/issues/53)
 
 # Summary
 [summary]: #summary

diff --git a/rfcs/0003-dns-policy.md b/rfcs/0003-dns-policy.md
@@ -3,7 +3,7 @@
 - Feature Name: DNSPolicy
 - Start Date: 2023-07-01
 - RFC PR: [Kuadrant/architecture#20](https://github.com/Kuadrant/architecture/pull/20)
-- Issue tracking: [Kuadrant/architecture#0000](https://github.com/Kuadrant/multicluster-gateway-controller/issues/219)
+- Issue tracking: [Kuadrant/multicluster-gateway-controller#219](https://github.com/Kuadrant/multicluster-gateway-controller/issues/219)
 - Labels: DNS, Load Balancing, Multi-Cluster
 
 
@@ -287,4 +287,5 @@ However, there is still significant value even with this limitation. This limita
 # Rationale and alternatives
 [rationale-and-alternatives]: #rationale-and-alternatives
 
-An alternative is to configure all of this yourself manually in a dns provider. This is can be a highly complex dns configuration that it would be easy to get wrong. 
+An alternative is to configure all of this yourself manually in a dns provider. This is can be a highly complex dns configuration that it would be easy to get wrong.
+