voronenko / devops-tf-eks

terraform baked AWS kubernetes cluster (EKS) - 1.18 compatible

Profile Highlights

About me

I provide Ops, software development services. On a remote, solo or as a part of remote distributed teams. Open for opportunities as an independent consultant. I do also provide short term consulting.

In s/d since beginning of the century ( :) ), approximately 7 times x 3 years technology periods, during which I was working with needed at that moment set of technologies. Roles covered were (depending on project) - software developer, lead developer, project architect, project manager.

On a current round I am collaborating mostly with a startups as a hired gun.

	I am supporting set of ansible playbooks used by me in a routine work, check on a github
📝 blogging	I do some rare blogging at https://medium.com/@V_Voronenko

How to reach me?

Tech Stack I do usually work with

   

Tech Stack I used to work with, but is chosen by clients very occasionally

  

Note: google cloud platfrom is chosen by customers more rarely than aws one. Openstack even more rarely than google cloud :)

Languages I am familiar with

       

Note: Lua - in scope of kong and nginx only

I am helping customers with ops solutions for most often used cd/ci systems

    

usually using, but not limited to

 

CV Website • Reddit • Twitter • LinkedIn • Contact

devops-tf-eks's Issues

Explanation of local.env and terraform.workspace

First off want to say stellar work man I really appreciate you putting all of this together!

It seems just about every K8 tutorial is around setting everything up from scratch in a new VPC. Ideally I'd like to spin up this TF plan inside my existing VPC so we can begin to migrate from docker swarm to this cluster. My plan was to basically skip the initial stage of the VPC config and then translate the rest of the config to match our existing IDs.

The TF variable file I've been handed down is very basic compared to this, I did read up on what workspaces are and we aren't using them to my knowledge. (Or maybe just using the default one, I've never changed workspaces.)

The two thing's I'm confused on are

1. What ${terraform.workspace} is going to do, is it just going to use the existing workspace or is it defining a new one?
2. What is ${local.env} doing? I've noticed it defined in a few places is that simply calling the locals envs?

I'm sure I can take all of that stuff out and dumb it down to match our stuff but if you don't mind explaining how those work I'd really appreciate it!

locals {
  env = "${terraform.workspace}"

  availabilityzone = "${var.AWS_REGION}a"
  availabilityzone2 = "${var.AWS_REGION}b"

  cluster_name= "${local.env}-cluster"

//  NOTE: The usage of the specific kubernetes.io/cluster/*
//  resource tags below are required for EKS and Kubernetes to discover
//  and manage networking resources.

  common_tags = "${map(
    "Environment", "${local.env}",
    "kubernetes.io/cluster/${local.cluster_name}", "shared"
  )}"
}

  name = "EKSClusterRole-${local.env}",
  description = "Allows EKS to manage clusters on your behalf.",
  assume_role_policy = <<POLICY
{
   "Version":"2012-10-17",
   "Statement":[
      {
         "Effect":"Allow",
         "Principal":{
            "Service":"eks.amazonaws.com"
         },
         "Action":"sts:AssumeRole"
      }
   ]
}
POLICY
}```

https://github.com/opsgenie/kubernetes-event-exporter

https://github.com/opsgenie/kubernetes-event-exporter