Fix Fleet deployment for AKS and GKE workflows

Now that sharding end-to-end test cases can be run without test infra, they are run in AKS and GKE workflows. Those workflows therefore require Fleet to be deployed with sharding enabled.
rancher · May 3, 2024 · 908a320 · 908a320
1 parent 4f1a2ec
commit 908a320
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/.github/workflows/aks.yml b/.github/workflows/aks.yml
@@ -126,7 +126,9 @@ jobs:
         run: |
           export KUBECONFIG="$GITHUB_WORKSPACE/kubeconfig-fleet-ci"
           echo "${{ steps.meta-fleet.outputs.tags }} ${{ steps.meta-fleet-agent.outputs.tags }}"
-          ./.github/scripts/deploy-fleet.sh ${{ steps.meta-fleet.outputs.tags }} ${{ steps.meta-fleet-agent.outputs.tags }}
+          SHARDS="shard1,shard2,shard3" ./.github/scripts/deploy-fleet.sh \
+                                       ${{ steps.meta-fleet.outputs.tags }} \
+                                       ${{ steps.meta-fleet-agent.outputs.tags }}
       -
         name: Fleet E2E Tests
         env:

diff --git a/.github/workflows/gke.yml b/.github/workflows/gke.yml
@@ -130,7 +130,9 @@ jobs:
         name: Deploy Fleet
         run: |
           echo "${{ steps.meta-fleet.outputs.tags }} ${{ steps.meta-fleet-agent.outputs.tags }}"
-          ./.github/scripts/deploy-fleet.sh ${{ steps.meta-fleet.outputs.tags }} ${{ steps.meta-fleet-agent.outputs.tags }}
+          SHARDS="shard1,shard2,shard3" ./.github/scripts/deploy-fleet.sh \
+                                       ${{ steps.meta-fleet.outputs.tags }} \
+                                       ${{ steps.meta-fleet-agent.outputs.tags }}
       -
         name: Fleet E2E Tests
         env: