Junaid Khokhar

Hosting a Dynamic Web Application on AWS Cloud Platform using Terraform Infrastructure as a Code by: - Creating IAM User with programmatic access to manage AWS resources, - Creating VPC with public and private subnets across at least two availability zones for redundancy. - Creating NAT Gateway to allow instances in private subnets to access the internet securely. - Creating Security Groups to control the inbound and outbound traffic to the EC2 instances and other services, - Creating MySQL RDS Database to store structured data for the application, - Creating Application Load Balancer to distribute incoming web traffic across multiple EC2 instances in different availability zones, ensuring high availability, - Creating SNS Topic to receive notifications about various events and operations, - Creating Auto Scaling Group to dynamically create and terminate EC2 instances based on load, ensuring the application is scalable and resilient. - Creating Route 53 Record to manage DNS routing for the domain, pointing it to the load balancer.

1

Improved CI/CD pipeline for going e2e test for Ksctl It is optimized for smaller vms without compromising on build speeds and platforms for docker build #devops #cicd

31

Earlier in the year I wrote a blog called “Running the Apache Camel™ HTTP Kafka Source Connector on Instaclustr Managed Apache Kafka®”. But there are a lot of Apache Camel Kafka Connectors available, and I wondered how to “get your Camels in a row”? That is, understand what permutations of Apache Camel Kafka connectors are possible and form a useful “camel train”!  Which technologies are supported by Apache Camel Kafka source connectors only, sink connectors only, or ideally, both source and sink connectors? I was also curious to see which of Instaclustr’s Managed Services have matching Apache Camel Kafka connectors - find out more in the latest blog: https://lnkd.in/gUF_NBS2 #apachekafka #apachecamel #kafkaconnectors

19

🔩 How to monitor AWS WAF logging centrally in near real-time through using Amazon Managed Grafana AWS Blog 🔗 https://lnkd.in/dDRpRwK8 #aws #awscommunity #awscommunitybuilders

34

My latest guide on Automating Longhorn Deployment During an RKE2 Cluster Installation! This step-by-step document simplifies the process of setting up Longhorn as a distributed block storage system during the installation of an RKE2 cluster. Whether you're new to Kubernetes or looking to streamline your deployment process, this guide provides clear instructions and practical tips to ensure a smooth setup. #Kubernetes #Rancher #RKE2 #Longhorn #DevOps #CloudComputing #StorageSolutions #TechGuide #Automation #OpenSource

8

Keptn is an open-source control plane for continuous delivery and automated operations. It is designed to help developers and SRE (Site Reliability Engineering) teams implement and manage continuous delivery pipelines, automate deployments, and perform automated operations tasks in cloud-native environments. ### Key Features and Components of Keptn: 1. Continuous Delivery (CD):   Keptn automates the end-to-end continuous delivery process, including building, testing, deploying, and promoting applications across different environments (e.g., development, staging, production). 2. Cloud-Native Support:   Keptn is designed for cloud-native environments and supports Kubernetes as the primary orchestration platform. It integrates seamlessly with popular cloud services and tools. 3. Event-Driven Automation:   Keptn uses an event-driven architecture to trigger and orchestrate delivery and operations tasks based on predefined events and conditions (e.g., code commits, performance thresholds). 4. GitOps Integration:   Keptn supports GitOps principles by managing application configurations and delivery workflows through Git repositories, enabling version control and traceability. 5. Multi-Stage Pipelines:   Keptn supports multi-stage delivery pipelines, allowing teams to define sequential or parallel stages for building, testing, and deploying applications. 6. Automated Operations:   Beyond deployment automation, Keptn includes features for automated operations, such as auto-remediation of incidents, performance monitoring, and scalability management. 7. Integration with Observability Tools:   Keptn integrates with observability tools like Prometheus, Grafana, and Dynatrace for monitoring application and infrastructure metrics, enabling automatic scaling and performance optimizations. ### Components of Keptn: - Bridge: A web-based user interface for viewing and managing Keptn projects, stages, services, and deployments. - Control Plane (APIs): The core control plane of Keptn responsible for managing projects, services, and orchestration of delivery and operations tasks. - CLI (Command-Line Interface): A CLI tool for interacting with Keptn, creating projects, triggering deployments, and monitoring pipeline execution. - Service Templates: Pre-defined templates for different types of services (e.g., microservices, web applications) that can be used to bootstrap new projects. - Automation Engine: The engine that executes delivery and operations workflows based on event triggers and defined configurations. ### Use Cases for Keptn: - Cloud-Native Application Delivery: Automate the deployment and lifecycle management of cloud-native applications across Kubernetes clusters. - Continuous Delivery Pipelines: read more : https://lnkd.in/da8GCebG #devpos #platform #linux #k8s #k3s #kubernetes #keptn #security #control #control_plane https://t.me/unixmens

