{"id":1057,"date":"2022-07-06T10:23:58","date_gmt":"2022-07-06T10:23:58","guid":{"rendered":"https:\/\/blog.ngocha.biz\/?p=1057"},"modified":"2022-07-06T10:23:58","modified_gmt":"2022-07-06T10:23:58","slug":"eks-anywhere-cluster","status":"publish","type":"post","link":"https:\/\/blog.ngocha.biz\/?p=1057","title":{"rendered":"EKS Anywhere Cluster Tutorial [Deploy Cluster in 7 Steps]"},"content":{"rendered":"

In this blog, you will learn what EKS Anywhere is and how to set up an EKS Anywhere development cluster<\/strong> and register it to the AWS EKS console using the EKS connector.<\/p>\n

What is EKS Anywhere?<\/h2>\n

EKS Anywhere is an AWS feature<\/strong> to run and manage EKS clusters in on-premises environments. It simplifies the on-premise Kubernetes management and enables a consistent Kubernetes experience in a multi-cloud Kubernetes deployment. Also, you will have full control over the control plane and the worker nodes.<\/p>\n

\"EKS<\/figure>\n

EKS anywhere uses Amazon EKS Distro (EKS-D)<\/a><\/strong>, a Kubernetes distribution customized and open-sourced by AWS. It is the same distro that powers the AWS-managed EKS. This means that when you install EKS anywhere, it comes with parameters and configurations optimized for AWS.<\/p>\n

Also, you can register the EKS anywhere clusters to the AWS EKS console using the EKS connector. <\/strong>Once the cluster is registered, you can visualize all the anywhere cluster components in the AWS EKS console.<\/p>\n

EKS connector<\/a> is a Statefulset that runs the AWS System Manager Agent<\/a> in your cluster. It is responsible for maintaining the connection between EKS anywhere cluster and AWS.<\/p>\n

<\/figure>\n

Following the key use cases of EKS anywhere:<\/p>\n

    \n
  1. Hybrid cloud consistency:<\/strong> EKS anywhere enables operational consistency across your on-premise and cloud Kubernetes clusters.<\/li>\n
  2. Disconnected environment<\/strong>: You can run EKS anywhere cluster without an internet connection. At the same time, your disconnected clusters will have the same features as the cloud EKS with the EKS-D distro.<\/li>\n
  3. Application modernization: <\/strong>With EKS-D, the administrative overhead of patching and version upgrades is reduced. So you can focus more on the applications.<\/li>\n<\/ol>\n

    EKS Anywhere Development Cluster Setup<\/h2>\n

    You can set up EKS anywhere development clusters using Docker on MAC or Ubuntu systems.<\/p>\n

    Follow the steps given below to set up EKS anywhere development cluster.<\/p>\n

    Step 1: Install Docker Desktop<\/h3>\n

    Go to Docker downloads<\/a> and install the Docker desktop on MAC. For Ubuntu use this link to download the deb package<\/a><\/p>\n

    Mac users, open the following file and change deprecatedCgroupv1<\/code> to true. And then restart the Docker desktop to apply the changes.<\/p>\n

    vi ~\/Library\/Group\\ Containers\/group.com.docker\/settings.json<\/code><\/pre>\n
    Or else you will get the following error.<\/p>\n
    Error: failed to validate docker desktop: EKS Anywhere requires Docker desktop to be configured to use CGroups v1. Please  set `deprecatedCgroupv1:true` in your `~\/Library\/Group\\ Containers\/group.com.docker\/settings.json` file<\/code><\/pre>\n
    Step 2: Install eksctl-anywhere<\/h3>\n
    brew install eks-anywhere<\/code><\/pre>\n
    Step 3: Generate the cluster configuration<\/h3>\n
    Generate the EKS anywhere cluster configuration using the following command.<\/p>\n
    CLUSTER_NAME=dev-eks-cluster\neksctl anywhere generate clusterconfig $CLUSTER_NAME \\\n   --provider docker > $CLUSTER_NAME.yaml<\/code><\/pre>\n
    Your cluster configuration would look like the following.<\/p>\n
    apiVersion: anywhere.eks.amazonaws.com\/v1alpha1\nkind: Cluster\nmetadata:\n  name: dev-eks-cluster\nspec:\n  clusterNetwork:\n    cniConfig:\n      cilium: {}\n    pods:\n      cidrBlocks:\n      - 192.168.0.0\/16\n    services:\n      cidrBlocks:\n      - 10.96.0.0\/12\n  controlPlaneConfiguration:\n    count: 1\n  datacenterRef:\n    kind: DockerDatacenterConfig\n    name: dev-eks-cluster\n  externalEtcdConfiguration:\n    count: 1\n  kubernetesVersion: \"1.22\"\n  managementCluster:\n    name: dev-eks-cluster\n  workerNodeGroupConfigurations:\n  - count: 1\n    name: md-0\n\n---\napiVersion: anywhere.eks.amazonaws.com\/v1alpha1\nkind: DockerDatacenterConfig\nmetadata:\n  name: dev-eks-cluster\nspec: {}\n\n---<\/code><\/pre>\n
    Step 4: Deploy the cluster<\/h3>\n
    Deploy the cluster using eksctl<\/code>. It will take a while for the cluster to be provisioned.<\/p>\n
    eksctl anywhere create cluster -f dev-eks-cluster.yaml<\/code><\/pre>\n
    You will get the following output after a successful cluster deployment.<\/p>\n
    \"EKS<\/figure>\n
    Step 5: Validate the cluster<\/h3>\n
    Once the cluster is created you can see a folder named dev-eks-cluster<\/code> with the kubeconfig file. Let’s export the kubeconfig file.<\/p>\n
    Replace \/path\/to<\/code> with the absolute path of the dev-eks-cluster folder location. Or check out the Kubeconfig file guide<\/a> to know more about kubeconfig file practical usage.<\/p>\n
    KUBECONFIG=\/path\/to\/dev-eks-cluster\/dev-eks-cluster-eks-a-cluster.kubeconfig<\/code><\/pre>\n
    Now, let’s list the pods in the kube-system<\/code> namespace to validate the cluster. You should see all the pods in running state as shown below.<\/p>\n
    \"EKS<\/figure>\n
    Step 6: Generate & Deploy EKS Connector Configs<\/h3>\n
    Now that we have a running EKS anywhere development cluster, we will go ahead and register the cluster using the EKS connector.<\/p>\n
    Note<\/strong>: Before you register the cluster, ensure you have a valid AWS cli configuration with admin privileges in your system. Refer the AWS CLI configuration guide<\/a> for more details.<\/p><\/blockquote>\n
    Here is the command to generate EKS connector config YAMLs. Replace the region value if you are using a different region.<\/p>\n
    eksctl register cluster --name dev-eks-cluster --provider EKS_ANYWHERE --region us-west-2 <\/code><\/pre>\n
    The above command creates the following three YAML files. Where eks-connector.yaml<\/code> is the EKS connector agent Statefulset YAML<\/p>\n
      \n
    1. eks-connector-clusterrole.yaml<\/li>\n
    2. eks-connector-console-dashboard-full-access-group.yaml<\/li>\n
    3. eks-connector.yaml<\/li>\n<\/ol>\n
      Let’s deploy all the three YAMLs.<\/p>\n
      kubectl apply -f eks-connector-clusterrole.yaml\nkubectl apply -f eks-connector-console-dashboard-full-access-group.yaml\nkubectl apply -f eks-connector.yaml<\/code><\/pre>\n
      Step 7: Validate EKS Anywhere Cluster Registration On the EKS console<\/h3>\n
      If you head over to the AWS EKS console, you should see the newly registered cluster as shown below.<\/p>\n
      \"EKS<\/figure>\n
      If you click the cluster name, you can view all the information and objects of the EKS anywhere cluster running in your local workstation.<\/p>\n
      \"Listing<\/figure>\n
      Here is the EKS connector demo I have added to DevOpsCube YouTube Channel.<\/a><\/p>\n