Terraform with AI: Build AWS Infra (Cursor + MCP)Understand how AI-assisted infrastructure workflows can reduce operational friction and improve Terraform productivity.6 min read·devopsbysanjay.hashnode.devMay 23
K3s vs Kubernetes (K8s): Performance, Architecture, Use Cases and When to Choose Each K3s vs Kubernetes (K8s) comparison with architecture, performance, and use cases. Find the right choice for DevOps, edge, and production.4 min read·devopsbysanjay.hashnode.devMay 22
Jenkins or GitHub Actions? Deciding the Right CI/CD Tool for Your Workflow Compare Jenkins and GitHub Actions from an operational perspective and understand CI/CD tradeoffs around flexibility and maintenance.13 min read·devopsbysanjay.hashnode.devMay 21
Managing Terraform State Locking in S3 Without DynamoDBLearn when to use Terraform S3 locking without DynamoDB and when DynamoDB is still required for production. Includes architecture, risks, and best practices.5 min read·devopsbysanjay.hashnode.devMay 20
How to Avoid GitHub Token Rate Limiting Issues | Complete Guide for DevOps TeamsFix GitHub API rate limit errors in CI/CD pipelines. Learn how to avoid 403 errors using tokens, caching, and GitHub Apps with real DevOps solutions. Introduction Your CI/CD pipeline was working fine until suddenly every build started failing with a GitHub API 403 error. I faced this exact issue during a production deployment. Everything looked fine—no code changes, no infrastructure issues—but pipelines kept failing. At first, we thought it was a bug in the pipeline, but nothing pointed to the actual issue. After debugging for hours, it became clear that the problem was not the code, but GitHub API rate limiting. If you are facing GitHub API rate limit exceeded errors in CI/CD pipelines, this guide will help you fix them effectively. Quick Fix (TL;DR for busy DevOps engineers): Use authenticated tokens, reduce unnecessary API calls, implement caching, and switch to GitHub Apps for scalable systems. What is GitHub API Rate Limiting? GitHub API rate limiting restricts how many API requests you can make within a specific time window. This ensures fair usage and prevents abuse. In real-world DevOps workflows, this limit can quickly become a bottleneck. Why GitHub API Rate Limit Errors Happen in CI/CD In most DevOps setups, pipelines frequently interact with GitHub APIs: Fetching repositories Triggering workflows Checking build statuses Managing pull requests Common causes include: Frequent API polling Multiple services making requests at the same time Unauthenticated API usage This is where GitHub API rate limit exceeded errors typically occur. GitHub API Rate Limits Explained (Token Types) Unauthenticated Requests: 60 requests per hour Personal Access Token (PAT): 5000 requests per hour GitHub Actions Token: approximately 1000 requests per hour Using authenticated requests significantly increases your available limits. Token Management Strategies Use GitHub Apps Instead of Personal Tokens GitHub Apps provide higher rate limits and better security.4 min read·devopsbysanjay.hashnode.devMay 19