🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting - me@antonputra.com 👉 [UPDATED] AWS EKS Kubernetes Tutorial [NEW]: ua-cam.com/play/PLiMWaCMwGJXnKY6XmeifEpjIfkWRo9v2l.html&si=wc6LIC5V2tD-Tzwl
Can you please implement everything in terraform? Maybe an idea for an upcoming video It would help a lot! And please explain a bit more why choose one configuration over the other. Like the thought process behind each step. :) Thank you for making these! Much appreciated
I have a video explaining how to install Helm in Kubernetes and deploying Nginx ingress - ua-cam.com/video/ezX4D1ZK5mA/v-deo.html I'm planning to start a playlist perhaps next week dedicated to Helm 3. I will go deep into how to integrate Helm 3 with Kubernetes, build helm charts, some of the building templating functions, how to version, and distribute Helm charts with Chartmuseum and S3.
Excellent introduction! Which roles have both nodes? One master and one worker? How could you add another master and further worker nodes? Keep up with the good work!
Well, EKS is managing (high available) control plane for you, you don't need to add master nodes.. In order to add worker nodes, you can simply increase auto scaling group, new nodes will join cluster automatically.
Followed this video exactly, but got an error: `Error: error waiting for EKS Node Group to create: unexpected state 'CREATE_FAILED', wanted target 'ACTIVE'.`. This was the case even after adding `cluster_endpoint_private_access = true` in `module eks` block
1. In your typical EKS (Kubernetes) setup, you would have worker nodes deployed in a private subnet (default route to nat). If you want to expose services to the internet, you will use something like a service of the type load balancer. It will be placed in the public subnet (default route to internet gateway). 2. No, you have to have subnets in different AZs to meet EKS requirements.
We create an eks cluster and say, we want to make sure curl ifconfig.me on any pod gives the same ip. Is it possible to do that ? One approach i find is creating a NAT-Gateway to the worker-nodes subnet (public) but, it didnt work. Do we have other ways to do it ??
🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting - me@antonputra.com
👉 [UPDATED] AWS EKS Kubernetes Tutorial [NEW]: ua-cam.com/play/PLiMWaCMwGJXnKY6XmeifEpjIfkWRo9v2l.html&si=wc6LIC5V2tD-Tzwl
Get Full-Length High-Quality DevOps Tutorials for Free - Subscribe Now! - ua-cam.com/users/AntonPutra
👉 How to Manage Secrets in Terraform - ua-cam.com/video/3N0tGKwvBdA/v-deo.html
👉 Terraform Tips & Tricks - ua-cam.com/video/7S94oUTy2z4/v-deo.html
👉 ArgoCD Tutorial - ua-cam.com/video/zGndgdGa1Tc/v-deo.html
🟢 [New] Terragrunt Tutorial: Create VPC, EKS from Scratch! (Step-by-Step) - ua-cam.com/video/yduHaOj3XMg/v-deo.html
🔴UPDATED🔴: How to Create EKS Cluster Using Terraform - ua-cam.com/video/MZyrxzb7yAU/v-deo.html
Available on December 27
Can you please implement everything in terraform? Maybe an idea for an upcoming video
It would help a lot!
And please explain a bit more why choose one configuration over the other. Like the thought process behind each step. :)
Thank you for making these! Much appreciated
Thank you, sounds like a good idea to put everything in tf:) I will try to do it next week.
@@AntonPutra can you please make it a collection and share the link... appreciate your work. Thanks
🔴UPDATED🔴 How to create EKS Cluster using Terraform MODULES (AWS Load Balancer Controller + Autoscaler + IRSA) - ua-cam.com/video/kRKmcYC71J4/v-deo.html
Thanks for the video, please have you got any video that shows how to integrate helm to kubernetes??
I have a video explaining how to install Helm in Kubernetes and deploying Nginx ingress - ua-cam.com/video/ezX4D1ZK5mA/v-deo.html
I'm planning to start a playlist perhaps next week dedicated to Helm 3. I will go deep into how to integrate Helm 3 with Kubernetes, build helm charts, some of the building templating functions, how to version, and distribute Helm charts with Chartmuseum and S3.
@@AntonPutra thank you very much. Your contents are brilliant 👏.. Please also include videos on hashicorp vault integration.
@@joeb.1163 Thank you for the support, I will definitely create a series about vault as well:)
Excellent introduction! Which roles have both nodes? One master and one worker?
How could you add another master and further worker nodes?
Keep up with the good work!
Well, EKS is managing (high available) control plane for you, you don't need to add master nodes.. In order to add worker nodes, you can simply increase auto scaling group, new nodes will join cluster automatically.
How to add cloudwatch to get logs from the EKS cluster?
I would recommend using fluentd or fluentbit, deploy it as a daemonset on each Kubernetes node, scrape docker logs and upload it to CloudWatch.
Hi Anton,
Don't you have a video to create a GCP Kubernetes cluster from scratch with Terraform? That would be definitely nice!!
Not yet, currently I'm working on terraform blue green and canary deployment.. I'll do GCP Kubernetes right after it.
@@AntonPutra Excellent, just can't wait to see it! ;-)
Why are you using two subnets, one public and one private? In which are the worker nodes placed?
Private subnet is used to place Kubernetes worker nodes and public subnet for load balancer to expose Kuberntes services to the internet.
Followed this video exactly, but got an error: `Error: error waiting for EKS Node Group to create: unexpected state 'CREATE_FAILED', wanted target 'ACTIVE'.`. This was the case even after adding `cluster_endpoint_private_access = true` in `module eks` block
It's possible that the version of terraform is slightly outdated. I will refresh this tutorial soon!
Hi Anton, can we create with this TF script a private resources instead of EC2 in fargate?
At this point, I don't have a lot of experience with AWS fargate. I will definitely explore it and share what I've learned soon..
Why do we need 2 subnets?
And do each have to be in a different AZ? Can you have one subnet in two AZs to meet EKS requirements?
1. In your typical EKS (Kubernetes) setup, you would have worker nodes deployed in a private subnet (default route to nat). If you want to expose services to the internet, you will use something like a service of the type load balancer. It will be placed in the public subnet (default route to internet gateway).
2. No, you have to have subnets in different AZs to meet EKS requirements.
Bring up Kubernetes (EKS) cluster with eksctl - ua-cam.com/video/jjPrH8yfkCs/v-deo.html
2022 update:
change subnets to subnet_ids and node_groups to eks_managed_node_groups
I have updated video and code - ua-cam.com/video/MZyrxzb7yAU/v-deo.html
We create an eks cluster and say, we want to make sure curl ifconfig.me on any pod gives the same ip. Is it possible to do that ?
One approach i find is creating a NAT-Gateway to the worker-nodes subnet (public) but, it didnt work. Do we have other ways to do it ??
Do you need to provide this IP to the client that they can whitelist or you just need a static IP for your load balancer?
@@AntonPutra I need to provide an IP to client so he can whitelist