Metaplay Docs

Appearance

Interacting with EKS

This guide provides some useful commands for interacting with an EKS cluster.

Target Audience

This page is primarily intended for users on Private Cloud plans. If you are using Metaplay Cloud with a Pre-launch/Production plan, information from this page may not be directly relevant to your needs.

Dependencies ​

How-To ​

By default, EKS has a kubeconfig file that we can use to interact with the cluster. But first, you need to find out which cluster you want to access.

You can list all EKS clusters in the specified region by running:

bash
$ aws eks list-clusters --region <aws region>

Then, you can get the kubeconfig of a specific cluster:

bash
$ aws eks update-kubeconfig --kubeconfig /path/to/file/with/kubeconfig.yaml --name <eks cluster name> --region <aws region>
$ export KUBECONFIG=/path/to/file/with/kubeconfig.yaml

With the kubeconfig.yaml file, we can inspect the cluster with kubectl and Helm:

Using Kubectl ​

bash
$ kubectl get nodes -A
Output
bash
NAME                                        STATUS   ROLES    AGE   VERSION
ip-10-0-25-213.eu-west-1.compute.internal   Ready    <none>   14m   v1.27.9-eks-5e0fdde
bash
$ kubectl get ns
Output
bash
NAME                STATUS   AGE
cluster-system      Active   18m
default             Active   22m
kube-node-lease     Active   22m
kube-public         Active   22m
kube-system         Active   22m
metaplay-env-init   Active   27s
metaplay-system     Active   27s

Using Helm ​

bash
$ helm ls -n metaplay-system
Output
bash
NAME              NAMESPACE       REVISION  UPDATED                                 STATUS    CHART                     APP VERSION
metaplay-services metaplay-system 1         2024-02-26 02:23:50.498412684 +0200 EET deployed  metaplay-services-0.1.21