tunasakar

Tuna Sakar

  • Cloud-Native Architecture
  • Enterprise AI
  • API-First
  • SRE
  • Event-Driven Systems
  • Automation
  • DevOps
  • Observability
  • DevEx
kubectl -n tuna get pods 

      

    


    
    
      
    
  1. 
      
     cat about.md
    
      
    I’m Tuna — a cloud-native architect who designs API-first, event-driven systems and the SRE, observability, and DevEx plumbing that keeps them running — on a lifelong mission to automate anything that moves (and most things that don’t). When I’m not deep in the CI/CD matrix, smoothing out Kubernetes tantrums, or convincing enterprise AI to behave in production, you’ll probably find me sipping çay and whispering sweet nothings to my .bashrc, while refactoring 10-year-old shell scripts buried somewhere in /etc/.
    
    
    2. 
      
    
  2. 
      
     ls ./skills/
    
      
      
        
    • 
          40001
          AWS
          Speaking cloud fluently since forever. If it scales, I'm on it.
        
      • 
        
    • 
          40002
          Azure
          Because why not both?
        
      • 
        
    • 
          40003
          Ansible
          Manual configs? Nah, life's too short. Automate everything.
        
      • 
        
    • 
          40004
          NGINX / Apache
          Gatekeepers of the web. Traffic control is an art.
        
      • 
        
    • 
          40005
          CI/CD
          Push. Pull. Deploy. Repeat. One pipeline to rule them all.
        
      • 
        
    • 
          40006
          Docker / Podman / containerd
          I like my containers like my cats: fast and flexible.
        
      • 
        
    • 
          40007
          Go / Python / JS
          From goroutines to async/await, I speak them all fluently.
        
      • 
        
    • 
          40008
          ELK Stack
          Logs, metrics, dashboards — observability on point.
        
      • 
        
    • 
          40009
          Git
          Code is life. Merge conflicts are just spicy puzzles.
        
      • 
        
    • 
          40010
          Terraform / HashiCorp Stack
          Infrastructure as code, a.k.a. Lego for grown-ups.
        
      • 
        
    • 
          40011
          Kubernetes / Rancher / OpenShift
          Because managing a single cluster is way too boring.
        
      • 
        
    • 
          40012
          AuthN / AuthZ / TLS
          Because security isn't the cherry on top; it's the cake itself.
        
      • 
        
    • 
          40013
          YAML
          Writing human-readable configs one elegant indent at a time.
        
      • 
        
    • 
          40014
          Unix/Linux Admin / VMware
          I keep the servers humming and the incidents at bay.
        
      • 
        
    • 
          40015
          TCP/IP
          The magical plumbing behind the internet. I try to keep the gremlins out.
        
    
    
    3. 
      
    
  3. 
      
     openssl x509 -noout -text -in ./certs/*
    
      
    
    
    4. 
      
    
  4. 
      
     echo $MYPRINCIPLE
    
      
    If you don’t have time to build it right today, you definitely won’t have time to fix it when it blows up in production. MVPs — or should I say Mostly Vulnerable Products — have become the industry’s favorite excuse for cutting corners and calling it “iteration.” But let’s be honest: technical debt doesn’t wait politely in your backlog — it accrues like compound interest and bites back at 3 AM. I always say: your users aren’t lab rats. Shipping broken things just to “see what happens” isn’t agility — it’s reckless roulette.
    That’s why I advocate for MaxVP — Maximum Viable Product — where viability means sustainability, maintainability, and a little bit of pride. Around here, we build clean infrastructure, document the messes we inherit, and season our commit messages with just the right amount of sarcasm. Because if you’re going to build it, build it like someone’s future depends on it — because it probably does.
    
    
    5. 
      
    
  5. 
      
     netstat -c
    
      
    If you’re into platform wizardry or event-driven chaos, or you just want to argue whether tabs are better than spaces:
    
    
    6. 
      
  6. 
        
     Thanks for dropping by. Fork a repo, trigger a workflow, and remember — if you’re not automating something, are you even alive? 😎
    
      
    7.