Remove docs references and opi filter in spec_helper

README.md

@@ -11,8 +11,6 @@
 * [Continuous Integration Pipelines](https://ci.cake.capi.land/)
 * [Notes on V3 Architecture](https://github.com/cloudfoundry/cloud_controller_ng/wiki/Notes-on-V3-Architecture)
 * [capi-release](https://github.com/cloudfoundry/capi-release) - The bosh release used to deploy cloud controller
-* [cf-for-k8s](https://github.com/cloudfoundry/cf-for-k8s) - How Cloud Foundry (including Cloud Controller) is deployed against Kubernetes
-* [capi-k8s-release](https://github.com/cloudfoundry/capi-k8s-release) - The parts of cf-for-k8s that are specific to CF API (including Cloud Controller)
 
 ## Components
 
@@ -51,12 +49,6 @@ Cloud Controller currently supports [webdav](http://www.webdav.org/) and the fol
 The Cloud Controller on VMs uses [Diego](https://github.com/cloudfoundry/diego-release) to stage and run apps and tasks.
 See [Diego Design Notes](https://github.com/cloudfoundry/diego-design-notes) for more details.
 
-When deployed on Kubernetes, Cloud Controller uses
-[kpack](https://github.com/pivotal/kpack) to build images from source with
-[Cloud Native Buildpacks](https://buildpacks.io) and
-[Eirini](https://github.com/cloudfoundry-incubator/eirini) to run apps directly on the Kubernetes cluster.
-
-
 ## Contributing
 
 Please read the [contributors' guide](https://github.com/cloudfoundry/cloud_controller_ng/blob/main/CONTRIBUTING.md) and the [Cloud Foundry Code of Conduct](https://cloudfoundry.org/code-of-conduct/)

docs/v3/source/includes/concepts/_lifecycles.md.erb

@@ -34,8 +34,6 @@ If buildpacks are not specified, then Cloud Foundry will automatically detect a
 compatible buildpack, based on the files in an app's package. If a stack is not
 specified, then the app will default to the operator-configured default stack.
 
-**Note**: This lifecycle is not supported on Cloud Foundry for Kubernetes.
-
 #### Buildpack lifecycle object
 
 Name | Type | Description
@@ -67,33 +65,3 @@ Name | Type | Description
 ---- | ---- | -----------
 **type** | _string_ | `docker`
 **data** | _object_ | Data is not used by the Docker lifecycle; valid value is `{}`
-
-### Kpack lifecycle
-
-```
-Example Kpack Lifecycle
-```
-
-```json
-{
-  "type": "kpack",
-  "data": {
-    "buildpacks": ["paketo-buildpacks/java"]
-  }
-}
-```
-
-This is the default lifecycle for Cloud Foundry for Kubernetes. When staging an app with this lifecycle, the app source code will be
-built into an OCI image using a [Cloud Native Buildpack](https://buildpacks.io/) and [kpack](https://github.com/pivotal/kpack).
-This image is published to the app image registry and a `docker` lifecycle droplet is created referring to the image.
-
-When running an app with this lifecycle, a container is created and the OCI image is executed inside of it.
-
-**Note**: This lifecycle is not supported on Cloud Foundry for VMs.
-
-#### Kpack lifecycle object
-
-Name | Type | Description
----- | ---- | -----------
-**type** | _string_ | `kpack`
-**data.buildpacks** | _list of strings_ | An optional list of buildpack names. Specify an empty list to auto-detect a suitable buildpack during staging

spec/spec_helper.rb

@@ -92,7 +92,7 @@
     rspec_config.mock_with :rspec do |mocks|
       mocks.verify_partial_doubles = true
     end
-    rspec_config.filter_run_excluding :opi, :stepper
+    rspec_config.filter_run_excluding :stepper
     rspec_config.expose_dsl_globally = false
     rspec_config.backtrace_exclusion_patterns = [%r{/gems/}, %r{/bin/rspec}]