This is rare. people everywhere teach the easy stuff, but real automation is found to be nowehere. Good work brother !! very few mix jenkins and terraform
Bravo!!!! This is hands down an easy to learn tutorial. Thank you so much for this. I will try monitoring with cloudwatch and grafana or with prometheus and grafana.
Nice one. Do we have to run this pipeline again and again if we want to make some changes like a diff version of the pod image or so, or create a separate pipeline that will deploy only the changes in the same eks cluster or the eks cluster will recreate using your pipeline and redeploy everything. What will be downtown in that case?
Hi I Have a question here in eks terraform file, you already mentioned instance_types under eks_managed_node_group_defaults why again instance_types under eks_managed_node_group
good video, but can you suggest below points: 1: You created a new VPC but suppose if we would need to use our own custom VPC which already in use with other services. 2: How we can integrate existing EKS cluster upgradation process in Jenkins and terraform code to upgrade where when we trigger the jenkins job then it ask you want to create or upgrade when we choose upgrade then we would have the option to enter the version once done, then it will ask to upgrade the node groups. can you create a video on the same if possible. 3: If we provision EKS in free tier account for testing with 1 node group 1 t2.micro instance then how much costing for 24 hours only.
This is rare. people everywhere teach the easy stuff, but real automation is found to be nowehere. Good work brother !! very few mix jenkins and terraform
I agree with you. Thank you for your kind words 🙏
Keep supporting!
Bravo!!!! This is hands down an easy to learn tutorial. Thank you so much for this. I will try monitoring with cloudwatch and grafana or with prometheus and grafana.
Thanks for the feedback! Keep supporting 🙌
Nice one. Do we have to run this pipeline again and again if we want to make some changes like a diff version of the pod image or so, or create a separate pipeline that will deploy only the changes in the same eks cluster or the eks cluster will recreate using your pipeline and redeploy everything. What will be downtown in that case?
Everyone uses the same pipeline. And downtime depends on what changes you are making
@@amonkincloud Thank you 🙂
Hi
I Have a question here
in eks terraform file, you already mentioned instance_types under eks_managed_node_group_defaults
why again instance_types under eks_managed_node_group
If you want to overwrite the default values then you can use this
good video, but can you suggest below points:
1: You created a new VPC but suppose if we would need to use our own custom VPC which already in use with other services.
2: How we can integrate existing EKS cluster upgradation process in Jenkins and terraform code to upgrade where when we trigger the jenkins job then it ask you want to create or upgrade when we choose upgrade then we would have the option to enter the version once done, then it will ask to upgrade the node groups. can you create a video on the same if possible.
3: If we provision EKS in free tier account for testing with 1 node group 1 t2.micro instance then how much costing for 24 hours only.
1. Yes you can
2. EKS UI itself has an upgrade button
3. Please check pricing documentation for details on the cost
If you can increase font size it would be nice
Sure, I have noted it.
For this video please refer to the GitHub repository in parallel while watching
Please create like this SQS creation video via paramerize
Sure
also, give as a full cicd pipeline using AWS services only
Jenkins is the standard tool used in the industry. But if you are willing to explore AWS Services, please go with AWS CodePipeline
Please suggest can and should we automate eks cluster upgrade via Jenkins parameterize please create a project video
Yes you can