Cleanup wording and decisions on various ADRs (#13068)

Signed-off-by: Derek Nola <derek.nola@suse.com>

docs/adrs/add-auto-import-containerd.md

@@ -4,7 +4,7 @@ Date: 2024-10-2
 
 ## Status
 
-Proposed
+Accepted
 
 ## Context
 
@@ -42,7 +42,7 @@ When the controller receive a event saying that a file was renamed, or removed,
 
 ## Decision
 
-- Decided
+- We will implement auto importing of images in the containerd image store, by using a watcher on the agent/images folder.
 
 ## Consequences
 

docs/adrs/flannel-options.md

@@ -4,7 +4,7 @@ Date: 2023-2-16
 
 ## Status
 
-Discussing
+Not Approved
 
 ## Context
 
@@ -112,6 +112,6 @@ The naming of the flag could be `flannel-arg`, but I don't want users to assume
 
 ## Decision
 
-
+The amount of flannel options has stablized at a low number. The benefit of reducing the number of flags is low, and the risk of breaking existing users is high.
 
 ## Consequences

docs/adrs/integrate-vpns.md

@@ -4,7 +4,7 @@ Date: 2023-04-26
 
 ## Status
 
-Under review
+Accepted
 
 ## Context
 
@@ -57,7 +57,7 @@ Going a bit deeper into the code, this is a high-level summary of the changes ap
 
 ## Decision
 
-???
+We will integrate tailscale into k3s. The user will be required to have a: the tailscale binary on the node, a tailscale account, and provide the tailscale authkey to k3s.
 
 ## Consequences
 

docs/adrs/multus.md

@@ -4,7 +4,7 @@ Date: 2024-04-15
 
 ## Status
 
-Dismissed
+Denied
 
 ## Context
 

docs/adrs/status-for-etcd-node.md

@@ -4,7 +4,7 @@ Date: 2023-09-14
 
 ## Status
 
-Decided
+Accepted
 
 ## Context
 

docs/adrs/testing-2024.md

@@ -2,9 +2,13 @@
 
 Date: 2024-02-23
 
-# Context
+## Status
 
-## Background
+Accepted
+
+## Context
+
+### Background
 
 Currently, Testing in K3s is categorized into various types and spread across Github Actions and Drone CI. The types are as follows:
 
@@ -24,14 +28,14 @@ Drone CI:
 
 - Performance Tests: Use Terraform to test large-scale deployments of K3s clusters. These were legacy tests and are never run in CI.
 
-## Problems
+### Problems
 
 - The current testing infrastructure is complex and fragmented, leading to maintenance overhead. Not all testing is grouped inside the [tests directory](../../tests/).
 - GitHub Actions had limited resources, making it unsuitable for running larger tests.
 - GitHub Actions only supported hardware virtualiztion on Mac runners and that support was often broken.
 - Drone CI cannot handle individual testing failures. If a single test fails, the entire build is marked as failed.
 
-## New Developments
+### New Developments
 
 As of late January 2024, GitHub Actions has made significant improvements:
 - The resources available to open source GitHub Actions have been doubled, with 4 CPU cores and 16GB of RAM. See blog post [here](https://github.blog/2024-01-17-github-hosted-runners-double-the-power-for-open-source/).