<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Ravi Yasakeerthi</title>
    <description>The latest articles on Forem by Ravi Yasakeerthi (@lkravi).</description>
    <link>https://forem.com/lkravi</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F930446%2F9c889211-9856-4a61-beb2-ebb397ea38e1.jpeg</url>
      <title>Forem: Ravi Yasakeerthi</title>
      <link>https://forem.com/lkravi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/lkravi"/>
    <language>en</language>
    <item>
      <title>EKS Blueprints - easier and faster way to adopt Kubernetes</title>
      <dc:creator>Ravi Yasakeerthi</dc:creator>
      <pubDate>Sun, 13 Nov 2022 15:59:48 +0000</pubDate>
      <link>https://forem.com/aws-builders/eks-blueprints-easier-and-faster-way-to-adopt-kubernetes-4ln9</link>
      <guid>https://forem.com/aws-builders/eks-blueprints-easier-and-faster-way-to-adopt-kubernetes-4ln9</guid>
      <description>&lt;p&gt;In the microservices world, a considerable amount of containerized applications are run on Kubernetes. It's one of the best open-source projects of all time. However, adopting it is a different story. Due to the complexity and lack of inadequate IT resources, many organizations find it challenging. &lt;/p&gt;

&lt;p&gt;In this journey, if we think about the pain points which are holding the development teams back.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Developer wait time. It takes weeks to provision the infrastructure and then configure it with the required add-ons.&lt;/li&gt;
&lt;li&gt;Difficulty in tracking infrastructure changes over time.&lt;/li&gt;
&lt;li&gt;Lack of Automation. Software is manually deployed on an ad-hoc basis.&lt;/li&gt;
&lt;li&gt;Tooling and configuration inconsistencies across teams and environments.&lt;/li&gt;
&lt;li&gt;Ensure the security best practices on cluster and application levels.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Imagine if we could have a template that helps us to address all these pain points and accelerate time to market. EKS Blueprints offers all of it. &lt;/p&gt;

&lt;h2&gt;
  
  
  What is EKS Blueprints
&lt;/h2&gt;

&lt;p&gt;It's a set of Infrastructures as Code scripts organized as a template that helps you provision EKS clusters, bootstrapped with all required add-ons to deploy and operate workloads in the cluster. Once a template is configured, you can use it as a blueprint to spawn consistent environments across multiple AWS accounts and regions.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fbw7yjnrtp9c54pn9m2vo.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fbw7yjnrtp9c54pn9m2vo.png" alt="Image description"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Benefits
&lt;/h2&gt;

&lt;p&gt;Once we adopt EKS Blueprints with GitOps to manage the application delivery, we can eliminate the end-to-end manual processes. Create any number of  Well-Architected environments, and destroy them at will. Then, recreate them quickly or revert them to any point in time. Also can manage teams, namespaces, and access control from the same git repo where you define the infrastructure. This means you can iterate rapidly. Consistency is another significant benefit we can achieve with IaC. It also allows the entire infra to be version controlled and updated using proper review and approval processes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Live Demo
&lt;/h2&gt;

&lt;p&gt;&lt;iframe width="710" height="399" src="https://www.youtube.com/embed/AavVfkZQp4k"&gt;
&lt;/iframe&gt;
&lt;/p&gt;

