.github/workflows: rebalance pr-kubernetes-tests

.github/workflows/pr-kubernetes-tests.yaml

@@ -50,27 +50,36 @@ jobs:
         # Our goal is to load balance tests in a way that allows quick iteration on PRs
         # If tests are exceeding the 25-minute limit, please see:
         # /test/kubernetes/e2e/load_balancing_tests.md
+        #
+        # Above each test below, we document the latest date/time for the GitHub action step to run
+        # NOTE: We use the GitHub action step time (as opposed to the `go test` time), because it is easier to capture
+
         test:
-        # August 6, 2024: 23 minutes execution time (see load_balancing_tests.md)
+        # September 16, 2024: 22 minutes
         - cluster-name: 'cluster-one'
           go-test-args: '-v -timeout=25m'
-          go-test-run-regex: '^TestGloomtlsGatewayEdgeGateway$$|^TestK8sGateway$$/^RouteDelegation$$|^TestK8sGateway$$/^Services$$|^TestGlooctlGlooGatewayEdgeGateway$$|^TestGlooctlK8sGateway$$|^TestHelm$$'
+          go-test-run-regex: '^TestK8sGateway$$/^RouteDelegation$$|^TestK8sGateway$$/^Services$$|^TestGlooctlGlooGatewayEdgeGateway$$|^TestGlooctlK8sGateway$$'
 
-        # August 6, 2024: 27 minutes execution time (see load_balancing_tests.md)
+        # September 16, 2024: 16 minutes
         - cluster-name: 'cluster-two'
           go-test-args: '-v -timeout=25m'
-          go-test-run-regex: '^TestValidationStrict$$|^TestValidationAlwaysAccept$$|^TestTransformationValidationDisabled$$|^TestK8sGatewayIstioRevision$$|^TestRevisionIstioRegression$$|^TestK8sGateway$$/^Deployer$$|^TestK8sGateway$$/^RouteOptions$$|^TestK8sGateway$$/^VirtualHostOptions$$|^TestK8sGateway$$/^Upstreams$$|^TestK8sGateway$$/^HeadlessSvc$$|^TestK8sGateway$$/^PortRouting$$|^TestK8sGatewayMinimalDefaultGatewayParameters$$'
+          go-test-run-regex: '^TestK8sGatewayIstioRevision$$|^TestRevisionIstioRegression$$|^TestK8sGateway$$/^Deployer$$|^TestK8sGateway$$/^RouteOptions$$|^TestK8sGateway$$/^VirtualHostOptions$$|^TestK8sGateway$$/^Upstreams$$|^TestK8sGateway$$/^HeadlessSvc$$|^TestK8sGateway$$/^PortRouting$$|^TestK8sGatewayMinimalDefaultGatewayParameters$$'
 
-        # August 6, 2024: 26 minutes execution time (see load_balancing_tests.md)
+        # September 16, 2024: 21 minutes
         - cluster-name: 'cluster-three'
           go-test-args: '-v -timeout=25m'
           go-test-run-regex: '(^TestK8sGatewayIstioAutoMtls$$|^TestAutomtlsIstioEdgeApisGateway$$|^TestIstioEdgeApiGateway$$|^TestIstioRegression$$)'
 
-        # August 6, 2024: 24 minutes execution time (see load_balancing_tests.md)
+        # September 16, 2024: 23 minutes
         - cluster-name: 'cluster-four'
           go-test-args: '-v -timeout=25m'
           go-test-run-regex: '(^TestK8sGatewayIstio$$|^TestGlooGatewayEdgeGateway$$|^TestGlooctlIstioInjectEdgeApiGateway$$|^TestK8sGatewayNoValidation$$)'
 
+        # September 16, 2024: 17 minutes
+        - cluster-name: 'cluster-five'
+          go-test-args: '-v -timeout=25m'
+          go-test-run-regex: '^TestValidationStrict$$|^TestValidationAlwaysAccept$$|^TestTransformationValidationDisabled$$|^TestGloomtlsGatewayEdgeGateway$$|^TestHelm$$'
+
         # In our PR tests, we run the suite of tests using the upper ends of versions that we claim to support
         # The versions should mirror: https://docs.solo.io/gloo-edge/latest/reference/support/
         version-files:

changelog/v1.18.0-beta22/rebalance-kube-tests.yaml

@@ -0,0 +1,5 @@
+changelog:
+  - type: NON_USER_FACING
+    description: >-
+      Add cluster-five to the set of KinD clusters that execute our Kubernetes tests. This is to ensure
+      that our existing 4 clusters do not exceed the 25 minute time limit.

test/kubernetes/e2e/load_balancing_tests.md

@@ -29,7 +29,7 @@ Re-balancing of tests is intentionally a very easy action, though it shouldn't n
 - All clusters are exhausted, and we need to introduce a new cluster into the rotation
 
 ### Steps to take
-1. Review the recent results from CI, and capture them in a document under `test/kubernetes/e2e/load_balances/`
+1. Review the recent results from CI, and identify which tests can be migrated
 2. Adjust the run functions that are invoked in our [GitHub action matrix](/.github/workflows/pr-kubernetes-tests.yaml)
 4. Document the **new** results, on the matrix that runs the tests
 4. Open a PR clearly documenting in the PR body the results before and after the change