drop OLM deployment docs
OLM deployment is broken, not tested and described steps are unnecessarily
complicated. Let's drop it for now. Once we have proper OLM integration,
we can add it back with complexity similar to operatorhub.io, e.g. install
a single manifest (2 if you are missing OLM).
@@ -195,96 +195,6 @@ kubectl get networkaddonsconfig cluster -o yaml
For more information about the configuration format check [configuring section](#configuration).
-## Deploy Using OLM
-
-For more information on the [Operator Lifecycle
-Manager](https://github.com/operator-framework/operator-lifecycle-manager) and
-Cluster Service Versions checkout out ["Building a Cluster Service
-Version"](https://github.com/operator-framework/operator-lifecycle-manager/blob/master/Documentation/design/building-your-csv.md).
-
-**NOTE**
-
-Replace `<docker_org>` with your Docker organization.
-
-1) Build and push an operator-registry image.
-
-```shell
-IMAGE_REGISTRY=docker.io/$DOCKER_ORG make docker-build-registry
-IMAGE_REGISTRY=docker.io/$DOCKER_ORG make docker-push-registry
-```
-
-2) Create the cluster-network-addons-operator Namespace and OperatorGroup.
-[This](https://github.com/operator-framework/operator-lifecycle-manager/blob/master/Documentation/design/building-your-csv.md#operator-metadata)
-portion of OLM's CSV writing documentation goes into more detail about
-OperatorGroups.
-
-```shell
-kubectl create ns cluster-network-addons-operator
-
-cat <<EOF | kubectl create -f -
-apiVersion: operators.coreos.com/v1alpha2
-kind: OperatorGroup
-metadata:
- name: cluster-network-addons-operator
- namespace: cluster-network-addons-operator
-EOF
-```
-
-3) Using the `cna-registry` container image built in step 1,
-create a CatalogSource. This object tells OLM about the operator.
-
-```bash
-cat <<EOF | kubectl create -f -
-apiVersion: operators.coreos.com/v1alpha1
-kind: CatalogSource
-metadata:
- name: cluster-network-addons
- namespace: openshift-operator-lifecycle-manager
-spec:
- sourceType: grpc
- image: docker.io/$DOCKER_ORG/cna-registry:example
- displayName: Cluster Network Addons
- publisher: Red Hat
-EOF
-```
-
-4) Subscribe to the cluster-network-addons-operator.
-
-```shell
-cat <<EOF | kubectl create -f -
-apiVersion: operators.coreos.com/v1alpha1
-kind: Subscription
-metadata:
- name: cluster-network-addons-operator-subscription
- namespace: cluster-network-addons-operator
-spec:
- channel: alpha
- name: cluster-network-addons
- source: cluster-network-addons
- sourceNamespace: openshift-operator-lifecycle-manager
- startingCSV: cluster-network-addons-operator.0.9.0
-EOF
-```
-
-5) With the cluster-network-addons-operator ready and available, create a NetworkAddonsConfig.
-
-```shell
-cat <<EOF | kubectl create -f -
-apiVersion: networkaddonsoperator.network.kubevirt.io/v1alpha1
-kind: NetworkAddonsConfig
-metadata:
- name: cluster
-spec:
- imagePullPolicy: Always
- kubeMacPool:
- rangeEnd: FD:FF:FF:FF:FF:FF
- rangeStart: "02:00:00:00:00:00"
- linuxBridge: {}
- multus: {}
- sriov: {}
- nmstate: {}
-```
-
# Development
```shell