&lt;h2&gt;
  
  
  Repos
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Repos used for the live demo.
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://github.com/lkravi/eks_blueprints" rel="noopener noreferrer"&gt;https://github.com/lkravi/eks_blueprints&lt;/a&gt;&lt;br&gt;
&lt;a href="https://github.com/lkravi/eks_blueprints_workloads" rel="noopener noreferrer"&gt;https://github.com/lkravi/eks_blueprints_workloads&lt;/a&gt;&lt;br&gt;
&lt;a href="https://github.com/lkravi/eks_blueprints_demo_app" rel="noopener noreferrer"&gt;https://github.com/lkravi/eks_blueprints_demo_app&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  AWS EKS BluePrint for Terraform Repo
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://github.com/aws-ia/terraform-aws-eks-blueprints" rel="noopener noreferrer"&gt;https://github.com/aws-ia/terraform-aws-eks-blueprints&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Finally I would like to thank awesome AWS containers team for initiating this Open source repo and making our life easier. &lt;a href="https://www.linkedin.com/in/askulkarni84/" rel="noopener noreferrer"&gt;Apoorva_Kulkarni&lt;/a&gt;, &lt;a href="https://www.linkedin.com/in/kevin-coleman-a3737326/" rel="noopener noreferrer"&gt;Kevin_Coleman&lt;/a&gt;, &lt;a href="https://www.linkedin.com/in/mikhail-shapirov-41968612/" rel="noopener noreferrer"&gt;Mikhail_Shapirov&lt;/a&gt;, &lt;a href="https://www.linkedin.com/in/varaprofile/" rel="noopener noreferrer"&gt;Vara_Bonthu&lt;/a&gt;, &lt;a href="https://www.linkedin.com/in/zvika-nadav/" rel="noopener noreferrer"&gt;Zvika Nadav&lt;/a&gt;&lt;/p&gt;

</description>
      <category>aws</category>
      <category>eks</category>
      <category>terraform</category>
      <category>iac</category>
    </item>
    <item>
      <title>Create your own Kubernetes Cluster in 15 Minutes on AWS EC2</title>
      <dc:creator>Ravi Yasakeerthi</dc:creator>
      <pubDate>Wed, 26 Oct 2022 12:39:50 +0000</pubDate>
      <link>https://forem.com/aws-builders/create-your-own-kubernetes-cluster-in-15-minutes-on-aws-ec2-4f5i</link>
      <guid>https://forem.com/aws-builders/create-your-own-kubernetes-cluster-in-15-minutes-on-aws-ec2-4f5i</guid>
      <description>&lt;p&gt;I was thinking about this project for a long time and finally, I was able to find some time to put things together. I know, these days it’s not a big deal to quickly spin up a Kubernetes cluster with most of the cloud service providers. But we don’t have full control over them as they are managed by cloud providers. Sometimes we all got requirements to change bits and pieces here and there to try new things in Kubernetes clusters. It’s always nice if we can quickly spin up a k8 cluster where we can manage all the pieces as we need.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F3yvdqf7tieevu5af7zza.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F3yvdqf7tieevu5af7zza.png" alt="Image description"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;At the time of this article, I managed to complete the Highly Available multi-master Kubernetes cluster as per the above architecture diagram. Once you apply the Terraform code, it will do the infrastructure provisioning and then the cluster configurations with Ansible. Although, I didn’t include the Ingress traffic management part and the post cluster configuration in this repo as I have already discussed them in the article linked &lt;a href="https://medium.com/@lkravi/aws-eks-with-terraform-gitops-7c5f3d60525d" rel="noopener noreferrer"&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Let me walk you through the code and quick demo.&lt;/p&gt;

&lt;p&gt;&lt;iframe width="710" height="399" src="https://www.youtube.com/embed/Oxv7ZA-iOpc"&gt;
&lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;As you can see in the demo, We have full control over all the layers. for example, if we need to try out different container runtime, we can change the ansible-playbook and quickly spin up a new cluster with the required new configuration. One thing to note, I didn’t pay much attention to security hardening at the moment as this is just an experimental cluster. So this is not good for production workloads. But I’m planning to improve the code 😊 as soon as I found more time.&lt;/p&gt;

&lt;p&gt;GitHub Repo : &lt;a href="https://github.com/lkravi/kube8aws" rel="noopener noreferrer"&gt;https://github.com/lkravi/kube8aws&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I know that there are many areas in which we can improve on this repo. If you find anything interesting in this repo. feel free to contribute.&lt;/p&gt;

</description>
      <category>ec2</category>
      <category>terraform</category>
      <category>ansible</category>
      <category>automation</category>
    </item>
  </channel>
</rss>
