Skip to content

Latest commit

 

History

History
71 lines (60 loc) · 3.68 KB

README.md

File metadata and controls

71 lines (60 loc) · 3.68 KB
Raw

AWS EKS Cluster for Rancher

Prerequisites

  • AWS account and credentials with permissions to create EKS cluster.
  • AWS credentials in ~/.aws/ folder as given here.
  • Wireguard setup.
  • Copy of ~/.kube/config file with another name. (IMPORTANT. As in this process your existing ~/.kube/config file will be overridden).
  • eksctl utility.
  • kubectl utility installed.
  • Key .pem file from AWS console in ~/.ssh/ folder. (Generate a new one if you do not have this key file).
  • aws-iam-authenticator installed.
  • Hardware requirements:
    • All the nodes must be in the same VPC.
Purpose vCPUs RAM Storage AWS Instance Type Number of Nodes
Cluster nodes 2 8 GB 32 GB t3.large 2
Wireguard bastion host 2 4 GB 8 GB t2.medium 1
  • Certificates:
    • Depending upon the above hostnames, atleast one wildcard SSL certificate will be required. For example; *.org.net.
    • More ssl certificates will be required, for every new level of hierarchy. For example; *.sandbox1.org.net.

Install cluster

  • Copy rancher.cluster.config.sample to rancher.cluster.config.
  • Review the parameters of rancher.cluster.config carefully.
  • Install
eksctl create cluster -f rancher.cluster.config
  • Note that it takes around 30 minutes to create (or delete a cluster).
  • After creating cluster make a backup copy of config with a suitable name in ~/.kube/ folder, eg. rancher_config because if you create cluster again using eksctl it will override existing ~/.kube/config. Set file permission to chmod 400 ~/.kube/rancher_config to avoid any accidental changes or deletion.

Ingress controller

Install Nginx ingress controller using Helm charts:

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
helm install \                               
  ingress-nginx ingress-nginx/ingress-nginx \
  --namespace ingress-nginx \
  --version 3.12.0 \
  --create-namespace  \
-f nginx.values.yaml

The above will automatically spawn an Internal AWS Network Load Balancer (L4).

Network Load Balancer (NLB)

Check the following on AWS console:

  1. An NLB has been created. You may also see the DNS of NLB with 
    kubectl -n ingress-nginx get svc
  2. Edit listner "443". Select "TLS".
  3. Note the target group name of listner 80. Set target group of 443 to target group of 80. Basically, we want TLS termination at the LB and it must forward HTTP traffic (not HTTPS) to port 80 of ingress controller. So
    • Input of LB: HTTPS
    • Output of LB: HTTP --> port 80 of ingress nginx controller
  4. Enable "Proxy Protocol v2" in the target group settings
  5. Make sure all subnets are selected in LB -->Description-->Edit subnets.
  6. Check health check of target groups.
  7. Remove listner 80 from LB as we will receive traffic only on 443.

Domain name

Create the following domain names:

  1. Rancher: rancher.xyz.net
  2. Keycloak: iam.xyz.net

Point the above to internal ip address of the NLB. This assumes that you have a Wireguard Bastion Host has been installed. On AWS this is done on Route 53 console.