Skip to content
View rodrigorfk's full-sized avatar
  • Haarlem, Noord-Holland, The Netherlands
  • 🔴 Hot News: rodrigorfk - ประเด็นร้อน in/kuntzer

Block or report rodrigorfk

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
rodrigorfk/README.md

Hi, I'm Rodrigo 👋

Senior Staff Site Reliability Engineer at Miro
Platform engineering · Kubernetes · AWS · Haarlem, the Netherlands

LinkedIn Speaker profile Medium CKA AWS

I am a Software Engineer turned Site Reliability Engineer, with 21 years in the field. I started on Java and the JVM, building platforms that need high throughput, low latency and reliability. Caring about how that software behaved in production pulled me towards DevOps, and platform engineering has been my main focus ever since.

At Miro I am a technical leader for the Cloud Compute platform on AWS: EKS, EC2, autoscaling and scheduling. I like the problems that sit between the platform and the application: a scheduler and an autoscaler that disagree, a health check that stays green while traffic fails, a latency regression that turns out to be where an instance landed.

When I find a bug in a tool we depend on, I try to fix it upstream. 🛠️


🧭 What I'm working on

  • ☸️ The compute platform behind Miro: EKS fleets, Karpenter, Graviton and Spot, all in infrastructure code
  • 🌐 A simpler edge for Miro: one Envoy-based gateway, tested against a production-shaped replica first
  • 📦 Compute for AI agent sandboxes: Kata microVMs, fast starts with lazy image pulling, egress enforced on the node
  • 🗣️ Sharing what we learn, on stage and upstream

🏆 Highlights at Miro

Moving Miro onto Kubernetes
  • Led the technical validation that moved Miro's board and table servers, the core of the product, from EC2 onto Kubernetes, with load tests and a performance sign-off before each step
  • Proved the Java monolith could run on Kubernetes and inside the service mesh, the groundwork for that move
  • Root-caused a latency regression after the move to EC2 placement relative to the cache tier, and won back 14-25% of median latency
  • Moved the miro.com website from EC2 web servers to Kubernetes behind a new edge router, path by path in five phases
  • Co-led bringing the Kong API gateway and the Istio service mesh to production on EKS
Platform engineering and infrastructure as code
  • Built the environment automation golden path: the first Miro environment created entirely from code, later adopted as the standard way to write infrastructure code
  • Delivered the infrastructure for Miro's Australian data residency environments in under two months
  • Led the GitLab to GitHub migration of the infrastructure and Kubernetes repositories, history included
  • Created the Helm chart and release path Miro's microservices use to deploy to EKS
  • Built a production-shaped replica of Miro's edge with a vcluster vending machine, to test gateway candidates before migrating anything
Efficiency and cost
  • Introduced Karpenter with Spot, cutting a non-production cluster's daily compute bill by about two thirds
  • Made Spot safe for single-replica workloads and pushed clusters to near-full allocation, with about 43% fewer nodes in one region
  • Cut container registry costs by 85% with same-region image pulls and lifecycle policies that know what is deployed
  • Brought AWS Graviton (arm64) to the platform, from benchmark to production node pools
  • Featured in AWS's case study on how Miro runs on Amazon EKS: Miro drives hypergrowth with Amazon EKS
Reliability and deep debugging
  • Proved the production EKS cluster could scale about 8x, and removed the bottlenecks found on the way
  • Found and fixed a five-year-old Calico Typha bug behind a CI outage, credited in CVE-2023-41378
  • Rebuilt the board PDF and SVG export service around headless Chrome workers; large exports got about 7x faster
  • Made a silent pod-network failure in the VPC CNI policy agent visible, with alerting and runbooks

🗓️ Timeline

timeline
    title My path so far
    2005 : Started building software on Java and the JVM
    2017 : Running Kubernetes in production for Brazil's largest online grocery
         : Spoke at TDC Porto Alegre
    2021 : Joined Miro's first centralized SRE team
         : miro.com moves to Kubernetes
    2022 : Kong and Istio in production
         : Karpenter and Spot
    2023 : CVE-2023-41378 fixed upstream
         : Karpenter article on Miro Engineering
    2024 : Staff Site Reliability Engineer
         : AWS Cloud Day Prague and KCD Porto
    2025 : Senior Staff Site Reliability Engineer
         : KubeCon EU London and AWS Summit Poland
    2026 : KubeCon EU and KyvernoCon in Amsterdam
         : Edge consolidation and AI agent sandboxes
