Skip to content

ECK Operator

Step 1: Download YAML

Download v1.2.1 (or higher) of the ECK all-in-one.yaml file from Elastic's Official Repository

This YAML file includes ECK's Custom Resource Definitions and the elastic-operator with its RBAC rules. 

wget https://download.elastic.co/downloads/eck/1.2.1/all-in-one.yaml

Step 2: Deploy Workload

  • Login into the Web Console and navigate to your Project as an Org Admin or Project Admin
  • Under Infrastructure (or Applications if accessed with Project Admin role), select "Namespaces" and create a new namespace called "elastic-system"
  • Go to Applications > Workloads
  • Select "New Workload" to create a new workload called "elastic-operator"
  • Ensure that you select "NativeYaml" for Package Type and select the namespace as "elastic-system"
  • Click CONTINUE to next step

Create elastic-operator workload

  • Upload the downloaded "all-in-one.yaml" file above to NativeYaml > Choose File

Create elastic-operator workload

  • Save and Go to Placement
  • Select the cluster that you would like to deploy the ECK Operator
  • Publish the elastic-operator workload to the selected cluster

Step 3: Verify Deployment

In this step, you will verify whether the required resources have been successfully created on the cluster.

  • After publishing the elastic-operator workload, click on the Debug button
  • Click on the Kubectl button to open a virtual terminal for kubectl proxy access right to the "elastic-operator" namespace context of the cluster

elastic-operator workload debug

ECK CRDs

First, we will verify whether ECK's Custom Resource Definitions (CRDs) are created

kubectl get crd

NAME                                                 CREATED AT
apmservers.apm.k8s.elastic.co                        2020-08-13T21:15:28Z
beats.beat.k8s.elastic.co                            2020-08-13T21:15:34Z
elasticsearches.elasticsearch.k8s.elastic.co         2020-08-13T21:15:40Z
enterprisesearches.enterprisesearch.k8s.elastic.co   2020-08-13T21:15:45Z
kibanas.kibana.k8s.elastic.co                        2020-08-13T21:15:50Z

Elastic Operator Pods

Next, we will verify the status of pods for the "elastic-operator"

kubectl get pod

NAME                 READY   STATUS    RESTARTS   AGE
elastic-operator-0   1/1     Running   1          23m
Once the elastic-operator pod is in running state, we are ready to move to the next step and deploy Elasticsearch and Kibana to the same cluster.