unparametrise, github does not support it

..nor does it support yaml anchors so back to hacks.

Signed-off-by: clux <[email protected]>

.github/workflows/ci.yml

@@ -4,8 +4,6 @@ on:
 
 env:
   RUST_BACKTRACE: 1
-  K3S_MAX: "latest"
-  K3S_MIN: "v1.28"
 
 # Spend CI time only on latest ref: https://docs.github.com/en/actions/using-jobs/using-concurrency
 concurrency:
@@ -134,7 +132,9 @@ jobs:
       fail-fast: false
       matrix:
         # Run these tests against older clusters as well
-        k8s: ["${{env.K3S_MIN}}", "${{env.K3S_MAX}}"]
+        k8s:
+        - "1.27" # MK8SV
+        - "latest"
     steps:
       - uses: actions/checkout@v4
       - uses: dtolnay/rust-toolchain@stable
@@ -200,7 +200,7 @@ jobs:
 
       - uses: nolar/setup-k3d-k3s@v1
         with:
-          version: "${{ env.K3S_MIN }}"
+          version: "1.27" # MK8SV
           # k3d-kube
           k3d-name: kube
           # Used to avoid rate limits when fetching the releases from k3s repo.

.github/workflows/coverage.yml

@@ -12,8 +12,6 @@ on:
 
 env:
   RUST_BACKTRACE: 1
-  K3S_MAX: "latest"
-  K3S_MIN: "v1.28"
 
 jobs:
   tarpaulin-codecov:
@@ -31,7 +29,7 @@ jobs:
           tool: [email protected]
       - uses: nolar/setup-k3d-k3s@v1
         with:
-          version: "${{ env.K3S_MIN }}"
+          version: "v1.27" # MK8SV
           # k3d-kube
           k3d-name: kube
           # Used to avoid rate limits when fetching the releases from k3s repo.