4

How does kubelet fetch images from private ECR repos on EKS (v1.26+)? Can we stop for a second to appreciate how come we don't specify any credentials/secrets (imagePullSecrets) whatsoever and yet we can launch Pods in our EKS cluster without any problems? how does this magic work? Let's break it down. kubelet doesn't know at the time of compilation on which cluster it is provisioned, so just like the old adage from David A. Wheeler, it shells it to an external plugin. The kubelet credential provider plugin has become GA in Kubernetes v1.26. And to validate what I just said, if you poke at how kubelet is launched on EKS worker nodes, you will see 2 interesting parameters: --image-credential-provider-config /etc/eks/image-credential-provider/config.json --image-credential-provider-bin-dir /etc/eks/image-credential-provider But that's just only half of the story. So how does the EKS credential provider securely fetch the credentials? Let's see how it works end to end: 1. When a Pod is scheduled to run on a Pod, kubelet looks for a matching credentials helper 2. A match is found and kubelet executes the ECR credentials helper 3. The ecr-credential-provider uses the AWS SDK (aws-sdk-go, under the hood) to obtain AWS auth token, which in turn contacts the link-local IMDSv2 to actually obtain that token 4. It uses the obtained AWS token to obtain yet another auth token from ECR using GetAuthorizationToken 5. It returns a CredentialProviderResponse JSON (on stdout) to kubelet with a Username and Password 6. The kubelet uses the credentials from the CredentialProviderResponse document and passes it to its registry client 7. The image is fetched to the node To me it's mind boggling how so many moving pieces are perfectly orchestrated together at a stroke of a pen (with either eksctl or CF or TF). In the next post we'll break down how similarly Pods and workload identities work in concert to access container registries without requiring any secrets whatsoever. Resources: https://lnkd.in/du7Ks--q https://lnkd.in/dhZgZGz4 #eks #cloudsecurity #kubernetes #kubernetessecurity #cloudnativesecurity #sigauth

33

2 Comments

🚀 Day 48 of #90DaysOfDevOpsChallenge - Exploring ECS ☁️ 🔍 Key Learning: - ECS (Elastic Container Service) is a fully-managed container orchestration service by AWS. - Supports Docker containers on EC2 instances or AWS-managed infrastructure. - Integrates with AWS services like Elastic Load Balancing, Auto Scaling, and Amazon VPC. - Offers support for Docker Compose and Kubernetes. 🛠️ Task of the Day: - Set up ECS by deploying Nginx on ECS. 📌 Steps: - Open AWS Management Console and search for ECS. - Create a new cluster with AWS Fargate. - Configure task definition and create an IAM role. - Deploy Nginx container and create a service. - Access Nginx using the public IP. 🎉 Exciting Moments: - Successfully deployed Nginx on ECS and accessed it via the public IP! 📝 Blog Updates: - Check out the detailed steps and screenshots on my blog post. - [https://lnkd.in/gzz6fF2Q] 💬 Join the Conversation: - Have you tried ECS for your containerized applications? Share your experiences and tips in the comments! #DevOps #AWS #ECS #CloudComputing #LearningJourney #TechBlog TrainWithShubham DevOps Parthu

9

Factors that Affect the Salaries of DevOps Engineers The average median salary of DevOps engineers depends on various factors, such as the country and its currency's weight, the types of certifications and qualifications the professional has acquired, the geographical location, the type of industry, the company chosen, and the years of professional experience. Let's find out these factors in detail: Years of Experience The number of years of experience of a DevOps engineer in the industry is of utmost importance when deciding their salaries. The more the experience is, the higher the annual salary packages the professionals can expect. Specialization and Skill Sets The biggest quality of a DevOps engineer is their diverse skill sets; the more skills they acquire, the higher pay scale they are offered. The DevOps professionals are specialized in working with advanced technologies and tools, such as Docker, Kubernetes, Git, Ansible, Jenkins, and many others. DevOps engineers also upgrade their skills and knowledge through specialized certifications that help them gain expertise in leading cloud platforms like AWS, Google Cloud, and Microsoft Azure services. The Chosen Industry The salary of DevOps engineers also depends on the chosen industry. DevOps professionals are frequently hired in software development, IT, healthcare, finance, entertainment, manufacturing, and several other industries. Therefore, depending on the type of industry and the importance of DevOps in the operations of the chosen industry, the salaries are decided. Type and Size of the Company The type of company chosen and its size matter the most in deciding the salaries of DevOps engineers. Leading companies like Google, Microsoft, Tata Consultancy Services, Accenture, Deloitte, Oracle, and HCL Tech offer DevOps professionals the highest salary packages. Similarly, smaller companies have much lower offers. Geographical Location The geographical location is another important factor that impacts the salary. The average annual salary of DevOps engineers in London is much different from that of those hired in California. Similarly, within a country, DevOps salaries also vary depending on the state, how developed it is, and the type of opportunities it offers for technical professionals. https://lnkd.in/gCUGaFwq

