Remove v1beta1 CRD (#1300) (#1358)

This is removed in Kubernetes 1.22 https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/#api-changes Signed-off-by: Baiju Muthukadan <[email protected]> Signed-off-by: Baiju Muthukadan <[email protected]> Signed-off-by: Baiju Muthukadan <[email protected]> Co-authored-by: Baiju Muthukadan <[email protected]>
redhat-developer · Jan 11, 2023 · 7614578 · 7614578
1 parent 7b05b8c
commit 7614578
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 25 deletions.
diff --git a/test/acceptance/features/discoverBindableResources.feature b/test/acceptance/features/discoverBindableResources.feature
@@ -15,11 +15,3 @@ Feature: Discover bindable resources in a cluster
         And User acceptance-tests-dev can read resource bindablekinds/bindable-kinds
         And Kind ProvisionedBackend with apiVersion stable.example.com/v1 is listed in bindable kinds
         And Kind BindableBackend with apiVersion stable.example.com/v1 is listed in bindable kinds
-
-    @crdv1beta1
-    @external-feedback
-    Scenario: Discover bindable service when defined by v1beta1 CRD API
-        Given OLM Operator "provisioned_backend_crdv1beta1" is running
-        Then bindablekinds/bindable-kinds is available in the cluster
-        And User acceptance-tests-dev can read resource bindablekinds/bindable-kinds
-        And Kind BetaProvisionedBackend with apiVersion stable.example.com/v1 is listed in bindable kinds
diff --git a/test/acceptance/resources/provisioned_backend_crdv1beta1.operator.manifest.yaml b/test/acceptance/resources/provisioned_backend_crdv1beta1.operator.manifest.yaml