awslabs/amazon-eks-ami released AMI Release v20260318 What's Changed • fix: reserve EKS addon ports to prevent containerd port collisions by @Shreyank031 in https://github.com/awslabs/amazon-eks-ami/pull/2650 • chore: unpin containerd minor version by @mselim00 in https://github.com/awslabs/amazon-eks-ami/pull/2653 • feat(nodeadm): support public ecr authenticated ipv6 pulls by @mselim00 in https://github.com/awslabs/amazon-eks-ami/pull/2593 • fix(nodeadm): Bump Go version to 1.25.7 by @junpengdev in https://github.com/awslabs/amazon-eks-ami/pull/2657 New Contributors • @Shreyank031 made their first contribution in https://github.com/awslabs/amazon-eks-ami/pull/2650 Full Changelog: https://github.com/awslabs/amazon-eks-ami/compare/v20260311...v20260318

awslabs/amazon-eks-ami released AMI Release v20260318 #eks #kubernetes

Session policies for Amazon EKS Pod Identity In this post, we demonstrate how to use session policies to dynamically scope down IAM permissions for your Kubernetes pods without creating additional IAM roles, and discuss important considerations when adopting this feature.

Session policies for Amazon EKS Pod Identity #eks #kubernetes

A Complete Terraform Setup for EKS Auto Mode: Is it right for you? One of the things I appreciate about AWS is the range of container options available. I recently...

✍️ New blog post by Darryl Ruggles

A Complete Terraform Setup for EKS Auto Mode: Is it right for you?

#eks #aws #kubernetes #terraform

