Deploy the operator

Note

These instructions do not apply if the operator is installed from the OpenShift software catalog or when using Operator Lifecycle Manager (OLM). However, creating resources outside of the installation namespace, as mentioned in step 3, is always advised.

This page shows the installation steps to deploy ECK in Openshift:

Apply the manifests the same way as described in Install ECK using the YAML manifests document:

		oc create -f https://download.elastic.co/downloads/eck/3.3.0/crds.yaml
oc apply -f https://download.elastic.co/downloads/eck/3.3.0/operator.yaml

[Optional] If the Software Defined Network is configured with the ovs-multitenant plug-in, you must allow the elastic-system namespace to access other Pods and Services in the cluster:
```
oc adm pod-network make-projects-global elastic-system
		
```
Create a namespace to hold the Elastic resources (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash):

Note

A namespace other than the default namespaces (default, kube-*, openshift-*, etc) is required such that default Security Context Constraint (SCC) permissions are applied automatically. Elastic resources will not work properly in any of the default namespaces.
```
oc new-project elastic
		
```
1. creates the elastic project
[Optional] Allow another user or a group of users to manage the Elastic resources:
```
oc adm policy add-role-to-user elastic-operator developer -n elastic
		
```
In this example the user developer is allowed to manage Elastic resources in the namespace elastic.