Skip to content
View gangadhar94r's full-sized avatar

Block or report gangadhar94r

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
gangadhar94r/README.md

Gangadhar

Platform Engineer. Cloud Engineer → SRE → Platform, which mostly means I've been on both ends of the pager and now spend my time building the things that stop it going off.

What I'm working on

internal-developer-platform — Self-service deployments. A developer writes twenty lines of YAML and gets a namespace with quotas and network policies, a deployment, autoscaling, a disruption budget, an Argo CD application and an SLO. Tiers instead of knobs, so the platform owns the replica counts and can change them everywhere at once. Generated output is committed, which makes the PR diff the review and lets CI catch drift.

k8s-slo-platform — SLO-based alerting for Kubernetes. Multi-window burn-rate alerts instead of CPU thresholds, OPA guardrails on every manifest, and a release gate that won't deploy into a service that's already spent its error budget. The alerting rules are unit tested with promtool, so the whole suite runs in CI without a cluster.

aws-platform-terraform — Terraform modules for a small AWS platform: VPC, hardened S3, ECS Fargate behind an ALB. Dev and prod are the same modules with different variables. 35 tests using Terraform's native test framework with mocked providers, plus tflint and checkov in CI.

message-announcer — An Android app that speaks who a message is from without reading it aloud or storing it. Kotlin and Compose. Ships with no INTERNET permission at all. The notification parsing is pure Kotlin so it's covered by 69 tests that run without a device.

How I like to work

Test the logic without the platform. Most of what's worth testing — parsing rules, alert thresholds, tier defaults, filtering decisions — doesn't need a cluster, an emulator or a cloud account, and pushing it somewhere it can be tested in seconds makes it far more likely to actually get tested.

Make the paved road the easiest road. A guardrail people route around is a guardrail that doesn't work.

Ask for the narrowest permission that does the job. Then check what actually shipped rather than what the source said.

Be precise about what's been verified versus what merely compiles. They're different claims and only one of them survives contact with production.

Tools

Terraform · AWS · Kubernetes · Prometheus · Argo CD · Docker · Python · Bash · Kotlin · GitHub Actions · OPA/Conftest


gangadhar94r@gmail.com

Pinned Loading

  1. k8s-slo-platform k8s-slo-platform Public

    SLO-based alerting for Kubernetes - burn rate alerts, policy guardrails and an error budget release gate, all unit tested without a cluster

    Open Policy Agent 1

  2. aws-platform-terraform aws-platform-terraform Public

    Tested, scanned Terraform for an AWS platform - VPC, hardened S3 and ECS Fargate, with 35 unit tests that run in CI without AWS credentials

    HCL 1

  3. message-announcer message-announcer Public

    Android app that speaks who a message is from - SMS, RCS and WhatsApp - without reading the message aloud

    Kotlin 1