<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Manoj Bhagwat on Medium]]></title>
        <description><![CDATA[Stories by Manoj Bhagwat on Medium]]></description>
        <link>https://medium.com/@manoj-bhagwat60?source=rss-726b1815a859------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EINIpX2pWFYlVwk4ioktBA.jpeg</url>
            <title>Stories by Manoj Bhagwat on Medium</title>
            <link>https://medium.com/@manoj-bhagwat60?source=rss-726b1815a859------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:31:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@manoj-bhagwat60/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Enhancing Security: How HeyJobs Implemented OIDC to Fortify its CI/CD Pipeline]]></title>
            <link>https://medium.com/heyjobs-tech/enhancing-security-how-heyjobs-implemented-oidc-to-fortify-its-ci-cd-pipeline-b10e52e98683?source=rss-726b1815a859------2</link>
            <guid isPermaLink="false">https://medium.com/p/b10e52e98683</guid>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[oidc]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <dc:creator><![CDATA[Manoj Bhagwat]]></dc:creator>
            <pubDate>Wed, 31 Jan 2024 18:40:29 GMT</pubDate>
            <atom:updated>2024-01-31T18:40:29.720Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SCTi0-odoiTauJZS" /></figure><h3><strong><em>Introduction</em></strong></h3><p>In the realm of software development, Continuous Integration and Continuous Deployment (CI/CD) pipelines have emerged as indispensable assets, facilitating the rapid and reliable deployment of features and products. As organizations embrace DevOps practices, CI/CD pipelines have become a cornerstone for streamlining the development-to-deployment lifecycle.</p><p>The adoption of cloud infrastructure has further amplified the significance of robust CI/CD pipelines. With applications running in the cloud, ensuring the secure and efficient deployment to cloud environments is imperative. This blog explores the pivotal role that CI/CD pipelines play in the modern DevOps landscape, particularly in the context of securing deployments to cloud environments. We will delve into how HeyJobs, a pioneering force in the talent platform industry, has fortified its CI/CD pipeline through the adoption of OpenID Connect (OIDC), ensuring a resilient and secure deployment process for its cloud-based applications.</p><h3>Background</h3><p>Let me give you a bit of the historical context of HeyJobs’ CI/CD pipeline, the teams heavily relied on Circle CI as their primary tool for executing continuous integration and deployment workflows, deploying changes to the production environment multiple times a day.</p><p>The pipelines had been configured with static credentials for these deployments. However, a significant turning point occurred in <strong>January 2023</strong> when <strong>CircleCI</strong> issued a <strong>security alert</strong>, urging users to promptly rotate any stored secrets in response to potential vulnerabilities (details available in the security alert here: <a href="https://circleci.com/blog/january-4-2023-security-alert/">https://circleci.com/blog/january-4-2023-security-alert/</a>).</p><p>This alert acted as a wake-up call, emphasizing the risks associated with static credentials and compelling HeyJobs to reconsider their security practices.</p><h4>Why OIDC for CI/CD Security?</h4><ul><li><strong>Circle CI Support:</strong> Circle CI’s support for OpenID Connect (OIDC) played a decisive role in HeyJobs’ choice, ensuring compatibility with their existing CI/CD infrastructure.</li><li><strong>Dynamic Credentials:</strong> OIDC offers a more secure option by utilizing dynamic credentials, which are short-lived. This contrasts with the previously employed static credentials, reducing the window of vulnerability and enhancing overall security.</li><li><strong>Enhanced Auditability:</strong> OIDC’s token-based authentication enables enhanced auditability, allowing HeyJobs to track and monitor user access and actions within the CI/CD pipeline. This contributes to improved visibility and accountability.</li><li><strong>Scalability:</strong> As HeyJobs continues to scale its operations, OIDC provides a scalable solution for managing authentication and authorization, accommodating the evolving needs of a growing organization without compromising security.</li><li><strong>Token-Based Authorization:</strong> OIDC’s token-based approach to authorization allows for fine-grained control over access rights. This facilitates the implementation of a least privilege principle, limiting access to only what is necessary for each user or component.</li></ul><h4>Solution Workflow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JASTVphA1KCbMkY8" /></figure><h4>Implementation</h4><ul><li><strong>Terraform Module Creation:</strong> We took a proactive approach by developing a Terraform module dedicated to implementing OIDC. This module, designed for repetitive use across multiple environments, standardized OIDC integration, ensuring consistency and reliability in its deployment.</li><li><strong>Pipeline Workflow Update:</strong> The CI/CD pipeline workflow underwent a crucial update to seamlessly incorporate dynamic credentials provided by OIDC. This adjustment marked a fundamental shift from the previous static credential-based approach to a more secure and dynamic authentication mechanism.</li><li><strong>Review and Approval Process:</strong> To maintain transparency and adhere to best practices, the team subjected the updated deployment workflows to a rigorous review and approval process. Repository owners, who play a critical role in overseeing the codebase, provided their insights and approvals, ensuring a collaborative and secure implementation.</li><li><strong>Decommissioning of Static Credentials</strong>: As a critical step towards enhancing security, HeyJobs proceeded with the decommissioning of static credentials. This phase involved removing and deactivating any existing static credentials within the CI/CD pipeline, thereby eliminating potential security vulnerabilities associated with their usage.</li><li><strong>Confluence Documentation</strong>: Also we had done a quick one-pager writeup on this topic so that in the future teams will be autonomous to adopt this for new services</li></ul><h4>Benefits and Impact</h4><ul><li>Enhanced Security Posture</li><li>Standardization and Consistency</li><li>Improved Collaboration and Transparency</li><li>Operational Efficiency</li><li>Future-Proofing and Scalability</li></ul><h4>Conclusion</h4><p>In a nutshell, HeyJobs revamped its CI/CD game by embracing OpenID Connect (OIDC). We ditched the old static credentials for dynamic tokens, amping up security. Thanks to a standardized Terraform module, things are consistent across the board. We streamlined ops by kicking static credentials to the curb, letting us focus on the good stuff. This move isn’t just about today — it’s our way of gearing up for whatever tech adventures tomorrow throws at us! 🚀✨</p><p>Interested in joining our team? <a href="https://hire.heyjobs.co/en-us/careers">Browse our open positions</a> or check out what we do at <a href="https://www.heyjobs.co/en-de">HeyJobs</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b10e52e98683" width="1" height="1" alt=""><hr><p><a href="https://medium.com/heyjobs-tech/enhancing-security-how-heyjobs-implemented-oidc-to-fortify-its-ci-cd-pipeline-b10e52e98683">Enhancing Security: How HeyJobs Implemented OIDC to Fortify its CI/CD Pipeline</a> was originally published in <a href="https://medium.com/heyjobs-tech">HeyJobs Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unleashing the Power of ChatGPT in the World of DevOps]]></title>
            <link>https://medium.com/geekculture/unleashing-the-power-of-chatgpt-in-the-world-of-devops-12832f16e302?source=rss-726b1815a859------2</link>
            <guid isPermaLink="false">https://medium.com/p/12832f16e302</guid>
            <category><![CDATA[pair-programming]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[openai]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Manoj Bhagwat]]></dc:creator>
            <pubDate>Sun, 09 Apr 2023 08:01:56 GMT</pubDate>
            <atom:updated>2023-04-11T08:41:37.214Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qi4EkGnvzg2-vVeD" /><figcaption>Photo by <a href="https://www.pexels.com/@bertellifotografia/">Matheus Bertelli</a> on pexels</figcaption></figure><blockquote>In this blog, we will discuss ChatGPT, a highly popular and trending tool that has recently emerged in the market. Over the past few weeks/months, there have been notable advancements in the AI domain, with ChatGPT’s introduction serving as a highlight. Despite being relatively new, it has generated a mix of anticipation and apprehension regarding its potential capabilities and impact.</blockquote><h3>Introduction</h3><p>In this demonstration, I will guide you through the process of utilizing ChatGPT in the realm of DevOps to build and deploy a containerized application on the AWS Cloud. Let’s begin by creating and deploying a simple PHP application.</p><p>GitHub Code: <a href="https://github.com/manoj8928/sample-php-docker-app">https://github.com/manoj8928/sample-php-docker-app</a></p><h3>ChatGPT: Your Programming Partner</h3><p>You’ll be amazed by the results ChatGPT produces when asked to write code. Let’s examine how it constructs and deploys a container-based application.</p><p>Although this code repository already includes a Dockerfile for building a Docker image, we’ll request ChatGPT to create one using Alpine as the base image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*DHQC6J1YkH-gqPV4Lo_tBQ.png" /></figure><p>The outcome was truly impressive. With the Dockerfile prepared, let’s now ask ChatGPT to produce a CI/CD configuration for a GitHub Action that will push this image to the Amazon ECR on AWS Cloud.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*MLRFQdPpnyfZSTXP7__AAA.png" /></figure><p>The following step involves deploying this containerized application to AWS ECS and exposing it through a public load balancer. Additionally, we aim to utilize Terraform for infrastructure setup. Let’s request ChatGPT to accomplish these tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/1*eq5SI7G2CRFWnqCxzW2DsA.png" /></figure><p>Indeed, the outcome was astonishing. ChatGPT not only generated the entire infrastructure code but also intelligently incorporated an open-source ALB module for the ALB resource.</p><p>Now, to ensure a thoroughly tested deployment, let’s perform unit testing on this infrastructure code. I requested ChatGPT to create unit tests for the application using the Terratest framework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*Wfou4JriQ28I7BPTU-s3SA.png" /></figure><p>Wow, I am genuinely amazed by the results. While I may need to make some minor adjustments to the code, ChatGPT has done a remarkable job in assembling this solution. It took just a few hours to reach this stage, whereas, without ChatGPT, I am confident that it would have taken me at least several days (if not longer) to piece everything together. A big thank you to ChatGPT for significantly simplifying my life as a DevOps engineer!</p><h3>Summary</h3><p>ChatGPT, possessing immense potential, is truly revolutionary. The impact of AI on our work lives has arrived more quickly than anticipated, and its capabilities are nothing short of astounding. As we’ve seen, ChatGPT is still in its early stages, and there’s room for it to mature. As it develops, it’s exciting to imagine how it might evolve further. Let’s embrace ChatGPT as our collaborative programmer, allowing it to enhance our productivity and assist in addressing daily challenges. By testing and utilizing ChatGPT, we can help it mature while simultaneously benefiting from its capabilities to improve our productivity.</p><blockquote>Although there are concerns that ChatGPT may replace developers’ jobs in the future, I remain optimistic. I believe the human brain’s capabilities far surpass those of bots. Even if some jobs are lost to automation, our minds are inherently designed to seek and discover new, innovative opportunities for adaptation. Let these technological advancements challenge us to innovate and grow further.</blockquote><p>Happy Coding!</p><p>Reference links</p><p><a href="https://learnprompting.org/docs/intro">https://learnprompting.org/docs/intro</a> (Great resource / free course to learn more about <strong>prompt engineering</strong>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12832f16e302" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/unleashing-the-power-of-chatgpt-in-the-world-of-devops-12832f16e302">Unleashing the Power of ChatGPT in the World of DevOps</a> was originally published in <a href="https://medium.com/geekculture">Geek Culture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Passing the AWS Security Specialty Certification: My Preparation Journey and Tips [2023]]]></title>
            <link>https://aws.plainenglish.io/passing-the-aws-security-specialty-certification-my-preparation-journey-and-tips-2023-3abafd0499c9?source=rss-726b1815a859------2</link>
            <guid isPermaLink="false">https://medium.com/p/3abafd0499c9</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[journey]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Manoj Bhagwat]]></dc:creator>
            <pubDate>Sun, 19 Mar 2023 11:16:45 GMT</pubDate>
            <atom:updated>2023-03-21T01:50:24.437Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/672/0*1zB-YeNeCQ9lb230.png" /></figure><h3>Introduction</h3><p>In the fast-growing world of cloud computing, AWS is a leading provider of cloud services. As cloud computing is becoming more popular, it is increasingly vital to ensure the security of the cloud infrastructure. This is where AWS Security Specialty Certification comes in. In this blog post, I will be sharing my journey of passing the AWS Security Specialty Certification exam, and the resources I used to prepare for the exam.</p><h3>Preparation</h3><p>I started my preparation with the official AWS Security Specialty Certification exam guide, which provided me with an overview of the exam objectives and the topics I needed to focus on.</p><p>Next, I enrolled in an online course on <a href="https://acloudguru.com/course/aws-certified-security-specialty"><strong>AcloudGuru</strong></a>, which provided me with a comprehensive overview of AWS security services and their implementation.</p><p>In addition to the online course and the official documentation, I used practice tests and mock exams from <strong>Dojo Tutorials</strong> and <strong>Whizlabs</strong> to evaluate my knowledge and identify my weak areas. The practice tests helped me to get a feel for the types of questions I could expect on the exam, and the mock exams provided me with an opportunity to simulate the exam environment and timing.</p><p><strong>Dojo Tutorial</strong>: <a href="https://portal.tutorialsdojo.com/courses/aws-certified-security-specialty-practice-exams/">https://portal.tutorialsdojo.com/courses/aws-certified-security-specialty-practice-exams/</a></p><p><strong>Whizlabs</strong>: <a href="https://www.whizlabs.com/aws-certified-security-specialty/">https://www.whizlabs.com/aws-certified-security-specialty/</a></p><p>Also, I would highly recommend going through <strong>Jayendra Patil&#39;s</strong> blog (<a href="https://jayendrapatil.com/aws-certified-security-speciality-scs-c01-exam-learning-path/"><strong><em>https://jayendrapatil.com/aws-certified-security-speciality-scs-c01-exam-learning-path/</em></strong></a>).</p><p>Another strategy I utilized was taking notes in my diary for all incorrect answers while practicing labs. This allowed me to identify the areas that required more focus and helped me better understand the topics.</p><h3><strong>Exam Day</strong></h3><p>On the day of the exam, I felt confident and well-prepared. The exam consisted of 65 multiple-choice questions, and I had 170 minutes to complete it. I was happy to find that the exam questions were well-written and focused on real-world scenarios. After completing the exam, I received the results after 24 hours, and I was thrilled to find out that I had passed!</p><h3>Conclusion</h3><p>Passing the AWS Security Specialty Certification exam was a great achievement for me. My journey to passing the exam was made possible by the resources I used, including the official AWS documentation, online courses, practice tests, and mock exams. I highly recommend these resources to anyone who is interested in taking the AWS Security Specialty Certification exam. Good luck with your own journey!</p><p><em>More content at </em><a href="https://plainenglish.io/"><strong><em>PlainEnglish.io</em></strong></a><em>.</em></p><p><em>Sign up for our </em><a href="http://newsletter.plainenglish.io/"><strong><em>free weekly newsletter</em></strong></a><em>. Follow us on </em><a href="https://twitter.com/inPlainEngHQ"><strong><em>Twitter</em></strong></a>, <a href="https://www.linkedin.com/company/inplainenglish/"><strong><em>LinkedIn</em></strong></a><em>, </em><a href="https://www.youtube.com/channel/UCtipWUghju290NWcn8jhyAw"><strong><em>YouTube</em></strong></a><em>, and </em><a href="https://discord.gg/GtDtUAvyhW"><strong><em>Discord</em></strong></a><strong><em>.</em></strong></p><p><strong><em>Interested in scaling your software startup</em></strong><em>? Check out </em><a href="https://circuit.ooo/?utm=publication-post-cta"><strong><em>Circuit</em></strong></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3abafd0499c9" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/passing-the-aws-security-specialty-certification-my-preparation-journey-and-tips-2023-3abafd0499c9">Passing the AWS Security Specialty Certification: My Preparation Journey and Tips [2023]</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Monolith to Modules: Our Terraform Migration Journey]]></title>
            <link>https://medium.com/heyjobs-tech/from-monolith-to-modules-our-terraform-migration-journey-f4560e0629c2?source=rss-726b1815a859------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4560e0629c2</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[terraform-modules]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[migration]]></category>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[Manoj Bhagwat]]></dc:creator>
            <pubDate>Fri, 24 Feb 2023 13:27:53 GMT</pubDate>
            <atom:updated>2023-02-24T13:27:53.267Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XT5WmqEDOIv6G-fr.jpg" /></figure><h3><strong>Introduction</strong></h3><p>In the world of infrastructure as code, Terraform is a powerful tool for managing and deploying infrastructure resources across multiple cloud providers. However, as the complexity of infrastructure grows, managing Terraform code can become a daunting task. One solution to this problem is to migrate from a monolithic Terraform codebase to modular code.</p><p>In this blog, we will share our experience and journey of migrating from a monolithic Terraform codebase to modular code. We will discuss the reasons behind our decision to make this change, the challenges we faced during the migration, and the benefits we gained from the new modular approach.</p><p>Join us as we share our insights and best practices, and learn how you too can successfully migrate from monolithic Terraform code to modular code.</p><p><strong>Here is the list of a few challenges:</strong></p><ol><li>The single monolithic repo will be difficult to maintain in the longer run.</li><li>Requires checkout of the entire codebase.</li><li>Terraform modules cannot be versioned.</li><li>Terraform application code is tightly coupled with modules so quite often ended up breaking the production system.</li><li>Limitations around access control. In future, there will be some instances where we may not want every engineer to have access to the entire codebase.</li></ol><p><strong>The solution to the above problem</strong></p><p>Adopting a multi-repo structure will help solve most of the aforementioned challenges, as it provides flexibility in setting up a sustainable structure for the long term.</p><p><strong>The advantages of adopting a Multi-repo structure are as follows:</strong></p><ul><li>The source code is lightweight and easier to manage as each Terraform module (AWS Service) will have its own repository.</li><li>Loosely coupled modules will allow developers to work independently on enhancing Terraform modules without conflicts.</li><li>Proper versioning of modules through git tags and release notes will make it easier to roll back in case of issues and ensure seamless application performance.</li><li>Access management to repositories will be more streamlined and easier to control.</li></ul><h3><strong>Planning the migration</strong></h3><p>As we were planning the migration, we recognized the chance to establish consistent naming conventions for our repositories. Additionally, we aimed to incorporate all relevant best practices for module development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/0*xFwBEi_6pt112XX8.jpg" /></figure><p><strong>Establishing naming standards:</strong> Establishing this standard early on is crucial for a rapidly expanding organization. Without it, things could easily spiral out of control. We ultimately came to a consensus on the following naming conventions for our GitHub repositories.</p><p>&lt;organization name&gt;-tf-module-&lt;provider&gt;-&lt;service&gt;</p><p><strong>Incorporating best practices:</strong> In addition, we aimed to ensure consistency across all our modules in terms of repository structure, ReadMe, and a preconfigured security pipeline. This enables users to quickly set up their own repository with these best practices already in place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3GEbwlaAiLD3zJVlx1k1Hw.png" /></figure><p><strong>Effortless configuration:</strong> As we utilize GitHub as our source code management and Terraform provider, we developed a Terraform module for establishing the Git repository. This approach allowed us to implement and adhere to all the standard best practices.</p><p><a href="https://registry.terraform.io/providers/integrations/github/latest/docs">https://registry.terraform.io/providers/integrations/github/latest/docs</a></p><p><strong>Applying a semantic approach to module versioning</strong>: Defining a release strategy is crucial to avoid confusion and mistakes. After careful consideration, we decided to adopt semantic versioning as our release strategy. This allows us to clearly define versions based on the MAJOR.MINOR.PATCH concept, making it easier to manage and control the release process.</p><p><a href="https://semver.org/">https://semver.org/</a></p><h3><strong>The Migration day</strong></h3><p>We had already communicated a code freeze to the developers as this one-day task was underway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/592/0*Vx7bTbM3DZsSZ3cu.gif" /></figure><p>On the day of migration, we performed the following tasks:</p><ul><li>Established Git repositories for our Terraform modules.</li><li>Moved modules from a monolithic structure to separate repositories.</li><li>Released these new modules with the initial tag of 1.0.0.</li><li>Updated the caller module source of the Infrastructure repository from the local path to the Git URL and pointed it to the 1.0.0 version.</li><li>Validated the changes by running the Terraform pipeline after updating the source to the Git URL.</li></ul><h4><strong>Conclusion</strong></h4><p>By splitting our monolithic repository into loosely coupled Terraform modules, we have improved our process standardization and module release management. As a result, we have seen a reduction in production incidents and are experiencing better periods of rest. 😊</p><p>Interested in joining our team? <a href="https://hire.heyjobs.co/en-us/careers">Browse our open positions</a> or check out what we do at <a href="https://www.heyjobs.co/en-de">HeyJobs</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4560e0629c2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/heyjobs-tech/from-monolith-to-modules-our-terraform-migration-journey-f4560e0629c2">From Monolith to Modules: Our Terraform Migration Journey</a> was originally published in <a href="https://medium.com/heyjobs-tech">HeyJobs Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Docker Security? Beginner’s Guide]]></title>
            <link>https://medium.com/heyjobs-tech/what-is-docker-security-beginners-guide-d7230eda722a?source=rss-726b1815a859------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7230eda722a</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[container-security]]></category>
            <category><![CDATA[heyjobs]]></category>
            <dc:creator><![CDATA[Manoj Bhagwat]]></dc:creator>
            <pubDate>Thu, 02 Jun 2022 08:09:09 GMT</pubDate>
            <atom:updated>2022-06-30T07:37:13.988Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EgzynDaHsS8RieeP9839Lw.png" /></figure><p>Here at <strong>HeyJobs</strong>, we use Docker for running our microservices on AWS Cloud. Running an application as a container has its own benefits like portability, performance, agility, isolation, and scalability.</p><p>Deploying these services as the container is much easier. We need to ask ourselves a few hard questions so that in the future we don&#39;t end up having Security issues.</p><ol><li>How are we making sure that these containers are secure enough for the production environment ?.</li><li>Are your Dockerfiles written following all the security best practices?.</li><li>Tested container images for vulnerabilities ?.</li><li>Have we optimized our docker images ?.</li></ol><p>Let&#39;s go step by step and discuss these topics in detail.</p><p><strong>What is Dockerfile ?.</strong></p><blockquote>A Dockerfile is a text document that contains all the commands a user can call on the command line to assemble an image.</blockquote><p>Example of a typical Dockerfile (nginx):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BjShEpvYUBRzRpp3IzHzPQ.png" /><figcaption><a href="https://github.com/dockerfile/nginx/blob/master/Dockerfile">https://github.com/dockerfile/nginx/blob/master/Dockerfile</a></figcaption></figure><p><strong>Why should we follow security best practices for Dockerfiles?.</strong></p><ul><li>Dockerfiles are a blueprint for building your Docker container images.</li><li>Dockerfiles are a codified version of your application and infrastructure.</li><li>Dockerfiles are among the key components in the entire supply chain security.</li><li>Dockerfiles need to be part of your security posture to maintain the highest level of security comprehensively.</li><li>Insecure Dockerfiles can cause serious security issues.</li></ul><p><strong>Some best practices for Dockerfiles are as below:</strong></p><ul><li>Start with a small version of the image.</li><li>Create ephemeral containers.</li><li>Exclude files from the image with <strong>.dockerignore</strong> — it works similarly to <strong>.gitignore</strong> in Git.</li><li>Use multi-stage builds to reduce the image size and its attack surface.</li><li>Create multi-line arguments in a structured way, and reduce the image layers.</li><li>Minimize the number of layers by grouping similar commands. For example: RUN apt-get update &amp;&amp; apt-get install -y curl.</li><li>Leverage the build cache and remove the package manager cache: rm -rf /var/lib/apt/lists/* .</li><li>Create your own base image like a golden image.</li></ul><p><strong>The Docker community also recommends a few other best practices :</strong></p><ul><li>Use the COPY instruction to copy only the necessary files. Avoid executing instructions such as COPY . . .</li><li>Only install what you need. For example, use the --no-install-recommendsoption.</li><li>Use a specific image tag; avoid the latest tag.</li><li>Set non-root user and group.</li><li>Use only trusted and official base images.</li><li>Don’t store secrets or sensitive information in Dockerfiles.</li><li>Don’t install SSH or similar services that may expose your containers.</li></ul><p>Till now we have seen a number of standard best practices to follow. Now let’s see how we can apply it in our DevOps workflow.</p><h4><strong>Use tools and techniques to validate the same</strong></h4><ol><li><strong>Hadolint — Haskell Dockerfile Linter</strong></li></ol><p>A smarter Dockerfile linter that helps you build <a href="https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices">best practice</a> Docker images. The linter parses the Dockerfile into an AST and performs rules on top of the AST. It stands on the shoulders of <a href="https://github.com/koalaman/shellcheck">ShellCheck</a> to lint the Bash code inside RUN instructions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YDzK-EiYC_4HEbhe.png" /><figcaption><a href="https://github.com/hadolint/hadolint">https://github.com/hadolint/hadolint</a></figcaption></figure><p>It is available on Github but it makes more sense to integrate these linters in your deployment CI/CD pipelines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-_nN2DfJCGxa2BRW" /><figcaption>Hadolint linter check against Dockerfile on local</figcaption></figure><p><strong>2. Dockle — Docker image linter for security</strong></p><p>It performs multiple CIS benchmark checks, as well as more generic checks that are considered recommended best practices.</p><p><a href="https://github.com/goodwithtech/dockle">GitHub - goodwithtech/dockle: Container Image Linter for Security, Helping build the Best-Practice Docker Image, Easy to start</a></p><p><strong>CIS Benchmark comparison</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A1BBcogtAmmL-80m.png" /></figure><p><strong>Checks for Dockerfiles</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O-GBj8-dBgvIwHpr.png" /></figure><p><strong>3. dive — Explore each layer in a Docker image</strong></p><p>It enables exploring a Docker image and layer contents and discovering ways to shrink the size of your Docker/OCI image. Find out more about the project on <a href="https://github.com/wagoodman/dive">https://github.com/wagoodman/dive</a>.</p><p><em>Dive offers a rich exploratory feature set. For example, it can:</em></p><ul><li>Show broken Docker image contents by layer.</li><li>Indicate what’s changed in each layer.</li><li>Estimate image efficiency.</li><li>Be included in CI integration.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n7-uKvF0lNlVOwyx" /><figcaption><a href="https://github.com/wagoodman/dive">https://github.com/wagoodman/dive</a></figcaption></figure><p><strong>4. IDE linters and plugins</strong></p><p>We usually use IDEs for writing Dockerfiles; there are some IDE linters and plugins that help us enforce best practices and identify potential security issues in the early stages of our SDLC lifecycle.</p><p>For example, this is a <a href="https://marketplace.visualstudio.com/items?itemName=henriiik.docker-linter">Docker linter plugin for Microsoft Visual Studio Code</a>.</p><h4>Conclusion</h4><p>We looked at security best practices that we should follow while writing Dockeriles and we explore a few tools and techniques that we can integrate into our CI/CD pipeline and development workflows for quick turnaround.</p><p><strong>Resources and references</strong></p><ul><li><a href="https://www.youtube.com/watch?v=JofsaZ3H1qM">Dockerfile Best Practices talk at dockercon 19</a></li><li><a href="https://docs.docker.com/develop/develop-images/dockerfile_best-practices">https://docs.docker.com/develop/develop-images/dockerfile_best-practices</a></li><li><a href="https://github.com/hexops/dockerfile">https://github.com/hexops/dockerfile</a></li><li><a href="https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html">https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html</a></li><li><a href="https://snyk.io/blog/10-docker-image-security-best-practices">https://snyk.io/blog/10-docker-image-security-best-practices</a></li><li><a href="https://github.com/goodwithtech/dockle">https://github.com/goodwithtech/dockle</a></li><li><a href="https://github.com/hadolint/hadolint">https://github.com/hadolint/hadolint</a></li><li><a href="https://www.conftest.dev/">https://www.conftest.dev</a></li><li><a href="https://github.com/madhuakula/docker-security-checker">https://github.com/madhuakula/docker-security-checker</a></li></ul><p><strong>Seems cool, exciting, and fun stuff? Then Join our team at HeyJobs!</strong></p><blockquote><em>Do you like building things and working at scale while we are in hypergrowth? Interested in joining HeyJobs</em>? <a href="https://hire.heyjobs.co/en-us/careers">Check out our open positions here.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7230eda722a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/heyjobs-tech/what-is-docker-security-beginners-guide-d7230eda722a">What is Docker Security? Beginner’s Guide</a> was originally published in <a href="https://medium.com/heyjobs-tech">HeyJobs Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kiali: Manage, visualize, validate and troubleshoot your Service mesh!]]></title>
            <link>https://medium.com/swlh/kiali-manage-visualize-validate-and-troubleshoot-your-service-mesh-5f9c68ea8ced?source=rss-726b1815a859------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f9c68ea8ced</guid>
            <category><![CDATA[twbloggersclub]]></category>
            <category><![CDATA[istio-service-mesh]]></category>
            <category><![CDATA[kiali]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[service-mesh]]></category>
            <dc:creator><![CDATA[Manoj Bhagwat]]></dc:creator>
            <pubDate>Sat, 05 Feb 2022 04:50:48 GMT</pubDate>
            <atom:updated>2022-02-05T04:50:48.916Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/636/0*FHiXP8bAAekhP0e5.png" /><figcaption>Image from Istio documentation</figcaption></figure><p>In this blog, we will talk about Kiali and its need in Service mesh setup.</p><h3><strong>What is Kiali ?.</strong></h3><p>Kiali is a management console for Istio service mesh. Kiali can be quickly installed as an Istio add-on or trusted as a part of your production environment.</p><h3><strong>Why do we need Kiali ?.</strong></h3><ol><li>Overall observability and management of Service Mesh Infrastructure.</li><li>Easy integration with products like <strong>Prometheus,Jaeger,Zipkin</strong> and <strong>Grafana</strong> etc.</li><li>Kiali helps in understanding the functionality of how <strong>mTLS</strong> is used in a typical complex Istio mesh environment.</li><li>Advanced Mesh Deployment and Multi-cluster support.</li></ol><h3><strong>Kiali Architecture :</strong></h3><p>Kiali is composed of two components: a back-end application running in the container application platform, and a user-facing front-end application. Kiali depends on external services and components provided by the container application platform and Istio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x4CHfZFPRxjZDzPKGZq2fg.png" /></figure><h3><strong>Implementation steps:</strong></h3><p>We are considering you already have the K8s cluster and Istio deployed in it. But in case you don&#39;t have you can set up one on any of your cloud providers on use Minikube on your local machine.</p><p>Once you have the above things in place next is you need to deploy Kiali in your environment. Kiali can be deployed using two approaches (Kiali Operator and Kaili Server).</p><p>In this blog, we will go ahead with the Kiali server method to deploy the same. We can deploy it using Kubectl YAML file or Helm charts.</p><pre>kubectl apply -f <a href="https://raw.githubusercontent.com/istio/istio/release-1.12/samples/addons/kiali.yaml">https://raw.githubusercontent.com/istio/istio/release-1.12/samples/addons/kiali.yaml</a>```</pre><p>We will recommend it to deploy using the Helm chart and the steps are as below:</p><pre>helm repo add kiali <a href="https://kiali.org/helm-charts">https://kiali.org/helm-charts</a></pre><pre>helm repo update</pre><pre>helm install \<br>    --namespace istio-system \<br>    kiali-server \<br>    kiali/kiali-server</pre><p>Once deployment is done you will see Kiali resources deployed in <strong>istio-system</strong> namespace. By default service type is Cluster IP so to access the dashboard, you will go ahead with the port forward method.</p><pre>kubectl port-forward svc/kiali 20001:20001 -n istio-system</pre><p>Access Kiali by visiting https://localhost:20001/ in your web browser. You can also expose it via Ingress controller or Cloud Loadbalancer (<a href="https://kiali.io/docs/installation/installation-guide/accessing-kiali/">https://kiali.io/docs/installation/installation-guide/accessing-kiali/</a>)</p><p>Now if you access the dashboard it will directly login and show you all the resources in the cluster since the default authentication mechanism is set as <strong>anonymous.</strong></p><p>You can also integrate Kiali with ODIC providers like (<strong>OKTA, KeyClock</strong>) for SSO. (<a href="https://kiali.io/docs/configuration/authentication/openid/">https://kiali.io/docs/configuration/authentication/openid/</a>)</p><p>All the metrics in Kiali dashboards are fetched via the Prometheus server and by default, it looks for the Prometheus server in the <strong>Istio-system namespace.</strong> If you don&#39;t have either install or you can pass the existing server URL as input to the helm chart. (<a href="https://kiali.io/docs/configuration/p8s-jaeger-grafana/">https://kiali.io/docs/configuration/p8s-jaeger-grafana/</a>)</p><p>The next step is to deploy a sample application and validate it in the Kiali console. We will deploy a book application that has 4 microservices.</p><ul><li><strong>The Product page:</strong> written in Python, this service displays the book page to the end-user. In doing so, it must display the book information by contacting the details service and the book reviews by contacting the reviews service.</li><li><strong>The Details Service:</strong> written in Ruby, it provides book information.</li><li><strong>The Reviews Service:</strong> written in Java, it provides book reviews. In doing so, it must contact the rating service to also get the star rating of the book.</li><li><strong>The Rating Service:</strong> written on NodeJS, it provides the star rating count for books.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RpraIUPrb-JR0bMsRkAlJA.png" /><figcaption>Book application architecture</figcaption></figure><p>The default Istio installation uses <a href="https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/#automatic-sidecar-injection">automatic sidecar injection</a>. Label the namespace that will host the application with istio-injection=enabled:</p><pre>kubectl label namespace default istio-injection=enabled</pre><pre>kubeclt apply -f <a href="https://raw.githubusercontent.com/istio/istio/release-1.12/samples/bookinfo/platform/kube/bookinfo.yaml">https://raw.githubusercontent.com/istio/istio/release-1.12/samples/bookinfo/platform/kube/bookinfo.yam</a></pre><p>The sample application is deployed now we will generate some traffic to the application using the curl command. I have another container up will use it to fire the curl request.</p><pre>curl productpage:9080/productpage</pre><p>Refresh the dashboard and you will be able to see the traffic coming to your application and how it is flowing to other microservices. Also, it will show you detailed metrics of incoming/outgoing metrics to your service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JbAyJd-q6W-TZSY4yRO_dg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6U2SpQ9X0cZeeMGp4j5l6w.png" /></figure><p>Hope this helps you in getting your Kiali dashboard up and running. Please reach out to me in case you need any help or have queries would be an absolute pleasure to discuss the same.</p><p>Reference links:</p><ul><li><a href="https://istio.io/latest/docs/setup/getting-started/">Getting Started</a></li><li><a href="https://kiali.io/docs/installation/installation-guide/install-with-helm/">Install via Helm</a></li><li><a href="https://www.magalix.com/blog/working-with-istio-track-your-services-with-kiali">Working With Istio: Track Your Services With Kiali</a></li><li><a href="https://github.com/kiali/helm-charts">GitHub - kiali/helm-charts: Helm Charts used to install Kiali resources.</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f9c68ea8ced" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/kiali-manage-visualize-validate-and-troubleshoot-your-service-mesh-5f9c68ea8ced">Kiali: Manage, visualize, validate and troubleshoot your Service mesh!</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Distributed Tracing in Microservices]]></title>
            <link>https://manoj-bhagwat60.medium.com/distributed-tracing-in-microservices-4c6fac8d941e?source=rss-726b1815a859------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c6fac8d941e</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[distributed-tracing]]></category>
            <category><![CDATA[jaegertracing]]></category>
            <category><![CDATA[twbloggersclub]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <dc:creator><![CDATA[Manoj Bhagwat]]></dc:creator>
            <pubDate>Sun, 16 Jan 2022 04:10:13 GMT</pubDate>
            <atom:updated>2022-01-16T04:10:13.540Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T-oJr1m30KhmseEQtSbq4A.png" /></figure><blockquote>This is my new blog on distributed tracing in microservices</blockquote><p>Let&#39;s first talk about the challenges that we are facing with modern microservices architecture.</p><h3>Common problems with Microservices.</h3><ol><li><strong>Loss of coherence: </strong>To fulfil a single end-user request is now broken across multiple processes, possibly written in multiple frameworks and implementation languages, it is much harder for team members to understand what exactly happened in the course of processing a request. Unlike a monolithic process, where we could gather the complete story of how a request was handled from a single process written in a single language, we no longer have an easy way of doing that in a microservices environment.</li><li><strong>Increased debugging and troubleshooting costs: T</strong>he act of tracking down and fixing sources of errors inside microservice architectures can be tremendously more expensive and time-consuming. In most cases failure data isn’t propagated in an immediately useful or clear manner inside microservices; instead of an immediately understandable stack trace, we have to work backwards from status codes and vague error messages propagated across the network.</li></ol><p>3. <strong>Data silos and cross-team communication: </strong>Given that one request has to. make multiple hops over the network and has to be handled by multiple. processes developed by independent teams, figuring out exactly where an. error occurred and whose responsibility it is to fix can become an exercise in. futility and frustration.</p><h3>What is distributed tracing ?.</h3><p><strong>Distributed Tracing is the process of tracking and analyzing what happens to a request (transaction) across all services it touches.</strong></p><p>What does “<strong>tracking</strong>” and “<strong>analyzing</strong>” mean?</p><ul><li>“<strong>Tracking</strong>” means generating the raw data in each service that says, “I did some processing for a request with a Trace ID abc123 — here&#39;s what I did, what other services I talked to, and how long each chunk of work took.&quot;</li><li>“<strong>Analyzing</strong>” means using any of the various searching, aggregation, visualization, and other analysis tools that help you make sense of the raw tracking data.</li></ul><h3>Why Does Your Business Need Distributed Tracing?</h3><p>Few of the critical questions that DT can answer quickly and easily in a distributed system architecture:</p><ul><li><strong>What services did a request pass through?</strong> Both for individual requests and for the distributed architecture as a whole (service maps).</li><li><strong>Where are the bottlenecks?</strong> How long did each hop take? Again, DT answers this for individual requests and helps point out general patterns and intermittent anomalies between services in aggregate.</li><li><strong>How much time is lost due to network lag</strong> during communication between services (as opposed to in-service work)?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0UB2eFeGMEdBShxDdFLlDA.png" /></figure><p><strong>Distributed tracing is extremely useful even for a single service where upstream and downstream haven’t implemented DT.</strong></p><h3>Key components of tracing system</h3><p>In order to discuss the core concepts for how distributed tracing works, we first need to define some common nomenclature and explain the anatomy of a trace. Lets take reference of the Google Dapper paper, so the main entities are Trace and Span. Note that distributed tracing has been around for a long time, so if you research DT you might find other tools and schemes that use different names. The concepts, however, are usually very similar:</p><ul><li><strong>Trace e</strong>xposes the execution path through a distributed system. Trace is composed of one or more spans.</li><li><strong>Span</strong> in the trace represents one microservice in the execution path.</li><li><strong>Request </strong>is how applications, microservices, and functions talk to one another.</li><li><strong>Root span </strong>is the first span in a trace.</li><li><strong>Child span </strong>is a subsequent span, which can be nested.</li></ul><h3>Selecting right tool for implementation</h3><p>Whatever tool you decide for implementation needs to have some basic features listed as below:</p><ul><li>In a distributed tracing scheme, there needs to be some kind of “<strong>span collector</strong>” that gathers the span data from the various services in a distributed systems architecture.</li><li>Another important component we need is good <strong>visualization UI . </strong>This will be used by developers for writing complex queries for debugging the issues.</li></ul><h3>Conclusion</h3><p>In this article, we first understood the challenges that we are facing in modern microservices and how DT system is helping us overcome all these problems.</p><p>Refrence links:</p><ul><li><a href="https://opentracing.io/docs/getting-started/">Getting Started</a></li><li><a href="https://www.jaegertracing.io/">Jaeger: open source, distributed tracing platform</a></li><li><a href="https://opencensus.io/">OpenCensus</a></li><li><a href="https://zipkin.io/">OpenZipkin · A distributed tracing system</a></li><li><a href="https://github.com/sourcegraph/appdash">GitHub - sourcegraph/appdash: Application tracing system for Go, based on Google&#39;s Dapper.</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c6fac8d941e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I passed the CKA and CKAD Exam in a month ..!!!]]></title>
            <link>https://medium.com/swlh/how-i-passed-the-cka-and-ckad-exam-in-a-month-4508b535bb65?source=rss-726b1815a859------2</link>
            <guid isPermaLink="false">https://medium.com/p/4508b535bb65</guid>
            <category><![CDATA[cka]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cncf]]></category>
            <category><![CDATA[ckad]]></category>
            <category><![CDATA[certification]]></category>
            <dc:creator><![CDATA[Manoj Bhagwat]]></dc:creator>
            <pubDate>Sun, 08 Aug 2021 07:35:01 GMT</pubDate>
            <atom:updated>2021-08-09T09:31:17.231Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I passed the CKA and CKAD Exam in a month ..!!!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*Y7NeXCCCd9bVzPyf.jpg" /></figure><p>I’m writing this post because, ever since I published my certification (CKA, CKAD) on Linkedin, I have been getting a massive number of messages from people who wanted tips for the examination. So I thought I would write up this medium article to share my learning path and experience.</p><p>To start with both these exam requires practical hands-on experience. CKA is a little tough as compared to CKAD. Mainly because it focuses on your ability to perform on a practical level rather than just asking a bunch of MCQ questions that would test your knowledge.</p><p>Will try to keep this blog simple/short and crisp.</p><h3>CKA preparation :</h3><ul><li>Mumshad’s course in Udemy <a href="https://www.udemy.com/course/certified-kubernetes-administrator-with-practice-tests/">https://www.udemy.com/course/certified-kubernetes-administrator-with-practice-tests/</a></li><li><a href="https://kodekloud.com/p/json-path-quiz">https://kodekloud.com/p/json-path-quiz</a></li><li><a href="https://github.com/StenlyTU/K8s-training-official">https://github.com/StenlyTU/K8s-training-official</a></li><li><a href="https://www.udemy.com/course/mastering-certified-kubernetes-application-developer/">https://www.udemy.com/course/mastering-certified-kubernetes-application-developer/</a> <strong><em>(No need to go through other content since it&#39;s already covered in Mumshad Course. Just focus on practice exam questions from this course. )</em></strong></li></ul><h3>CKAD preparation :</h3><ul><li><a href="https://www.udemy.com/course/certified-kubernetes-application-developer/">https://www.udemy.com/course/certified-kubernetes-application-developer/</a></li><li><a href="https://github.com/dgkanatsios/CKAD-exercises">https://github.com/dgkanatsios/CKAD-exercises</a></li><li><a href="https://github.com/reetasingh/CKAD-Bookmarks">https://github.com/reetasingh/CKAD-Bookmarks</a></li></ul><p>I would highly recommend setting up <a href="https://minikube.sigs.k8s.io/docs/start/"><strong>MiniKube</strong></a> on your local for practising and getting familiar with Kubectl commands.</p><h3>General Tips :</h3><ul><li>Solve Mock exams from the Mumshad course until you score 90+ every single attempt.</li><li>Have a strong hold on <strong>Kubectl</strong> imperative commands. Helps a lot during exam.</li><li>Bookmark all the necessary URLs from the Kubernetes docs site, since it will save time in searching things at the last moment.</li><li>From my personal experience, you really don&#39;t need to set those shortcut alias as you have enough time to attempt all the questions. Given you are a master in writing imperative commands.</li><li><strong>Kubectl cheatsheet</strong> that would help you right out with most questions in your exams. <a href="https://kubernetes.io/docs/reference/kubectl/cheatsheet/">https://kubernetes.io/docs/reference/kubectl/cheatsheet</a></li><li>If you are unsure of the spec or parameters of a YAML, always use</li></ul><pre>kubectl explain &lt;resource&gt;.&lt;key&gt;</pre><h4>Below are few articles that I would recommend before the Exam:</h4><ul><li><a href="https://www.runlevl4.com/kubernetes/patching-kubernetes-resources">Resize a PVC</a></li><li><a href="https://www.alibabacloud.com/blog/kubernetes-volume-basics-emptydir-and-persistentvolume_594834">Kubernetes Volume Basics: emptyDir and PersistentVolume</a></li><li><a href="https://medium.com/bb-tutorials-and-thoughts/kubernetes-learn-sidecar-container-pattern-6d8c21f873d">Sidecar containers</a></li><li><a href="https://matthewpalmer.net/kubernetes-app-developer/articles/kubernetes-ingress-guide-nginx-example.html">Ingress</a></li><li><a href="https://reuvenharrison.medium.com/an-introduction-to-kubernetes-network-policies-for-security-people-ba92dd4c809d">Network policy</a></li><li><a href="https://kubernetes.io/docs/concepts/cluster-administration/logging/">Logging Architecture</a></li><li><a href="https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/">NodeSelector</a></li><li><a href="https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/">Upgrading Kubeadm clusters</a></li><li><a href="https://discuss.kubernetes.io/t/etcd-backup-and-restore-management/11019">ETCD Backup/Restore</a></li><li>multi-container pod</li></ul><h3>Take it easy and All the very best!</h3><p>Don’t stress out much on the exam. True, it’s hard. Don’t panic. If you have practised enough you will pass with flying colours.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4508b535bb65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/how-i-passed-the-cka-and-ckad-exam-in-a-month-4508b535bb65">How I passed the CKA and CKAD Exam in a month ..!!!</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simplify Network Architecture with AWS Transit Gateway]]></title>
            <link>https://aws.plainenglish.io/simplifying-global-network-architectures-using-aws-transit-gateway-723b9b5890a4?source=rss-726b1815a859------2</link>
            <guid isPermaLink="false">https://medium.com/p/723b9b5890a4</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Manoj Bhagwat]]></dc:creator>
            <pubDate>Wed, 21 Apr 2021 06:38:50 GMT</pubDate>
            <atom:updated>2021-04-21T12:01:18.858Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In this blog will talk about AWS Transit Gateway and its implementation use cases.</em></p><p>AWS Transit Gateway provides a hub and spoke design for connecting VPCs and on-premises networks as a fully managed service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/0*p-OPV1rnpv8FGVF8.jpeg" /><figcaption>AWS Transit gateway design</figcaption></figure><p>Before we deep dive into Transit gateway, let&#39;s take a step back and first try to understand what networking challenges/issues it has eliminated.</p><h4><strong>Challenges:</strong></h4><ul><li>With increasing AWS footprint the number of point-to-point connections grows, resulting in a large mesh network that can be difficult, cumbersome, and costly to manage.</li><li>Also with <strong>Infosec/Compliance</strong> regulation pairing between prod and lower environment isn&#39;t allowed.</li><li>Connectivity options using (<strong>AWS Direct Connect, NAT Gateways, Internet Gateways,VPC Peering,AWS Managed VPN Connections</strong>) are strictly point-to-point, so the number of VPC-to-VPC connections grows quickly.</li><li>No single entry exit point for network.</li></ul><p>Use <a href="https://docs.aws.amazon.com/vpc/latest/tgw/what-is-transit-gateway.html"><strong>AWS Transit Gateway</strong></a> to build a hub-and-spoke network topology. You can connect your existing VPCs, data centers, remote offices, and remote gateways to a managed Transit Gateway, with full control over network routing and security.</p><h4><strong>Advantages:</strong></h4><ul><li>Simplify your overall network architecture.</li><li>Reduce operational overhead, and gain the ability to centrally manage crucial aspects of your external connectivity.</li><li>Consolidate your existing edge connectivity and route it through a single ingress/egress point.</li></ul><p>Let&#39;s consider a scenario where you have build/setup scalable hybrid network for an application that is spread across multiple VPCs/AWS accounts and also has requirement to connect on-premise datacenter. Using <strong>AWS Transit gateway</strong> and <a href="https://aws.amazon.com/ram/"><strong>Resource Access Manager</strong></a> combination will be able to achieve it with zero complexity.</p><p>Your network architecture diagram will look something similar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QmW9uV4HzdGjlITy.png" /><figcaption>Overview of Transit Gateway, Transit Gateway Attachments, and Transit Gateway Route Table</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/0*B9LnvAGXK3rVtmXQ.png" /><figcaption>Route Table for a subnet in VPC 1</figcaption></figure><p>In above diagram you can see that all incoming/outgoing network connections are managed via Transit Gateway and it acts are single point of communication. Also in case you have new AWS VPC/Account added you just need to share Transit gateway with new account / update route table and rest everything will work seamlessly.</p><h4><strong>Building Global Enterprise Network Architectures with AWS Transit Gateway</strong></h4><p>Organizations can now use AWS Transit Gateway to build out their IT networks without dealing with extensive network architecture planning and upgrades. They can take advantage of other networking and security services offered by AWS or <a href="https://aws.amazon.com/transit-gateway/partners/"><strong>AWS Partner Network (APN) Partners</strong></a> to deploy a global enterprise-grade network.</p><h4>Key AWS Transit Gateway features that can be leveraged to build out a global network architecture</h4><p><strong>AWS Transit Gateway Inter-Region Peering</strong>: Inter-Region peering enables traffic to traverse between AWS Transit Gateways over the AWS global backbone. Deploying a global network becomes easier using inter-region peering as AWS Transit Gateways and their VPC and VPN attachments can be interconnected</p><p><strong>AWS Transit Gateway Network Manager</strong>: It provides a centralized and consistent user experience. With a single interface, global IT networks can be viewed and monitored as AWS Transit Gateway Network Manager summarizes configuration and performance data from all AWS Transit Gateways and their attachments with other Amazon VPCs and on-premises locations.</p><p><strong>Route Analyzer</strong>:<strong> </strong>To monitoring near real-time network metrics, organizations can also identify potential causes of network disruptions by analyzing how traffic is routed between AWS Transit Gateways and their attached Amazon VPCs and on premises locations.</p><p><strong>Cross-account Support</strong>: You can share its AWS Transit Gateway with other AWS accounts so that they are free to attach their own Amazon VPCs or on-premises locations when business needs dictate.</p><p><strong>Security</strong>: AWS Transit Gateway operates on the AWS private network, thus not exposing an enterprise’s traffic on the public internet. This helps to decrease threat vectors such as distributed denial of service (DDoS) attacks and common exploits such as SQL injection and cross-site scripting.</p><h3>Conclusion</h3><p>Using Transit Gateway you can greatly simplify a network architecture in AWS. Before Transit Gateway, connectivity to multi-VPC environments was accomplished via Direct Connect Gateway or Transit VPC solutions which proved to be complex in nature. However, the use of Transit Gateway allows use cases as simple as inter-VPC connectivity to more complex scenarios involving connectivity to on-site networks.</p><p>Reference links :</p><ul><li><a href="https://aws.amazon.com/transit-gateway/pricing/">AWS Transit Gateway pricing - Amazon Web Services</a></li><li><a href="https://aws.amazon.com/transit-gateway/faqs/">AWS Transit Gateway FAQs - Amazon Web Services</a></li><li><a href="https://aws.amazon.com/blogs/networking-and-content-delivery/creating-a-single-internet-exit-point-from-multiple-vpcs-using-aws-transit-gateway/">Creating a single internet exit point from multiple VPCs Using AWS Transit Gateway | Amazon Web Services</a></li></ul><p><em>More content at </em><a href="https://plainenglish.io/"><strong><em>plainenglish.io</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=723b9b5890a4" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/simplifying-global-network-architectures-using-aws-transit-gateway-723b9b5890a4">Simplify Network Architecture with AWS Transit Gateway</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upgrade AWS EKS Cluster with Zero Downtime]]></title>
            <link>https://aws.plainenglish.io/guide-for-upgrading-aws-eks-cluster-with-zero-downtime-3cff3dcbdac?source=rss-726b1815a859------2</link>
            <guid isPermaLink="false">https://medium.com/p/3cff3dcbdac</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Manoj Bhagwat]]></dc:creator>
            <pubDate>Fri, 16 Apr 2021 04:32:48 GMT</pubDate>
            <atom:updated>2021-04-20T20:32:27.725Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*4l5H0iLq22Od-DUcEQhWew.png" /></figure><p>Amazon Elastic Kubernetes Service (Amazon EKS) is a fully managed Kubernetes service offering from AWS.It provides high availability and scalability for the Control Plane to run across multiple availability zones (thus eliminating a single point of failure situation).</p><p><strong><em>Note</em></strong><em>: New Kubernetes versions have introduced significant changes. Therefore, its recommend that you test the behavior of your applications against a new Kubernetes version in non-prod environment before you update your production clusters.</em></p><p>The upgrade process steps are as follow:</p><ul><li><strong>Upgrade EKS cluster version (1.18 to 1.19)</strong></li><li><strong>Update system component versions</strong></li><li><strong>Select a new AMI for worker nodes and launch node group</strong></li><li><strong>Drain pods from the old worker nodes</strong></li><li><strong>Cleanup</strong></li></ul><h4><strong>Step 1. Upgrade EKS cluster version</strong></h4><p>The first step before starting EKS upgrade is ensuring you are using version of <strong>kubectl</strong> that is at least as high as the Kubernetes version you wish to upgrade. Next step is to update your EKS Control plane via AWS CLI /Terraform or any other tool you are using for cluster management.</p><pre>aws eks update-cluster-version \<br> --region &lt;region-code&gt; \<br> --name &lt;my-cluster&gt; \<br> --kubernetes-version &lt;1.19&gt;</pre><p>It will take as long as <em>20</em> <em>minutes</em> for the EKS cluster’s version to be updated, and you can track its progress in the AWS console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M5njxwrieCwGHlrD.png" /></figure><h4><strong>Step 2. Update system component versions</strong></h4><p>After updating your cluster, its recommend that you update your add-ons to the versions listed in the following table for the new Kubernetes version that you’re updating to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ff76zoJT4mv1MAaMZ7uH2w.png" /></figure><p>For updating above components you can either use <strong>kubectl</strong> cmd or existing CI/CD pipelines.</p><p>Apart from above components if you have <a href="https://github.com/kubernetes/autoscaler/releases"><strong>cluster autoscaler</strong></a>, <strong>VPC Controller</strong>, <strong>metric-server </strong>etc its recommended to upgrade them to your cluster version.</p><h4><strong>Step 3. Select a new AMI for worker nodes and launch node group.</strong></h4><p>So approach would be to launch new worker node group and then terminate the old, but hold on with this approach you might end up having below issues and digging a hole for yourself.</p><p>While shutdown the old nodes, you would be taking down the running pods with it. What if the pods need to clean up for a graceful shutdown?</p><p>In case you shutdown all the nodes at the same time? You could have a brief outage while the pods are relaunched into the new nodes.</p><h4><strong>Step 4. Drain pods from the old worker nodes</strong></h4><p>What we want to achieve is gracefully migrate running pods to new worker nodes. The first step is to use the name of your nodes returned from <strong>kubectl get nodes</strong> to run <strong>kubectl taint nodes</strong> on each old node to prevent new pods from being scheduled on them:</p><pre>kubectl taint nodes &lt;node ip &gt; key=value:NoSchedule</pre><p>Now use kubectl drain which will gracefully handle pod eviction. In order to minimize downtime issues Kubernetes provide below features to handle same.</p><ul><li><a href="https://kubernetes.io/docs/concepts/workloads/pods/disruptions/#how-disruption-budgets-work">PodDisruptionBudgets</a></li><li><a href="https://kubernetes.io/docs/concepts/workloads/pods/pod/#termination-of-pods">Graceful termination</a></li><li><a href="https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/">Lifecycle hooks</a></li></ul><h4><strong>Step 5. Cleanup</strong></h4><p>Since all of your application pods are now rescheduled on new worker nodes and are running properly we can plan to terminate old worker node group vai AWS CLI/Terraform.</p><p>Reference links:</p><p><a href="https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html">https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html</a></p><p><a href="https://docs.aws.amazon.com/eks/latest/userguide/update-managed-node-group.html">https://docs.aws.amazon.com/eks/latest/userguide/update-managed-node-group.html</a></p><h3><strong>Conclusion</strong></h3><p>Now we’ve successfully upgraded your Kubernetes cluster on EKS to a new version of Kubernetes, updated the kube-system components to newer versions, and rotated out your worker nodes to also be on the new version of Kubernetes.</p><p>Feel free to share your ideas and I would love to learn about your strategies. Let’s discuss in the comments!</p><p><em>More content at </em><a href="https://plainenglish.io/"><strong><em>plainenglish.io</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cff3dcbdac" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/guide-for-upgrading-aws-eks-cluster-with-zero-downtime-3cff3dcbdac">Upgrade AWS EKS Cluster with Zero Downtime</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>