Kyverno Automates Proxy Injection for EKS on Fargate
AWS details a solution for automating HTTP/HTTPS proxy injection into Amazon EKS pods running on AWS Fargate using Kyverno mutating admission policies. This addresses a common friction point for enterprises in regulated environments requiring outbound traffic to pass through a corporate proxy, a scenario challenging due to Fargate's managed node layer. The approach centralizes proxy configuration with a single GitOps-compatible Kubernetes policy, eliminating the need for per-workload manifest changes. This significantly reduces operational effort for EKS administrators and simplifies onboarding for application teams.
Notes (1) ›
- Automated Proxy Injection for EKS on Fargate
This solution leverages Kyverno mutating admission policies to automatically inject HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables into Fargate pods in labeled namespaces. It provides a centrally managed, GitOps-compatible approach for routing outbound EKS Fargate traffic through corporate proxies, crucial for regulated environments, and removes the need for manual, per-workload configuration.
https://aws.amazon.com/blogs/containers/automate-proxy-injection-for-amazon-eks-on-aws-fargate-using-kyverno/
Related releases
- Fast Model Loading for AI Inference on Amazon EKS AWS Containers Blog ·
- Amazon EC2 R9g and R9gd Memory-Optimized Instances Now Generally Available AWS What's New ·
- Amazon EMR on EKS Adds Job Run Concurrency Controls AWS What's New ·
- Mountpoint for Amazon S3 adds memory usage controls AWS What's New ·
- Break-Glass Access for Amazon EKS When Federated Identity Fails AWS Containers Blog ·
- GPU-accelerated Apache Spark on Amazon EMR with EC2 G7 instances runs up to 3.7x faster AWS Big Data Blog ·