docs: remove OLM installation and release docs (#4617)

Signed-off-by: Gergely Brautigam <182850+Skarlso@users.noreply.github.com>

docs/contributing/release.md

@@ -14,7 +14,6 @@ Otherwise the `latest` documentation will point to the older version. Also avoid
     1. ⚠️ make sure that CI on the relevant branch has completed the docker build/push jobs. Otherwise an old image will be promoted.
 1. GitHub Release, Changelog will be created by the `release.yml` workflow which also promotes the container image.
 1. update Helm Chart, see below
-1. update OLM bundle, see [helm-operator docs](https://github.com/external-secrets/external-secrets-helm-operator/blob/main/docs/release.md#operatorhubio)
 
 ## Release Helm Chart
 
@@ -26,39 +25,3 @@ Otherwise the `latest` documentation will point to the older version. Also avoid
 1. create/merge into release branch
     1. on a `minor` release: create a new branch `release-x.y`
     1. on a `patch` release: merge main into `release-x.y`
-
-## Release OLM Bundle
-
-In order to make the latest release available to [OperatorHub.io](https://operatorhub.io/) we need to create a bundle and open a PR in the [community-operators](https://github.com/k8s-operatorhub/community-operators/) repository.
-
-To create a bundle first increment the `VERSION` in the Makefile as described above. Then run the following commands in the root of the repository:
-
-```bash
-# clone repo
-git clone https://github.com/external-secrets/external-secrets-helm-operator
-cd external-secrets-helm-operator
-
-# bump version
-export VERSION=x.y.z
-sed -i "s/^VERSION ?= .*/VERSION ?= ${VERSION}/" Makefile
-
-# prep release
-make prepare-stable-release ATTACH_IMAGE_DIGESTS=0
-```
-
-Check the generated files in the `bundle/` directory. If they look good add & commit them, open a PR against this repository. You can always use the [OperatorHub.io/preview](https://operatorhub.io/preview) page to preview the generated CSV.
-
-```bash
-git status
-git add .
-git commit -s -m "chore: bump version xyz"
-git push
-```
-
-Once the PR is merged and the image build job on `main` has completed, we need create a pull request against both community-operators repositories. There's a make target that does the heavy lifting for you:
-```bash
-make attach-image-digests
-make bundle-operatorhub
-```
-
-This command will add/commit/push and open pull requests in the respective repositories.

docs/introduction/getting-started.md

@@ -102,10 +102,6 @@ Events:                    <none>
 For more advanced examples, please read the other
 [guides](../guides/introduction.md).
 
-## Installing with OLM
-
-External-secrets can be managed by [Operator Lifecycle Manager](https://olm.operatorframework.io/) (OLM) via an installer operator. It is made available through [OperatorHub.io](https://operatorhub.io/), this installation method is suited best for OpenShift. See installation instructions on the [external-secrets-operator](https://operatorhub.io/operator/external-secrets-operator) package.
-
 ## Uninstalling
 
 Before continuing, ensure that all external-secret resources that have been created by users have been deleted.