Skip to main content

EKS Provisioning Using TF

Full script is available at

https://github.com/JaydeepUniverse/terraform/tree/master/aws/eks

Prerequisites

  • Install kubectl
  • Install AWS CLI
  • Install AWS IAM Authenticator
  • Update kubeconfig file if needed
    • aws eks update-kubeconfig --name eksClusterName

Please keep in mind about below commented notes while changing names of name,cluster,environment else EKS,ASG,VPC all resources will be created but while running kubectl get nodes command it won't show any worker nodes

                
provider "aws" {
    region = "us-east-2" # region
  }
  
module "vpc" {
    source        = "../../modules/vpc"
    vpc-location  = "Ohio" # location name as per region
    namespace     = "nextgen-cicd" # namespace
    name          = "vpc" # KEEP IT AS IS
    stage         = "dev" # stage name
    cluster-name  = "nextgen-cicd-dev-eks-cluster" # clustername = namespace-stagename-eks-cluster
}
  
module "eks_workers" {
    namespace    = "nextgen-cicd" # namespace
    stage        = "dev" # stage name
    name         = "eks" # KEEP IT AS IS
    cluster_name = "nextgen-cicd-dev-eks-cluster" # clustername = namespace-stagename-eks-cluster
    key_name     = "nextgen-cicd-key" # MAKE SURE THIS KEY MUST BE CREATED BEFORE RUNNING THIS SCRIPT
}
  
module "eks_cluster" {
    namespace  = "nextgen-cicd" # namespace
    stage      = "dev" # stage name
    name       = "eks" # KEEP IT AS IS
    region     = "us-east-2" # region
}
                
            

Comments

Popular posts from this blog

Install AWS CLI on Ubuntu localhost using Ansible Playbook

Install AWS CLI on Ubuntu localhost using Ansible Playbook --- - hosts: localhost tasks: - name: Installing Unzip package package: name: unzip state: present when: ansible_facts['os_family'] == "Debian" become: true - name: Create awscli directory in home directory file: path: ~/awscli state: directory mode: '0755' - name: Download bundled installer zip file get_url: url: https://s3.amazonaws.com/aws-cli/awscli-bundle.zip dest: ~/awscli/awscli-bundle.zip - name: Extract zip file unarchive: src: ~/awscli/awscli-bundle.zip dest: ~/awscli - name: Run install command shell: /home/ubuntu/awscli/awscli-bundle/install -i /usr/local/aws -b /usr/local/bin/aws become: true Same script is also avail...

How to clone Github repository using SSH

Run ssh-keygen Upload ssh public key to github account curl -u "gitUsername:password" --data '{"title":"keyName","key":"'"$(cat ~/.ssh/id_rsa.pub)"'"}' https://api.github.com/user/keys Sample output of ssh public key upload command { "id": 1234567890, "key": "ssh-rsa aaaaaaaaaaaaaaaaaaaa/dddd/+aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", "url": "https://api.github.com/user/keys/123456...

Docker Networks

Docker Networks One of the reasons Docker containers and services are so powerful is that you can connect them together, or connect them to non-Docker workloads. Docker’s networking subsystem is pluggable, using drivers. Several drivers exist by default, and provide core networking functionality: Bridge: The default network driver. If you don’t specify a driver, this is the type of network you are creating. Bridge networks are usually used when your applications run in standalone containers that need to communicate. Host: For standalone containers, remove network isolation between the container and the Docker host, and use the host’s networking directly. host is only available for swarm services on Docker 17.06 and higher. See use the host network. Overlay: Overlay networks connect multiple Docker...