Loading
Roles at Miro
Since Role Team
2025 Senior Staff Site Reliability Engineer Platform Engineering stream
Apr 2024 Staff Site Reliability Engineer Infrastructure
2023 Site Reliability Engineer Compute
2021 Site Reliability Engineer SRE Cloud
Feb 2021 Site Reliability Engineer Centralized SRE team

🎤 Talks and writing

When Where What Links
Mar 2026 KubeCon + CloudNativeCon Europe, Amsterdam Cutting Metrics Traffic, Cutting Costs: The AZ-Aware Observability Blueprint 🎥 video · 💻 demo · 📅 schedule
Mar 2026 KyvernoCon Europe, Amsterdam Kyverno Mutating Policies: Shifting Platform Logic Into the Control Plane 💻 demo · 📅 schedule
Oct 2025 Kubernetes Podcast (NL), episode 112 Stateful on Kubernetes: Lessons from Miro's Real-Time Platform 🎧 listen
May 2025 AWS Summit Poland Maximizing Kubernetes Efficiency with Karpenter: A Miro Case Study
Apr 2025 KubeCon + CloudNativeCon Europe, London Stateful Connections in Kubernetes: The Scaling Secrets Nobody Talks About 🎥 video · 📅 schedule
Oct 2024 AWS Cloud Day Prague Maximizing Kubernetes Efficiency with Karpenter: A Miro Case Study
Sep 2024 KCD Porto Kyverno mutating policies 💻 demo
Sep 2024 Life at Miro / Medium Automating Kubernetes Workflows with Kyverno's Mutating Webhooks 📝 read
Sep 2023 Miro Engineering Optimizing Kubernetes scalability and cost-efficiency with Karpenter 📝 read
Nov 2017 TDC Porto Alegre Kubernetes and immutable infrastructure with Ansible, Packer and AWS 📅 track
2017 Talk (pt-BR) Kubernetes: Orchestrating Brazil's largest online grocery 🖼️ slides

🌱 Open source

Fixes and features I got merged upstream while running these tools at scale:

Project What PRs
Calico Timeout for the Typha TLS handshake, the fix behind CVE-2023-41378 #7909
Karpenter Consider pending pods with preferred node affinity #2182
Argo CD Faster short ref resolution in the repo-server for large monorepos #26456
Kyverno Metrics controls, MutatingPolicy user info, and more 6 merged
Terragrunt Symlinked module discovery, skip merging, dependency outputs from state 4 merged
External Secrets Vault mTLS, PushSecret improvements 3 merged
cert-manager Secrets informer race fix, Vault mTLS 2 merged
Trivy Operator Private registry auth and image mirroring fixes 2 merged
More: KEDA, vcluster, helmfile, Grafana, podinfo and others

KEDA · vcluster · helmfile · Grafana · podinfo · kms-issuer · terraform-aws-msk-apache-kafka-cluster · pipeline-aws-plugin

🧰 Tools I work with

Kubernetes Amazon EKS AWS Karpenter Terraform Terragrunt Istio Envoy Kyverno Argo CD Helm Prometheus Grafana VictoriaMetrics GitHub Actions Go Java Linux


Opinions here are my own. Happy to talk about platforms, Kubernetes and the bugs in between.

Pinned Loading

  1. gruntwork-io/terragrunt gruntwork-io/terragrunt Public

    Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu/Terraform to scale.

    Go 9.9k 1.2k

  2. kedacore/keda kedacore/keda Public

    KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes

    Go 10.7k 1.6k

  3. projectcalico/calico projectcalico/calico Public

    Cloud native networking and network security

    Go 7.4k 1.6k

  4. kyverno/kyverno kyverno/kyverno Public

    Unified Policy as Code

    Go 8.3k 1.7k

  5. external-secrets/external-secrets external-secrets/external-secrets Public

    External Secrets Operator reads information from a third-party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.

    Go 6.9k 1.5k