chore: run resourcePlacement e2e in a separate pipeline

Signed-off-by: Wantong Jiang <[email protected]>

Author: jwtty

.github/workflows/ci.yml

@@ -89,12 +89,16 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        customized-settings: [default, joinleave, custom]
+        customized-settings: [default, resourceplacement, joinleave, custom]
         include:
           - customized-settings: default
             # to shorten the test duration, set the resource snapshot creation interval to 0
             resource-snapshot-creation-minimum-interval: 0m
             resource-changes-collection-duration: 0m
+          - customized-settings: resourceplacement
+            # to shorten the test duration, set the resource snapshot creation interval to 0
+            resource-snapshot-creation-minimum-interval: 0m
+            resource-changes-collection-duration: 0m
           - customized-settings: joinleave
             # to shorten the test duration, set the resource snapshot creation interval to 0
             resource-snapshot-creation-minimum-interval: 0m
@@ -136,7 +140,9 @@ jobs:
       - name: Run e2e tests
         run: |
           if [ "${{ matrix.customized-settings }}" = "default" ]; then
-            make e2e-tests LABEL_FILTER="!custom && !joinleave"
+            make e2e-tests LABEL_FILTER="!custom && !joinleave && !rp"
+          elif [ "${{ matrix.customized-settings }}" = "resourceplacement" ]; then
+            make e2e-tests LABEL_FILTER="!custom && rp"
           elif [ "${{ matrix.customized-settings }}" = "joinleave" ]; then
             make e2e-tests LABEL_FILTER="!custom && joinleave"
           else

test/e2e/README.md

@@ -35,16 +35,21 @@ test suites, follow the steps below:
    ginkgo --label-filter="!custom" -v -p .
    ```
 
-   or run the custom configuration e2e tests with the following command
+   or run the custom configuration e2e tests with the following command:
    ```sh
    ginkgo --label-filter="custom" -v -p .
    ```
 
-   or run tests involving member cluster join/leave scenarios with the following command (serially)
+   or run tests involving member cluster join/leave scenarios with the following command (serially):
    ```sh
    ginkgo --label-filter="joinleave" -v .
    ```
 
+   or run tests related to resourcePlacement (rp) only with the following command:
+   ```sh
+   ginkgo --label-filter="rp" -v -p .
+   ```
+
    or create a launch.json in your vscode workspace.
    ```yaml
    {

test/e2e/resource_placement_pickall_test.go

@@ -31,7 +31,7 @@ import (
 	"github.com/kubefleet-dev/kubefleet/test/e2e/framework"
 )
 
-var _ = Describe("placing namespaced scoped resources using a RP with PickAll policy", func() {
+var _ = Describe("placing namespaced scoped resources using a RP with PickAll policy", Label("rp"), func() {
 	crpName := fmt.Sprintf(crpNameTemplate, GinkgoParallelProcess())
 	rpName := fmt.Sprintf(rpNameTemplate, GinkgoParallelProcess())
 

test/e2e/resource_placement_pickn_test.go

@@ -31,7 +31,7 @@ import (
 	"github.com/kubefleet-dev/kubefleet/test/e2e/framework"
 )
 
-var _ = Describe("placing namespaced scoped resources using a RP with PickN policy", func() {
+var _ = Describe("placing namespaced scoped resources using a RP with PickN policy", Label("rp"), func() {
 	crpName := fmt.Sprintf(crpNameTemplate, GinkgoParallelProcess())
 	rpName := fmt.Sprintf(rpNameTemplate, GinkgoParallelProcess())
 	rpKey := types.NamespacedName{Name: rpName, Namespace: appNamespace().Name}