On managed Kubernetes platforms like EKS, this has a second benefit: the cluster autoscaler pays attention to resource requests when deciding whether to add new nodes. - Source: dev.to / 2 months ago

After returning from AWS Summit London 2026 I was doing some research on running AI/ML workload in AWS EKS with Karpenter. With some assistance from Gemini I turned some of my notes from various talks into this guide that will talk through the intricacies of deploying and scaling Generative AI (GenAI) workloads on AWS EKS, leveraging the power of Karpenter. - Source: dev.to / 3 months ago

This post is a small step in that direction: serving an LLM using vLLM, deployed on Amazon EKS, provisioned the infra using AWS CDK, and wrapped into a simple chatbot using Streamlit. - Source: dev.to / 3 months ago

In this post, I'll walk you through setting up observability for Spring Boot applications on Amazon EKS - starting with the basics (logs and metrics), diving into distributed tracing, and finishing with Application Signals. Hopefully this saves you some time. - Source: dev.to / 7 months ago

Running Apache Spark on Kubernetes with AWS EMR on EKS brings big benefits – you get the best of both worlds. AWS EMR's optimized Spark runtime and AWS EKS's container orchestration come together in one managed platform. Sure, you could run Spark on Kubernetes yourself, but it's a lot of manual work. You'd need to create a custom container image, set up networking, and handle a bunch of other configurations. But... - Source: dev.to / 9 months ago

I have a small "GitHub summarizer" agent: one system prompt, one job — answer questions about my GitHub account by calling the GitHub MCP server. I duplicated its configuration (MAVERIK supports this directly — same model, same prompt, same everything) and changed one field on the copy: the set of attached MCP servers, adding deepwiki, microsoft-learn, and context7. Neither agent needs any of those three for the... - Source: dev.to / 11 days ago

GitHub's official MCP server is excellent — and GitHub is narrowing its default toolset and consolidating PR tools into fewer, more capable ones, explicitly to cut tool bloat and improve agent reasoning. The implication is hard to miss: even one of the best API companies on the planet is learning that a 1:1 mapping from product API to agent tools isn't the right shape. - Source: dev.to / about 2 months ago

The official GitHub MCP server registers 83 tools. Most people set it up for reading code and managing issues. What they don't realise is they've also handed their agent the keys to:. - Source: dev.to / about 2 months ago

A lot of people use MCP servers to connect Claude to tools. I'm not generally a fan. MCP servers load a lot of information into context and often don't do everything that the API can. Last I looked, even the official Github MCP Server is guilty of this. I'd rather write tools directly, to my specifications. - Source: dev.to / 4 months ago

Rather than manually searching through repositories, I used Kiro with the GitHub MCP server to:. - Source: dev.to / 4 months ago