k-mitevski / terraform-k8s Goto Github PK
View Code? Open in Web Editor NEWExample code for provisioning Kubernetes clusters on EKS using Terraform.
Example code for provisioning Kubernetes clusters on EKS using Terraform.
For learners who struggle to upgrade to most recent version numbers, here is a hint based on 06_terraform_envs_customised
:
$ diff -up main.tf main_v19.tf
--- main.tf 2023-04-11 12:07:31.933612969 +0200
+++ main_v19.tf 2023-04-13 21:37:57.794521841 +0200
@@ -66,13 +66,15 @@ module "vpc" {
module "eks" {
source = "terraform-aws-modules/eks/aws"
- version = "18.30.3"
+ version = "19.13.0"
cluster_name = "eks-${var.cluster_name}"
cluster_version = "1.24"
subnet_ids = module.vpc.private_subnets
vpc_id = module.vpc.vpc_id
+ cluster_endpoint_public_access = true
+
eks_managed_node_groups = {
first = {
desired_capacity = 1
@@ -82,16 +84,6 @@ module "eks" {
instance_type = var.instance_type
}
}
- node_security_group_additional_rules = {
- ingress_allow_access_from_control_plane = {
- type = "ingress"
- protocol = "tcp"
- from_port = 9443
- to_port = 9443
- source_cluster_security_group = true
- description = "Allow access from control plane to webhook port of AWS load balancer controller"
- }
- }
}
resource "aws_iam_policy" "worker_policy" {
See https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/UPGRADE-19.0.md
is there any way to retrive the load balancer utl(DNS name) using terraform output? when we deploy through helm
Hi there,
Thank you for the awesome tutorial at https://learnk8s.io/terraform-eks#you-can-provision-an-eks-cluster-with-terraform-too... Very useful as I was looking for an example to get different clusters per environment... I just need 2... really appreciated your work!!!
Just got an error creating the cluster using the step 6. I had updated a couple of properties shown below, but here's the error...
I'm getting the following error:
module.prd_cluster.module.eks.aws_iam_role_policy_attachment.workers_AmazonEKS_CNI_Policy[0]: Refreshing state... [id=eks-prd-super-cash-example-com20201018045153077400000007-2020101804515980130000000a]
module.prd_cluster.module.eks.aws_iam_role_policy_attachment.workers_AmazonEC2ContainerRegistryReadOnly[0]: Refreshing state... [id=eks-prd-super-cash-example-com20201018045153077400000007-20201018045159789200000008]
module.prd_cluster.module.eks.aws_iam_role_policy_attachment.workers_AmazonEKSWorkerNodePolicy[0]: Refreshing state... [id=eks-prd-super-cash-example-com20201018045153077400000007-2020101804515988710000000b]
module.prd_cluster.module.eks.aws_iam_role_policy_attachment.workers_additional_policies[0]: Refreshing state... [id=eks-prd-super-cash-example-com20201018045153077400000007-20201018045159794400000009]
Error: Kubernetes cluster unreachable: Get https://44C5045D2C00520DBF55914A260A17C8.
gr7.sa-east-1.eks.amazonaws.com/version?timeout=32s: dial tcp: lookup
44C5045D2C00520DBF55914A260A17C8.gr7.sa-east-1.eks.amazonaws.com on 192.168.1.1:53:
read udp 192.168.1.35:54700->192.168.1.1:53: i/o timeout
At this point, I know I can ping amazonaws.com... But maybe we are missing a security group? The cluster got created...
$ terraform version
Terraform v0.13.4
+ provider registry.terraform.io/hashicorp/aws v3.11.0
+ provider registry.terraform.io/hashicorp/helm v1.3.1
+ provider registry.terraform.io/hashicorp/kubernetes v1.13.2
+ provider registry.terraform.io/hashicorp/local v2.0.0
+ provider registry.terraform.io/hashicorp/null v3.0.0
+ provider registry.terraform.io/hashicorp/random v3.0.0
+ provider registry.terraform.io/hashicorp/template v2.2.0
$ aws eks list-clusters
{
"clusters": [
"eks-prd-super-cash-example-com",
"eks-ppd-super-cash-example-com"
]
}
ATTENTION: The article doesn't mention the creation of the
aws-iam-authenticator
- All the kubeconfig files were created with the authenticator dependency
$ kubectl get pods --all-namespaces
Unable to connect to the server: getting credentials: exec: exec: "aws-iam-authenticator": executable file not found in $PATH
$ brew install aws-iam-authenticator
$ ls -la kubeconfig_eks-p*
-rw-r--r-- 1 marcellodesales staff 2056 Oct 18 01:52 kubeconfig_eks-ppd-super-cash-example-com
-rw-r--r-- 1 marcellodesales staff 2056 Oct 18 01:51 kubeconfig_eks-prd-super-cash-example-com
$ kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
default ingress-aws-alb-ingress-controller-6ccd59df99-8lsvh 0/1 Pending 0 29m
kube-system coredns-59dcf49c5-5wkkf 0/1 Pending 0 32m
kube-system coredns-59dcf49c5-hbqtl 0/1 Pending 0 32m
1.17
to 1.18
private_subnets = ["172.16.1.0/24", "172.16.3.0/24", "172.16.5.0/24"]
public_subnets = ["172.16.2.0/24", "172.16.4.0/24", "172.16.6.0/24"]
unreachable
, I can see that the certs are incorrect...$ curl -v https://DCF5F17BFF0ACDC562845DA97F3B171F.sk1.sa-east-1.eks.amazonaws.com/api/v1/namespaces/kube-system/configmaps
* Trying 54.207.147.62...
* TCP_NODELAY set
* Connected to DCF5F17BFF0ACDC562845DA97F3B171F.sk1.sa-east-1.eks.amazonaws.com (54.207.147.62) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS alert, unknown CA (560):
* SSL certificate problem: unable to get local issuer certificate
* Closing connection 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Thank you
Marcello
I created the cluster successfully, but I am unable to access the ec2 instance directly? I see there is no public-ip for the instance that got created? How do we specify a public ip to the node-group?
Thx for the article. Could you update it with helm repo? I suppouse it should be now:
helm repo add eks https://aws.github.io/eks-charts
and helm install eks/aws-load-balancer-controller
. According to readme from https://github.com/aws/eks-charts/tree/master/stable/aws-load-balancer-controller there is one more step needed kubectl apply -k "github.com/aws/eks-charts/stable/aws-load-balancer-controller//crds?ref=master"
but I do not know how to include that in terraform
I am following this blog
When I tried to run terraform apply
on 02_terraform_node_pools
I found this error
Error: creating CloudWatch Logs Log Group (/aws/eks/learnk8s/cluster): ResourceAlreadyExistsException: The specified log group already exists
│
│ with module.eks.aws_cloudwatch_log_group.this[0],
│ on .terraform/modules/eks/main.tf line 80, in resource "aws_cloudwatch_log_group" "this":
│ 80: resource "aws_cloudwatch_log_group" "this" {
How to fix that.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.