Add unintall feature test

Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>

Author: Per Goncalves da Silva

test/e2e/features/install.feature

@@ -30,9 +30,7 @@ Feature: Install ClusterExtension
     Then ClusterExtension is rolled out
     And ClusterExtension is available
     And bundle "test-operator.1.2.0" is installed in version "1.2.0"
-    And resource "networkpolicy/test-operator-network-policy" is installed
-    And resource "configmap/test-configmap" is installed
-    And resource "deployment/test-operator" is installed
+    And ClusterExtension resources are created and labeled
 
   @mirrored-registry
   Scenario Outline: Install latest available version from mirrored registry
@@ -57,9 +55,7 @@ Feature: Install ClusterExtension
     Then ClusterExtension is rolled out
     And ClusterExtension is available
     And bundle "<package-name>-operator.1.2.0" is installed in version "1.2.0"
-    And resource "networkpolicy/test-operator-network-policy" is installed
-    And resource "configmap/test-configmap" is installed
-    And resource "deployment/test-operator" is installed
+    And ClusterExtension resources are created and labeled
 
     Examples:
       | package-name  |

test/e2e/features/uninstall.feature

@@ -0,0 +1,41 @@
+Feature: Uninstall ClusterExtension
+
+  As an OLM user I would like to uninstall a cluster extension,
+  removing all resources previously installed/updated through the extension.
+
+  Background:
+    Given OLM is available
+    And ClusterCatalog "test" serves bundles
+    And ServiceAccount "olm-sa" with needed permissions is available in ${TEST_NAMESPACE}
+    And ClusterExtension is applied
+      """
+      apiVersion: olm.operatorframework.io/v1
+      kind: ClusterExtension
+      metadata:
+        name: ${NAME}
+      spec:
+        namespace: ${TEST_NAMESPACE}
+        serviceAccount:
+          name: olm-sa
+        source:
+          sourceType: Catalog
+          catalog:
+            packageName: test
+            selector:
+              matchLabels:
+                "olm.operatorframework.io/metadata.name": test-catalog
+      """
+    And bundle "test-operator.1.2.0" is installed in version "1.2.0"
+    And ClusterExtension is rolled out
+
+  Scenario: Removing ClusterExtension triggers the extension uninstall, eventually removing all installed resources
+    When ClusterExtension is removed
+    Then ClusterExtension is uninstalled
+
+  Scenario: Removing ClusterExtension resources leads to all installed resources being removed even if the service account is no longer present
+    When resource "serviceaccount/olm-sa" is removed
+    # Ensure service account is gone before checking to ensure resources are cleaned up whether the service account
+    # and its permissions are present on the cluster or not
+    And resource "serviceaccount/olm-sa" is eventually not found
+    And ClusterExtension is removed
+    Then ClusterExtension is uninstalled

test/e2e/steps/hooks.go

@@ -16,6 +16,7 @@ import (
 	"k8s.io/apimachinery/pkg/apis/meta/v1/unstructured"
 	"k8s.io/component-base/featuregate"
 	"k8s.io/klog/v2/textlogger"
+	"sigs.k8s.io/controller-runtime/pkg/client"
 
 	"github.com/operator-framework/operator-controller/internal/operator-controller/features"
 )
@@ -32,6 +33,9 @@ type scenarioContext struct {
 	removedResources     []unstructured.Unstructured
 	backGroundCmds       []*exec.Cmd
 	metricsResponse      map[string]string
+
+	// set by ClusterExtensionIsRolledOut
+	extensionObjects []client.Object
 }
 
 type contextKey string