Skip to content

Deploy Okera on EKS

This document prepares you to install Okera on an EKS cluster.

Prerequisites

  1. A functional EKS cluster that adheres to the Okera prerequisites.
  2. A Linux node that can execute kubectl commands against the EKS cluster - we will call this the deployer node.

Verify EKS Access

On the deployer node, you can verify you have EKS access by running:

$ kubectl get nodes -owide
NAME                                       STATUS   ROLES    AGE   VERSION               INTERNAL-IP   EXTERNAL-IP   OS-IMAGE         KERNEL-VERSION                  CONTAINER-RUNTIME
ip-10-1-10-96.us-west-2.compute.internal   Ready    <none>   38m   v1.12.10-eks-ffbd96   10.1.10.96    <none>        Amazon Linux 2   4.14.133-113.112.amzn2.x86_64   docker://18.6.1
ip-10-1-2-109.us-west-2.compute.internal   Ready    <none>   44m   v1.12.10-eks-ffbd96   10.1.2.109    <none>        Amazon Linux 2   4.14.133-113.112.amzn2.x86_64   docker://18.6.1

You should see all the nodes that you have in your EKS cluster listed.

Deploy and Configure Okera Using Helm Charts

See Deploy Okera Using Helm Charts for information about deploying and updating Okera using Helm charts.