Raees Qazi (RYQ's) | DevOps Engineer | Learner | Mentor | Creator

Raees Qazi | DevOps Engineer | Learner | Mentor | Creator | CEO-Briller Technologies Today, I’m starting a new hands-on series about Prometheus and Grafana .  This will be a detailed, practical project divided into 4–5 blogs , where we’ll go step by step from setup to complete monitoring. 🧠 What This Project Is About As shown in the project diagram (above), here’s the overall workflow we’ll follow: Create an EC2 instance on AWS. Install Docker and run it on that instance. Deploy a sample application inside a Docker container. Use cAdvisor to collect metrics (like CPU, memory, and container stats). Forward metrics to Prometheus , which stores and organizes the data. Install Node Exporter to collect system-level metrics from the EC2 instance and Forward metrics to Prometheus Finally, use Grafana to visualize all these metrics on a beautiful dashboard. This setup helps us easily monitor: How well our app is running, The system performance, Incoming and outgoing traffic, An...

  By Raees Qazi | DevOps Engineer | Learner | Mentor | Creator Today, I’m excited to share that I’ve finally started working with  Terraform  — a powerful tool in the DevOps world. But before we dive into Terraform itself, let’s first understand how a typical company runs and how infrastructure plays a key role in its operations. Press enter or click to view image in full size 🏢 How Does a Company Operate? (Company Hierarchy) To understand why we need tools like Terraform, we must first understand the hierarchy and flow of work in an IT company: Business Every company runs on business. If the business is doing well, employees get paid, and operations continue smoothly. Business Analyst This team finds clients and identifies opportunities to expand the business. Solution Architect / Technical Team Lead Once a client is onboarded, the architect or team lead designs the actual solution or product. Procurement At this stage, the company arranges the resources: Hiring teams l...

  As a DevOps engineer, managing user access in Kubernetes (K8s) is a critical task. Today, let’s talk about   RBAC , which stands for   Role-Based Access Control . It helps us control   who can do what   in a Kubernetes cluster. 🎯 Why RBAC is Important? Let’s say your  Dev team  needs access to the cluster. But we  don’t want to give them full admin access . For example, they might need permission to  read and write deployments and services , but  not delete or execute  critical commands. This is where  RBAC  comes into play. Press enter or click to view image in full size 🧱 RBAC Basic Structure RBAC in Kubernetes works just like  AWS IAM : In  AWS , you: Create a  user Attach a  policy  (which defines what the user can do) In  Kubernetes , you: Create a  Role  (defines permissions) Create a  RoleBinding  (assigns Role to a user or service account) 🔧 Step-by-Step: How R...