eks

Elastic Kubernetes Service

Never spend your money before you have it, Jefferson T.

EKS não tem cota grátis, sempre é muito bem cobrado.

Rise up an EKS

1. Creating a role

IAM - Identity and Access Management: gerencia usuários e acessos.

Role é um grupo de policiies que estão vinculadas a serviços AWS, assim, o EKS precisa de permissionamento para acessar os recursos da AWS.

2. Creating a VPC

Virtual Private Cloud

Organização do Kubernetes

Kubernetes Components ²

É necessário criar uma estrutura de rede para suportar o Kubernetes, para isso, é aconselhável utilizar um template do Cloud Formation. Abaixe o arquivo amazon-eks-vpc-private-subnets.yaml e dê um upload na criação da VPC.

https://s3.us-west-2.amazonaws.com/amazon-eks/cloudformation/2020-10-29/amazon-eks-vpc-private-subnets.yaml

flowchart TB
  subgraph Region
    direction LR
    subgraph Zone A
      direction LR
      subgraph subpri1["Subnet Private"]
        direction TB
        poda1["pod 1"]
        poda2["pod 2"]
        poda3["pod 3"]
      end
      subgraph subpub1["Subnet Public"]
        loadbalancea["Load Balance"]
      end
    end
    subgraph Zone B
      direction LR
      subgraph subpri2["Subnet Private"]
        direction TB
        podb1["pod 1"]
        podb2["pod 2"]
        podb3["pod 3"]
      end
      subgraph subpub2["Subnet Public"]
        loadbalanceb["Load Balance"]
      end
    end
    User --> loadbalancea
    loadbalancea --> poda1
    loadbalancea --> poda2
    loadbalancea --> poda3
    User --> loadbalanceb
    loadbalanceb --> podb1
    loadbalanceb --> podb2
    loadbalanceb --> podb3
  end

gateway --> auth gateway --> discovery

3. Building an EKS

4. Accessing the EKS

On terminal, after that it had been set up the aws cli.

aws configure

See the configuration that was done.

aws configure list

aws configure list Name Value Type Location
---- ----- ---- --------
profile <not set> None None
access_key ****************TTNI shared-credentials-file
secret_key ****************zAJ1 shared-credentials-file
region us-east-2 config-file ~/.aws/config

Set up the kube-config to point to the remote aws eks cluster.

aws eks update-kubeconfig --name eks-store

aws eks update-kubeconfig --name eks-storeAdded new context arn:aws:eks:us-east-2:058264361068:cluster/eks-store to /Users/sandmann/.kube/config
>
>kubectl get podsNo resources found in default namespace.
>
>kubectl get nodesNo resources found
>

Come back to AWS EKS > compute:

Notice that there no nodes on cluster also, because only the Control Pane had been created, there is no exist a node for the worker nodes.

Attach roles to node group, it is exclusive for the worker nodes.

IAM > Roles

Add Permissions

AmazonEKS_CNI_Policy (Configuration Network Interface)
AmazonEKSWorkerNodePolicy
AmazonEC2ContainerRegistryReadOnly

Review

Group Node Group

Only private subnets:

kubectl get nodes

kubectl get nodesNAME STATUS ROLES AGE VERSION
ip-192-168-179-174.us-east-2.compute.internal Ready <none> 54s v1.29.3-eks-ae9a62a
ip-192-168-204-234.us-east-2.compute.internal Ready <none> 54s v1.29.3-eks-ae9a62a

Now, deploy the microservice.

kubectl apply -f ./k8s/deployment.yamldeployment.apps/gateway createdkubectl apply -f ./k8s/service.yamlservice/gateway created
>
>
>kubectl get allNAME READY STATUS RESTARTS AGE
pod/gateway-7894679df8-lbngj 1/1 Running 0 81s

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/gateway LoadBalancer 10.100.245.4 a3a5cc62ba81e466e9746f64f83fc349-1127848642.us-east-2.elb.amazonaws.com 8080:32681/TCP 25m
service/kubernetes ClusterIP 10.100.0.1 <none> 443/TCP 87m

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/gateway 1/1 1 1 82s

NAME DESIRED CURRENT READY AGE
replicaset.apps/gateway-7894679df8 1 1 1 82s
>

Jenkins update

Jenkins precisa instalar o awscli (adicionar ao docker-compose.yaml)

RUN apt-get install -y awscli

Dentro da instância, configurar:

> aws configure
> aws eks update-kubeconfig --name eks-store

Scale

> kubectl scale --replicas=3 deployment/gateway

kubectl scale --replicas=3 deployment/gatewaydeployment.apps/gateway scaledkubectl get podsNAME READY STATUS RESTARTS AGE
gateway-7894679df8-62m7z 1/1 Running 0 12s
gateway-7894679df8-r2kp2 1/1 Running 0 12s
gateway-7894679df8-v6xhs 1/1 Running 0 5m58s

eks