awslabs/kro released v0.9.0 What's Changed • cut docs v0.8.5 by @michaelhtm in https://github.com/kubernetes-sigs/kro/pull/1032 • fix: flaky validate RGD status test by @michaelhtm in https://github.com/kubernetes-sigs/kro/pull/1034 • chore(deps): bump webpack from 5.96.1 to 5.105.0 in /website in the npm_and_yarn group across 1 directory by @dependabot[bot] in https://github.com/kubernetes-sigs/kro/pull/1027 • refactor(cel): Move cel conversion functions to separate package by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1043 • Fix flaky validate RGD status integration test by @Aman-Cool in https://github.com/kubernetes-sigs/kro/pull/1041 • add jakobmoellerdev to kro-maintainers by @jlbutler in https://github.com/kubernetes-sigs/kro/pull/1020 • promote nicslatts to emeritus-kro-maintainers by @jlbutler in https://github.com/kubernetes-sigs/kro/pull/1044 • chore: bump controller-runtime to v0.23.1 by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1046 • chore: bump cel-go to v0.27.0 by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1047 • Limit collection size to 1000 to protect cluster performance by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1036 • Add map library with merge functionality by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1068 • chore: limit collection dimension to 5 by @michaelhtm in https://github.com/kubernetes-sigs/kro/pull/1045 • fix(docs): Wrong schema apiVersion definition in RGD chaining by @gagahsyuja in https://github.com/kubernetes-sigs/kro/pull/1050 • fix: properly return error in simpleschema parsing when the marker does by @NickKeller in https://github.com/kubernetes-sigs/kro/pull/1073 • Add json.marshal and json.unmarshal cel functions by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1033 • chore(deps): bump the npm_and_yarn group across 2 directories with 4 updates by @dependabot[bot] in https://github.com/kubernetes-sigs/kro/pull/1070 • fix: remove the rgd labels from managed resources by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1075 • fix(applyset): preserve prune scope on UID conflicts and requeue retry by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1081 • chore: Remove myself from NOTICE by @codesenju in https://github.com/kubernetes-sigs/kro/pull/1082 • Document escaping Bash '${VAR}' syntax for CEL by @mwarkentin in https://github.com/kubernetes-sigs/kro/pull/1083 • fix: pass up expressive error by @fabianburth in https://github.com/kubernetes-sigs/kro/pull/1078 • feat: disable instance reconciliation when a kro.run/reconcile:"disabled" label is present by @NickKeller in https://github.com/kubernetes-sigs/kro/pull/1062 • fix(runtime): schema-aware CEL value conversion by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1080 • chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates by @dependabot[bot] in https://github.com/kubernetes-sigs/kro/pull/1087 • chore(deps): bump @tootallnate/once from 2.0.0 to removed in /website in the npm_and_yarn group across 1 directory by @dependabot[bot] in https://github.com/kubernetes-sigs/kro/pull/1089 • feat: external ref watches and external ref collections by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1079 • docs: expand external references to support collections with label selectors by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1093 • test: harden pkg/runtime coverage by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1099 • build: group Dependabot npm and Go security updates by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1096 • test(instance): harden instance reconciler coverage by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1103 • fix(cel/ast): derive known functions from CEL environment by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1109 • test(rgd): Harden rgd controller unit tests by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1102 • docs(website): remove pre-v0.7.0 entries from versions.json by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1111 • fix(graph/resolver): expose schema resolver metrics on controller-runtime registry by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1113 • dynamiccontroller: retain parent informers for shared GVR watches by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1105 • perf(graph): eliminate duplicate CEL type building during RGD construction by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1116 • Fix ResourceGraphDefinition delete predicate handling by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1097 • feat: add metrics for pkg/runtime by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1053 • docs(metrics): add stability notice for ALPHA metrics by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1118 • perf(cel): cache base declarations and environment with sync.Once by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1119 • dynamiccontroller: rollback provisional watches on failed reconciles by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1106 • test: verify externalref integration cases reconcile on watched updates by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1123 • refactor(dag): use a heap-based topological sort by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1122 • test(pkg/graph): harden unit tests for graph builder and friends by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1120 • feat(compat): detect default value changes as non-breaking in schema comparison by @michaelhtm in https://github.com/kubernetes-sigs/kro/pull/1098 • Add AWS Accounts Factory example with nested RGDs by @tzahimizrahi in https://github.com/kubernetes-sigs/kro/pull/1128 • KREP-008: docs: add proposal for resource-backed includeWhen evaluation by @shivansh-source in https://github.com/kubernetes-sigs/kro/pull/933 • feat(cel): add deterministic seeded integer generation function by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1108 • website: overhaul overview docs with interactive resource graph diagrams by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1110 • Make string templates compile to concentation by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1131 • fix: return a requeue error when waiting for readiness by @fabianburth in https://github.com/kubernetes-sigs/kro/pull/1090 • feat(helm): add topologySpreadConstraints in deployment by @QuentinBtd in https://github.com/kubernetes-sigs/kro/pull/1137 • feat(instance): block graph propagation on terminating managed resources by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1132 • Add RGD controller metrics by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1063 • feat(cel): add support for TwoVarComprehensions in CEL environment by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1136 • perf(cel): add caching for CEL compilation artifacts to optimize performance by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1129 • fix(cel): sort transformList result before comparison in TwoVar test by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1141 • Fix: Kro controller metrics report errors when objects are deleted by @Avr8 in https://github.com/kubernetes-sigs/kro/pull/1059 • feat(cel): add metrics for CEL cache hit/miss tracking by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1142 • Add instance controller metrics by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1056 • feat(cel): add cel.bind() support to default environment and AST inspector by @pnz1990 in https://github.com/kubernetes-sigs/kro/pull/1145 • website: add KREP roadmap page by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1133 • docs: add "Building Abstractions with kro" guides by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1112 • KREP-003: Decorators (Collection Watching) by @ellistarn in https://github.com/kubernetes-sigs/kro/pull/738 • refactor(api): move InstanceState and NodeState to api/v1alpha1 by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1134 • chore(deps): bump dompurify from 3.3.0 to 3.3.2 in /website in the npm_and_yarn group across 1 directory by @dependabot[bot] in https://github.com/kubernetes-sigs/kro/pull/1092 • feat(cel): add index-mutation functions to the lists library by @pnz1990 in https://github.com/kubernetes-sigs/kro/pull/1148 • chore: implement annotation change predicate to allow reconciles on a… by @shabbskagalwala in https://github.com/kubernetes-sigs/kro/pull/1155 • Add client-go and reflector metrics registration by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1143 • test: add webhook denial integration tests with ValidatingAdmissionPolicy by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1154 • KREP-10 for cluster-scoped instance CRDs by @antcybersec in https://github.com/kubernetes-sigs/kro/pull/1030 • KREP-017 template field omission with omit() by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1121 • allow includeWhen to reference other resources by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1104 • Use expressive histogram buckets for controller reconciliation metrics by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1157 • commit watches on requeue signals, not just on success by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1158 • feat: implement KREP-10 - support cluster-scoped instance CRDs by @antcybersec in https://github.com/kubernetes-sigs/kro/pull/1152 • feat(cel): add omit() for conditional field omission in templates by @michaelhtm in https://github.com/kubernetes-sigs/kro/pull/1139 • test: integration test case, omit() removes field by @michaelhtm in https://github.com/kubernetes-sigs/kro/pull/1168 • feat(#510): implement standard Kubernetes feature gates via component-base by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1172 • fix: show root cause error by @fabianburth in https://github.com/kubernetes-sigs/kro/pull/1160 • fix(dynamic): skip parent instance events with unchanged generation by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1173 • fix(metadata): skip instance-namespace label for cluster-scoped instances by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1175 • KREP-15: label/annotation migration to internal.kro.run/ prefix by @michaelhtm in https://github.com/kubernetes-sigs/kro/pull/1094 • docs: Update docs be explicitly clear about resources depending on schema.spec by @NickKeller in https://github.com/kubernetes-sigs/kro/pull/1072 • docs: document cluster-scoped instance support by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1162 • fix(docs): correct RGD conditions by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1181 • fix(collections): register collection watch for all expanded resources by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1182 • feat(cel): add k8s Quantity library support by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1177 • fix(cel): handle oneOf string|number schemas in UnstructuredToVal by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1179 • feat: Add opt-in pprof profiling support via build tags by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/922 • feat(graph): reject omit() on required resource metadata fields by @michaelhtm in https://github.com/kubernetes-sigs/kro/pull/1167 • refactor(runtime,instance): split large files and simplify state management by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1165 • feat(cel): add k8s Lists library support by @NicholasBlaskey in https://github.com/kubernetes-sigs/kro/pull/1178 • Use RGD metadata.name as the label for ResourceGraphDefinition controller metrics. by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1140 • make instance requeue interval configurable by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1184 • add verify-codegen script by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1183 • feat(events): Add events for instance status condition transition by @spattk in https://github.com/kubernetes-sigs/kro/pull/1151 • feat(graph): gate omit() behind CELOmitFunction feature flag by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1185 • docs: Add a page for feature gates by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1186 • feat(helm): expose feature gates in chart values by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1187 • fix(externalref): allow external collections to list across all namespaces by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1180 • fix(test): use unique labels to avoid cross-namespace collisions by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1193 • harden BuilderCache stores and cache iterator environments by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1189 • add schema.Cache for pointer stable OpenAPI field lookups by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1190 • perf: removes the lock convoy during large RGD bursts by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1192 • fix: disable instance reconciliation with annotation instead of label by @michaelhtm in https://github.com/kubernetes-sigs/kro/pull/1191 • fix missing dynamic controller registration, and wire up missing metrics by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1146 • key typed env cache by schema structure instead of pointer address by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1194 • Implementation of Graph Revisions (KREP-013) by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1085 • fix: get rid of cel build caches due to problems during stabilization by @jakobmoellerdev in https://github.com/kubernetes-sigs/kro/pull/1195 • Add verify-codegen ci entrypoint by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1196 • Add an upgrade test framework that validates kro upgrades don't break by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1197 • refactor(apis): add condition prune mechanism for upgrades by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1198 • fix(instance): surface graph resolution failures in conditions and metrics by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1201 • docs(website): rewrite graph revisions page and add interactive diagrams by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1199 • Update helm chart and values.yaml by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1203 • docs: Fix formatting in the verify installation step (getting started… by @KatharinaSick in https://github.com/kubernetes-sigs/kro/pull/1188 • Watch owned GraphRevisions from the RGD controller by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1200 • expose leader election tuning flags in helm chart by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1205 • feat(perf): use DefaultUnstructuredConverter to eliminate JSON round-trips in conditions by @spattk in https://github.com/kubernetes-sigs/kro/pull/1204 • watch graph revisions by spec.snapshot.name for orphan adoption by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1206 • cut docs for 0.9.0 by @a-hilaly in https://github.com/kubernetes-sigs/kro/pull/1207 New Contributors • @NicholasBlaskey made their first contribution in https://github.com/kubernetes-sigs/kro/pull/1043 • @gagahsyuja made their first contribution in https://github.com/kubernetes-sigs/kro/pull/1050 • @NickKeller made their first contribution in https://github.com/kubernetes-sigs/kro/pull/1073 • @mwarkentin made their first contribution in https://github.com/kubernetes-sigs/kro/pull/1083 • @shivansh-source made their first contribution in https://github.com/kubernetes-sigs/kro/pull/933 • @QuentinBtd made their first contribution in https://github.com/kubernetes-sigs/kro/pull/1137 • @Avr8 made their first contribution in https://github.com/kubernetes-sigs/kro/pull/1059 • @pnz1990 made their first contribution in https://github.com/kubernetes-sigs/kro/pull/1145 • @KatharinaSick made their first contribution in https://github.com/kubernetes-sigs/kro/pull/1188 Full Changelog: https://github.com/kubernetes-sigs/kro/compare/v0.8.5...v0.9.0

awslabs/kro released v0.9.0 #kro #eks #kubernetes

How Generali Malaysia optimizes operations with Amazon EKS In this post, we look at how Generali is using Amazon EKS Auto Mode and its integration with other AWS services to enhance performance while reducing operational overhead, optimizing costs, and enhancing security.

How Generali Malaysia optimizes operations with Amazon EKS #eksautomode #eks #kubernetes

kubernetes-sigs/aws-ebs-csi-driver released v1.57.1 AWS EBS CSI Driver CHANGELOG See CHANGELOG for full list of changes

kubernetes-sigs/aws-ebs-csi-driver released v1.57.1 #eks #kubernetes

Amazon EKS announces 99.99% Service Level Agreement and new 8XL scaling tier for Provisioned Control Plane clusters

חדש! Amazon EKS מציע SLA של 99.99% ורמת 8XL לאשכולות Provisioned Control Plane לביצועים מקסימליים #AWS #EKS

kubernetes-sigs/aws-ebs-csi-driver released helm-chart-aws-ebs-csi-driver-2.57.1 A Helm chart for AWS EBS CSI Driver

kubernetes-sigs/aws-ebs-csi-driver released helm-chart-aws-ebs-csi-driver-2.57.1 #eks #kubernetes

aws/karpenter-provider-aws released v1.10.0 Features • add kubereplay tool for workload replay (#8864) #8864 (Ellis Tarn) • support launching from interruptible ODCRs (#9019) #9019 (Ryan Mistretta) Bug Fixes • prevent RequestLimitExceeded CreateFleet error from marking ODCRs unavailable #8936 (Sarthak Umarani) Documentation • carry forward static capacity docs (#8956) #8956 (Jason Deal) • add karpenter.sh/nodepool, karpenter.k8s.aws/ec2nodeclass, topology.k8s.aws/zone-id labels to the list of well known labels. minor contribution guide update (#8960) #8960 (Derek Frank) • update cloudformation reference (#8958) #8958 (Jason Deal) • upgrade guide (#9025) #9025 (Ryan Mistretta) Chores • Release v1.9.0 (#8938) #8938 (github-actions[bot]) • Add kubelet Memory Manager policy for Bottlerocket (#8907) #8907 (Jens-Uwe Walther) • deps: bump golang.org/x/oauth2 from 0.23.0 to 0.27.0 in /tools/kubereplay (#8950) #8950 (dependabot[bot]) • Bump upstream karpenter version (#8979) #8979 (Jigisha Patil) • deps: bump the go-deps group across 1 directory with 14 updates (#8980) #8980 (dependabot[bot]) • deps-dev: bump tar from 7.5.6 to 7.5.9 in /website (#8974) #8974 (dependabot[bot]) • Add instances ineligible for free tier error (#9004) #9004 (Andrew Mitchell) • bump karpenter version (#9024) #9024 (Ryan Mistretta)

aws/karpenter-provider-aws released v1.10.0 #karpenter #eks #kubernetes

EKS Diagnoses: The Swiss Knife The 2 AM wake-up call every Kubernetes engineer dreads — and the tool I built to make it...

✍️ New blog post by Amar Tinawi

EKS Diagnoses: The Swiss Knife

#aws #eks #kubernetes #k8s

Amazon EKS announces 99.99% Service Level Agreement and new 8XL scaling tier for Provisioned Control Plane clusters <p><a href="https://aws.amazon.com/eks/">Amazon Elastic Kubernetes Service (Amazon EKS)</a>&nbsp;now offers a 99.99% Service Level Agreement (SLA) for clusters running on Provisioned Control Plane, up from the 99.95% SLA offered on standard control plane. Amazon EKS is also introducing the 8XL scaling tier, the largest available Provisioned Control Plane tier.<br> <br> Provisioned Control Plane gives you the ability to select your cluster's control plane capacity from a set of well-defined scaling tiers, ensuring the control plane is pre-provisioned and ready to handle traffic spikes or unpredictable bursts. The higher 99.99% SLA is measured in 1-minute intervals, providing a more granular and stringent availability commitment for mission-critical workloads. The new 8XL tier offers double the Kubernetes API server request processing capacity of the next lower 4XL tier, enabling workloads such as ultra-scale AI/ML training, high-performance computing (HPC), and large-scale data processing.<br> <br> Both the 99.99% SLA and the 8XL tier are available today in all AWS regions where Amazon EKS Provisioned Control Plane is offered. To learn more about the SLA, see the&nbsp;<a href="https://aws.amazon.com/eks/sla/">Amazon EKS Service Level Agreement</a>. For 8XL pricing and capabilities, see the&nbsp;<a href="https://aws.amazon.com/eks/pricing/">EKS pricing</a>&nbsp;and&nbsp;<a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-provisioned-control-plane.html">EKS Provisioned Control Plane documentation</a>.</p>

Amazon EKS announces 99.99% Service Level Agreement and new 8XL scaling tier for Provisioned Control Plane clusters #eks #kubernetes

AWS Neuron announces support for Dynamic Resource Allocation with Amazon EKS <p>AWS announces the Neuron Dynamic Resource Allocation (DRA) driver for Amazon Elastic Kubernetes Service (EKS), bringing Kubernetes-native hardware-aware scheduling to AWS Trainium-based instances. The Neuron DRA driver publishes rich device attributes — including hardware topology and Neuron-EFA PCIe co-location — directly to the Kubernetes scheduler, enabling topology-aware placement decisions without custom scheduler extensions.<br> <br> Deploying AI workloads on Kubernetes requires ML engineers to make infrastructure decisions that are not directly related to model development, such as determining device counts, understanding hardware and network topologies, and writing accelerator-specific manifests. This creates friction, slows iteration, and tightly couples workloads to underlying infrastructure. As use cases expand to distributed training, long-context inference, and disaggregated architectures, this complexity becomes a scaling bottleneck.<br> <br> The Neuron DRA driver removes this burden by separating infrastructure concerns from ML workflows. Infrastructure teams define reusable ResourceClaimTemplates that capture device topology, allocation, and networking policies—for example, mapping instance types to optimal NeuronDevice and EFA configurations. ML engineers can simply reference these templates in their manifests, without needing to reason about hardware details. This enables consistent deployment across workload types while allowing per-workload configuration so multiple workloads can efficiently share the same nodes.<br> <br> The Neuron DRA driver supports all AWS Trainium instance types&nbsp; and is available in all AWS Regions where AWS Trainium is available.</p> <p>For documentation, sample templates, and implementation guides, visit <a href="https://awsdocs-neuron.readthedocs-hosted.com/en/latest/containers/neuron-dra.html">the Neuron DRA documentation.</a></p> <p><b>Learn more:</b><br> </p> <ul> <li><a href="https://awsdocs-neuron.readthedocs-hosted.com/en/latest/containers/neuron-dra.html">Neuron EKS DRA templates</a></li> <li><a href="https://awsdocs-neuron.readthedocs-hosted.com/en/latest/containers/kubernetes-getting-started.html" style="background-color: rgb(255,255,255);">Neuron EKS documentation</a></li> <li><a href="https://docs.aws.amazon.com/eks/latest/userguide/device-management-neuron.html">Amazon EKS documentation</a></li> </ul>

AWS Neuron announces support for Dynamic Resource Allocation with Amazon EKS #eks #kubernetes

The 80/20 of AWS (the services that actually matter) AWS has over 200 services. That number is intimidating. You log into the console, see a wall of icons, and immediately feel like you need a…

heyjoshlee.medium.com/the-80-20-of...

#AWS #cloud #infrastructure #EC2 #IAM #S3 #RDS #DynamoDB #Lambda #APIGateway #CloudFront #Route53 #SQS #SNS #CloudWatch #EKS #CDN

Tigera Tigera provides zero-trust network security and continuous compliance for Kubernetes platforms that enables enterprises to meet their security and compliance requirements.

The latest update for #Tigera includes "What Your #EKS Flow Logs Aren't Telling You" and "How AI Agents Communicate: Understanding the A2A Protocol for #Kubernetes".

#cybersecurity #devops https://opsmtrs.com/2ZYXor3

Deploy production generative AI at the edge using Amazon EKS Hybrid Nodes with NVIDIA DGX This post demonstrates a real-world example of integrating EKS Hybrid Nodes with NVIDIA DGX Spark, a compact and energy-efficient GPU platform optimized for edge AI deployment. In this post we walk you through deploying a large language model (LLM) for low-latency generative AI inference on-premises, setting up node monitoring and GPU observability with centralized management through Amazon EKS.

Deploy production generative AI at the edge using Amazon EKS Hybrid Nodes with NVIDIA DGX #eks #kubernetes

AI-powered event response for Amazon EKS In this post, you'll learn how AWS DevOps Agent integrates with your existing observability stack to provide intelligent, automated responses to system events.

AI-powered event response for Amazon EKS #eks #kubernetes

Building a Production-Grade Private EKS Cluster with OpenVPN, Prometheus & Grafana Step-by-step guide to deploying a private Amazon EKS cluster with zero public API exposure,...

✍️ New blog post by Asmaa Elalfy

Building a Production-Grade Private EKS Cluster with OpenVPN, Prometheus & Grafana

#devops #aws #eks #kubernetes

Building a Production-Grade Private EKS Cluster with OpenVPN, Prometheus & Grafana Liquid syntax error: Unknown tag 'aside'

✍️ New blog post by Asmaa Elalfy

Building a Production-Grade Private EKS Cluster with OpenVPN, Prometheus & Grafana

#aws #eks #terraform #devops

AWS Backup adds logically air-gapped vault support for Amazon EKS <p>AWS Backup logically air-gapped vault now supports Amazon EKS. Logically air-gapped vaults are a type of AWS Backup vault that allows secure sharing of backups across accounts and AWS Organizations, supporting direct restore to reduce recovery time from a data loss event.</p> <p>You can now protect your Amazon EKS clusters in logically air-gapped vaults. A logically air-gapped vault stores immutable backup copies that are locked by default, and isolated with encryption using AWS owned keys or customer-managed keys. You can store your Amazon EKS backups in a logically air gapped vault either the same account or across other accounts and Regions. This helps reduce the risk of downtime, ensure business continuity, and meet compliance and disaster recovery requirements.</p> <p>You can get started using the <a href="https://console.aws.amazon.com/backup/home">AWS Backup console</a>, API, or CLI. Target Amazon EKS backups to a logically air-gapped vault by specifying it as the primary target or copy destination in your backup plan. Share the vault for recovery using <a href="https://aws.amazon.com/ram/">AWS Resource Access Manager</a> (RAM) or access it via Multi-party approval. Once available, you can initiate direct restore jobs from that account, eliminating the overhead of copying backups first.</p> <p>AWS Backup logically air-gapped vault support for Amazon EKS is available in 24 AWS Regions. For more information and detailed regional availability, visit the <a href="https://docs.aws.amazon.com/aws-backup/latest/devguide/eks-backups.html">AWS Backup documentation</a>.</p>

AWS Backup adds logically air-gapped vault support for Amazon EKS #eks #kubernetes

EKS Capabilities Deep Dive: ArgoCD, KRO, and ACK #kro #eks #kubernetes

Automated Amazon EKS Pod Right-Sizing | Step-by-Step Demo with Amazon Bedrock and ArgoCD #eks #kubernetes

From Zero to EKS in Minutes First, you're going to use the following CLIs as local tooling: eksctl: to create EKS clusters in...

✍️ New blog post by dejanualex

From Zero to EKS in Minutes

#aws #eks #kubernetes #devops

awslabs/amazon-eks-ami released AMI Release v20260304 What's Changed • Ensure Nvidia repo install for Isolated regions by @whoix in https://github.com/awslabs/amazon-eks-ami/pull/2636 • Skip nvidia-repo-sync package during verification by @whoix in https://github.com/awslabs/amazon-eks-ami/pull/2638 Full Changelog: https://github.com/awslabs/amazon-eks-ami/compare/v20260224...v20260304

awslabs/amazon-eks-ami released AMI Release v20260304 #eks #kubernetes

Application Performance Monitoring Enabled by Default in CloudWatch Observability EKS Add-on <p>Today, Amazon CloudWatch Observability EKS add-on version 5.0.0 automatically enables CloudWatch Application Signals — Amazon's application performance monitoring (APM) capability — for all new installations and upgrades, eliminating the previous manual opt-in step. Amazon Elastic Kubernetes Service (EKS) is a managed Kubernetes service that simplifies running containerized applications at scale. The CloudWatch Observability add-on for EKS extends native Kubernetes observability by integrating Enhanced Container Insights, Container Logs, and now Application Signals directly into your clusters. The Observability add-on automatically instruments your services to collect traces, metrics, and logs for a unified, application-centric view. For DevOps engineers, platform teams, and developers who needed application-level visibility into their EKS-hosted services — such as service latency, error rates, and request traces — this change closes that gap by making those capabilities available out of the box, so teams can focus on building and operating applications rather than configuring observability tooling.azon EKS.</p> <p>With Application Signals now enabled by default, customers immediately benefit from automatic service instrumentation — no manual configuration or Kubernetes workload annotations required — along with pre-built dashboards that surface application performance metrics and a rich troubleshooting experience that goes beyond infrastructure-level data to help teams quickly identify and resolve issues. For example, a platform team managing a microservices application on EKS can now detect latency spikes or error rate increases at the service level without any additional setup, accelerating root cause analysis during incidents.</p> <p>This feature is available in all commercial AWS regions where Amazon CloudWatch Application Signals is available; to get started, you can refer to the <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/install-CloudWatch-Observability-EKS-addon.html#Container-Insights-setup-EKS-appsignalsconfiguration">Amazon CloudWatch Application Signals documentation</a> and upgrade to version 5.0.0 of the add-on.</p>

Application Performance Monitoring Enabled by Default in CloudWatch Observability EKS Add-on #eks #kubernetes

Amazon EKS Capabilities Demo | GitOps with ACK and ArgoCD #eks #kubernetes

awslabs/amazon-eks-ami released AMI Release v20260224 What's Changed • feat: set oom score for ssm-agent by @fletcherw in https://github.com/awslabs/amazon-eks-ami/pull/2618 • fix: make govcloud builds possible by @fletcherw in https://github.com/awslabs/amazon-eks-ami/pull/2621 • chore: add test timing to e2e tests by @fletcherw in https://github.com/awslabs/amazon-eks-ami/pull/2614 • feat(nodeadm): add console logging support to nodeadm by @chenwng in https://github.com/awslabs/amazon-eks-ami/pull/2620 • fix: initialize logger after parsing command line flags by @chenwng in https://github.com/awslabs/amazon-eks-ami/pull/2633 New Contributors • @chenwng made their first contribution in https://github.com/awslabs/amazon-eks-ami/pull/2620 Full Changelog: https://github.com/awslabs/amazon-eks-ami/compare/v20260209...v20260224

awslabs/amazon-eks-ami released AMI Release v20260224 #eks #kubernetes

Dyrektorzy NAWA Wojciech Karczewski i Damian Syjczak na XI Europejskim Kongresie Samorządów.
Wspólnie z samorządami i środowiskiem akademickim dyskutujemy o tym, jak potencjał polskich i zagranicznych naukowców może wspierać rozwój lokalnych społeczności.

#NAWA #EKS

Grafana on EKS – Install and Test Deploy Grafana on EKS via Argo CD, configure Prometheus datasource, and access it locally with port-forward. Includes full Application manifest and verification steps.

Grafana on EKS – Install and Test Grafana on EKS – Install and Test Deploy Grafana via Argo CD on EKS and access it locally with port-forward. The Application manifest includes persistence, Pro...

#grafana #eks #argocd #prometheus

Origin | Interest | Match

Argo CD Ingress Stuck – Find & Fix Troubleshoot Argo CD ingress that is stuck without an address or in Terminating state. Learn how to diagnose ssl-redirect issues, check ALB controller logs, and fix stuck ingress resources.

Argo CD Ingress Stuck – Find & Fix Argo CD Ingress Stuck – Find & Fix When Argo CD ingress gets stuck—no ADDRESS assigned or stuck in Terminating—the AWS Load Balancer Controller ma...

#argocd #eks #ingress #troubleshooting

Origin | Interest | Match

Stop Managing Kubernetes Infrastructure Manually — Use EKS Capabilities Instead If you've ever spent hours wiring Helm charts, debugging IRSA roles, or babysitting controller...

✍️ New blog post by Asma Elalfy

Stop Managing Kubernetes Infrastructure Manually — Use EKS Capabilities Instead

#aws #k8s #eks #devops