1

Terraform allows us to quickly deploy, update and destroy cloud services. The project called for us to build a Terraform file that can deploy an AWS EC2 instance that deploys Jenkins. https://lnkd.in/gQEbNnqz In this project we: ✅Created a Terraform file that did everything below using Cloud9 IDE ✅Create an EC2 instance with the default VPC and associated a new security group ✅Installed Jenkins on the instance with a user-data file ✅Created a S3 bucket that blocks all public access ✅Pushed the code to GitHub ✅Checked our work, used resources responsibly and documented❗️❗️ Thank you to our coaches for your support and guidance Broadus Palmer, Troy Ingram, Bryant Witcher, Janita Green Williamson, Charles Woodruff, Zaire Ali, Ifeanyi Otuonye, MBA, Carl Hayes, Katoria Henry, Nafis Ansari and Daniel Rothamel. 🙏 👊 #careertransition #cloudcomputing #alwayslearning

17

assume, one of the first #Terraform providers to utilize the new capabilities of Terraform 1.8: Terraform Provider Functions. Learn more about it here: https://lnkd.in/dSAUnyBv Finally, we can put an end to the abuse of modules for such function calls.

6

In this video you will learn about variables in Terraform and the variable precedence in Terraform. There are different variable types that you can declare in Terraform and pass values to variables in multiple ways, hence there is a precedence order. https://lnkd.in/gxt56Y4d #terraform #cloudcomputing #devops

32

Vagrant Or Terraform vs Foreman : Vagrant and Terraform are both projects from HashiCorp. Vagrant is a tool focused for managing development environments and Terraform is a tool for building infrastructure. Terraform can describe complex sets of infrastructure that exist locally or remotely. It is focused on building and changing that infrastructure over time. The minimal aspects of virtual machine lifecycle can be reproduced in Terraform, sometimes leading to confusion with Vagrant. Vagrant provides a number of higher level features that Terraform doesn't. Synced folders, automatic networking, HTTP tunneling, and more are features provided by Vagrant to ease development environment usage. Because Terraform is focused on infrastructure management and not development environments, these features are out of scope for that project. The primary usage of Terraform is for managing remote resources in cloud providers such as AWS. Terraform is designed to be able to manage extremely large infrastructures that span multiple cloud providers. Vagrant is designed primarily for local development environments that use only a handful of virtual machines at most. Vagrant is for development environments. Terraform is for more general infrastructure management. In terms of why Vagrant might be considered better than Terraform: -Simplicity for Development Environments**: Vagrant is simpler to set up and use for creating and managing development environments locally, which can be beneficial for individual developers or small teams working on local projects. -Ease of Use : Vagrant has a more straightforward learning curve compared to Terraform, making it easier for developers who are new to infrastructure as code concepts. Quick Setup : Vagrant allows developers to quickly spin up virtual machines with predefined configurations, making it faster to start development work compared to setting up cloud resources with Terraform. -Focused Purpose : Vagrant focuses on creating reproducible local development environments specifically, while Terraform is designed for managing cloud infrastructure, so Vagrant might be seen as a better tool for its intended purpose. However, it's important to note that the choice between Vagrant and Terraform depends on the specific use case and requirements of the project. Terraform is better suited for managing cloud resources and infrastructure in production environments, whereas Vagrant excels at creating consistent development environments locally. Both tools have their strengths and are valuable in different contexts. more info : https://lnkd.in/dJ-WEUWi

3

How to Perform Simple String Concatenation in Terraform https://lnkd.in/eDNmdrNg #HashiCorp #join #string #stringconcatenation #Terraform

3

How to Perform Simple String Concatenation in Terraform https://lnkd.in/eDNmdrNg #HashiCorp #join #string #stringconcatenation #Terraform

4

