Petr A

Facing the "Address is not allowed" error while deploying Apigee Hybrid on AWS EKS with Cilium? You've hit a common networking roadblock: the default CNI Overlay Mode conflict. Platform engineers and SREs: Don't let a webhook failure stall your mission-critical deployment. Ayo Salawu (TSC Apigee NorthAm) and Anmol Sachdeva (Hybrid Cloud Architect) share the guide to the fix: 🔸The Problem: Root cause analysis of the EKS kube-apiserver communication failure. 🔹The Solution: Precise eksctl and cilium-config.yaml steps for enabling ENI Mode (VPC Native Routing). ⭐The Outcome: Achieve seamless, secure, and successful Apigee Hybrid installation with VPC-native connectivity. Read the full story to overcome this hurdle →

🛡️ Secure your K8s Supply Chain in 4 Steps. Running Kubernetes? Make sure you aren't letting critical CVEs slip through into production. Our latest blog post breaks down how to combine JFrog and K8s to build an automated defense line. We cover everything from setting up trust to blocking Critical vulnerabilities automatically. Don't let bad images compromise your cluster. Check out the guide! 🚀 👉 Read more: https://lnkd.in/g3cYzrSM #Kubernetes #JFrog #DevSecOps #SupplyChainSecurity #DevOpsTec

2

AWS EKS Traffic Flow in Real Production: From Route 53 to Pods & RDS In real-world AWS production, Kubernetes is not just about running containers. It’s about designing a secure, scalable, and predictable traffic flow that can survive failures, scale under pressure, and remain observable at every layer. This architecture reflects a proven EKS production pattern used across SaaS, fintech, and enterprise platforms. 🔁 End-to-End Request Lifecycle 1️⃣ User → Route 53 DNS resolves the domain and routes traffic using health checks, failover, and multi-region strategies. 2️⃣ Route 53 → Application Load Balancer (Public Subnet) The ALB is the only internet-facing component. It terminates TLS, enforces security groups, and performs host/path-based routing. 3️⃣ ALB → EKS Worker Nodes (Private Subnets) Traffic is forwarded to target groups mapped to worker nodes that have no direct internet exposure. 4️⃣ NAT Gateway (Outbound Access) Nodes and pods access external services (images, APIs) securely without being publicly reachable. 5️⃣ NGINX Ingress → Services → Pods Ingress converts external traffic into Kubernetes-native routing, enabling: • Blue/green deployments • Canary releases • Zero-downtime rollouts 6️⃣ Pods → Amazon RDS (Database Subnet) The database is fully isolated. Only application security groups can access it—no internet gateway, no public exposure. ⸻ 🔐 Security by Design (Defense in Depth) • NACLs protect subnets • Security Groups control component-to-component traffic • Kubernetes Policies govern pod behavior Every layer has a clear boundary and failure domain. ⸻ 📌 Final Thought This model works in production because each layer has a single responsibility: • Internet traffic stops at the ALB • Compute stays in private networks • Data is isolated in dedicated subnets • NAT, SGs, and NACLs reduce blast radius When paired with observability, incident response, and controlled releases, this architecture enables teams to run Kubernetes on AWS with predictability, resilience, and confidence. #AWS #EKS #Kubernetes #DevOps #SRE #CloudArchitecture #PlatformEngineering #SiteReliability #SecurityByDesign #HighAvailability #Microservices

79

🚀 OpenEMR on EKS v2.6.2 is here! You know what’s 23,385 lines of code, written entirely by one person, open-sourced under an MIT license and lets you run an enterprise-grade Kubernetes deployment of the world’s most popular open-source medical record? That’s right — OpenEMR on EKS v2.6.2 🎉 Will I ever know what possessed me to write this? Probably not. Am I glad I’m going on vacation this Saturday? Definitely. But if you’re interested in Kubernetes, healthcare, or just what many cans of Celsius and a “can-do” attitude can accomplish, come check it out. And if you think it could be useful to someone, please share. It would be sincerely humbling if this project helps make healthcare even a little bit better. 👉 Project link: https://lnkd.in/eZ3_r2bS 💻 For the curious (and MacBook users), here’s an attached picture of a single one-liner you can run at your own risk that uses Bash (https://lnkd.in/eN8vJRMz)) to download Homebrew (https://brew.sh/), uses Homebrew to download Git (https://git-scm.com/), Git to download the repository (https://lnkd.in/eZ3_r2bS) and also downloads and uses cloc to count the number of lines of code in the project!

25

2 Comments

🚀 Speed Up Your Bold BI Setup with Easy Terraform Scripts Want to get Bold BI running in the cloud quickly and easily? Take a look at our Carousel Post to see how you can set up Bold BI confidently and quickly using our ready-made Terraform scripts for Amazon ECS & EKS, Azure AKS, and Google GKE. Easy setup instructions are available in our documentation.  https://lnkd.in/giUzxbzG Give it a try today and make better decisions with self-service and embedded analytics from Bold BI. #AWS #GCP #Kubernetes #terraformscripts 

10

1 Comment

Compute infrastructure has a hidden bottleneck. Not CPU. Not memory. It's energy. Most systems still run as if power is infinite. Seamium introduces a governance layer that keeps workloads aligned with real energy conditions. See how it works: seamium.com #seamium

1

Korrel8r is a rule-based correlation engine that automatically discovers and graphs relationships between Kubernetes cluster resources and observability signals across Prometheus, Loki, Alertmanager, and the Kubernetes API. More: https://ku.bz/tdFklzjTN

11