🚀 𝐓𝐢𝐭𝐥𝐞:  Ensuring Reliability with Static Pods in Kubernetes 🚀 🔍 𝐈𝐬𝐬𝐮𝐞: In certain scenarios, critical services need to be tightly coupled with specific nodes. Traditional pod management methods in Kubernetes might not guarantee the deployment and stability of these essential services directly on designated nodes, which can lead to operational inefficiencies and potential service gaps. 💡𝐅𝐢𝐱: The solution is Static Pods! 🎯 Static Pods are managed directly by the kubelet on a specific node, bypassing the Kubernetes API server. This ensures that the pods are always running on the desired nodes, providing a robust solution for deploying essential, node-specific services. 📋 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: To illustrate, you can define a Pod definition yaml file and to deploy this as a Static Pod, save the YAML file on the node at a specified directory (e.g., /etc/kubernetes/manifests/), (This path can be checked by the config file of kublet which is at location /var/lib/kublet/config.yaml with a line stating the path to static pod) The kubelet will automatically detect and start the Static Pod, ensuring it runs directly on that node. 📂 🎓 𝐋𝐞𝐚𝐫𝐧𝐢𝐧𝐠s: Implementing Static Pods in your Kubernetes clusters provides several key advantages: 1. Node-specific Deployment: Ensure that critical services run on specific nodes without relying on the Kubernetes scheduler. 2. High Availability: Direct management by the kubelet ensures that the pods are always running, even if the API server is down. 3. To identify which is a static pod , check the suffix of the pod name it is appended with the nodename , check the snippet where some pods like "etcd-my-node-1" is static pod as it has node-1 appended to the name and the other pods without a node name suffix are managed by the Kubernetes scheduler. By leveraging Static Pods, you can achieve higher reliability and control for node-specific deployments, ensuring that your critical services are always up and running. #Kubernetes #DevOps #CloudComputing #StaticPods #K8s #TechTips #Infrastructure #Scalability #Reliability 🚀🔧

20

2 Comments

📦 Kubernetes Deployments-Your Gateway to Smooth Nginx Scaling on AWS! 🚀 In the world of modern application delivery, Kubernetes has emerged as the de facto standard for orchestrating containerized workloads. While Pods are the building blocks, Deployments take center stage, offering a robust and efficient way to manage and scale your applications. 💻 Why Kubernetes Deployments? 🤔 High Availability 🔁 Rolling Updates (Zero Downtime) 🆙 Easy Rollbacks ⏪ Seamless Scaling ⬆️⬇️ Self-Healing Capabilities 🚑 🌐🚀Deploying Nginx on AWS with Kubernetes Deployments 🌐🚀 🔁Created a Deployment with 3 replicas for High Availability 🔁Exposed the Nginx service with an AWS Load Balancer 🔁Scaled the Deployment to 5 replicas with a single command 🔁Performed a rolling update to a new Nginx version (Zero Downtime) Kubernetes Deployments unlock the true power of containerized applications, ensuring high availability, seamless updates, and effortless scaling. Embrace this game-changer and elevate your application delivery game! 🎉 If you found this post helpful, please show your support by giving it a round of applause 👏👏👏. Your engagement means a lot and helps other DevOps and Cloud Engineers discover this content. Thank you for your support! 😀 #KubernetesDeployments #ContainerOrchestration #CloudNative #AWSCloud #NginxWebServer #DevOps #CloudComputing #TechBlog #KubernetesTutorial #AWSDeployment #ContainerizedApps #ApplicationDelivery #DevOpsBlog #TechWriting #NginxDeployment #WebServerDeployment #KubernetesNginx #ContainerizedNginx #AWSNginx #CloudNginxDeployment #NginxOnAWS #WebServerScaling #LoadBalancingNginx #NginxHighAvailability #NginxRollingUpdates #NginxRollbacks #NginxAutoHealing #NginxDeploymentTutorial #KubernetesNginxTutorial #AWSNginxTutorial #DevOpsBlog #CloudNativeBlog #ContainerBlog #TechBlogger #KubernetesBlogs #AWSBlogs #NginxBlogs  #90daysofdevopschallenge #90daysofdevops #CloudInfrastructure #TechInnovation #LinkedInPost #linkedincommunity #linkedinconnections #devopscommunity #devopsskills #devopsengineer

6

How to develop your first Kubernetes Validating Admission Controller I created a hello world Golang project for Kubernetes Validating Admission Controllers that denies creating Pods with name equals to pod-with-an-invalid-name. I did this as both an educational exercise and as means to debug and troubleshoot issues related to validating webhooks in Kubernetes, without having to debug complex production-grade code. To get started do the following: git clone https://lnkd.in/d_-4b7nM cd admission-controller task build package gen-certs task deploy Then try to deploy a Pod that is not allowed by the webhook and it should fail: kubectl apply -f examples/pod-with-an-invalid-name.yaml To uninstall, run: task uninstall For more information: https://lnkd.in/dD8iSX-C Please let me know your thoughts in the comments below. #kubernetes #admissioncontrollers #go #golang

49

3 Comments