Home New Trending Search
About Privacy Terms
#
#eks
Posts tagged #eks on Bluesky
Preview
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

1 0 0 0
Preview
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

0 0 0 0
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

0 0 0 0
EKS Capabilities Deep Dive: ArgoCD, KRO, and ACK
EKS Capabilities Deep Dive: ArgoCD, KRO, and ACK

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

0 0 0 0
Automated Amazon EKS Pod Right-Sizing | Step-by-Step Demo with Amazon Bedrock and ArgoCD
Automated Amazon EKS Pod Right-Sizing | Step-by-Step Demo with Amazon Bedrock and ArgoCD

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

0 0 0 0
Preview
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

0 0 0 0
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

1 0 0 0
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

0 0 0 0
Amazon EKS Capabilities Demo | GitOps with ACK and ArgoCD
Amazon EKS Capabilities Demo | GitOps with ACK and ArgoCD

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

0 0 0 0
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

0 0 0 0
Post image

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

0 0 0 0
Preview
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

0 0 0 0
Preview
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

0 0 0 0
Preview
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

2 0 0 0
AI Model Training and Inference on Amazon SageMaker HyperPod EKS | Amazon Web Services
AI Model Training and Inference on Amazon SageMaker HyperPod EKS | Amazon Web Services

AI Model Training and Inference on Amazon SageMaker HyperPod EKS | Amazon Web Services #eks #kubernetes

0 0 0 0
Train AI Models on Amazon SageMaker HyperPod EKS | Amazon Web Services
Train AI Models on Amazon SageMaker HyperPod EKS | Amazon Web Services

Train AI Models on Amazon SageMaker HyperPod EKS | Amazon Web Services #eks #kubernetes

0 0 0 0
Run AI Models Inference on Amazon SageMaker HyperPod EKS | Amazon Web Services
Run AI Models Inference on Amazon SageMaker HyperPod EKS | Amazon Web Services

Run AI Models Inference on Amazon SageMaker HyperPod EKS | Amazon Web Services #eks #kubernetes

0 0 0 0
kubernetes-sigs/aws-load-balancer-controller released v3.1.0 📚 Quick Links v3.1.0 (requires Kubernetes 1.22+) Image: public.ecr.aws/eks/aws-load-balancer-controller:v3.1.0 Documentation Thanks to all our contributors!💜💜💜 ⚠️ Action Required CRD Updates Action : Please apply the latest CRD definitions • kubectl apply -k "github.com/aws/eks-charts/stable/aws-load-balancer-controller/crds?ref=master" If using Gateway API feature • Installation of LBC Gateway API specific CRDs: kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/refs/heads/main/config/crd/gateway/gateway-crds.yaml • Standard Gateway API CRDs: kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.3.0/standard-install.yaml [REQUIRED] • Experimental Gateway API CRDs: kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.3.0/experimental-install.yaml [OPTIONAL: Used for L4 Routes] 🚀 What's New Gateway API Enhancements • [ALB Gateway] Port defaulting for scheme - Fixed redirect port handling to comply with Gateway API spec. When port is not specified in HTTPRequestRedirectFilter, the controller correctly defaults to well-known ports (80 for http, 443 for https) based on the redirect scheme. • [ALB Gateway] Improved regex handling - Corrected regex value handling in Gateway API route matching • [Gateway] Status hostname normalization - Gateway status hostnames are now normalized to lowercase for consistency AWS Global Accelerator Controller • [AGA] Cross-namespace reference support - AGA resources can now reference resources across namespaces, enabling more flexible multi-tenant architectures 🔧 Enhancements and Fixes • [NLB Gateway] TLS passthrough listener - Fixed TLS listener construction to respect TLS mode configuration. NLB Gateways now support passthrough, termination, and re-encryption modes as defined in Gateway API spec. Note: SNI-based routing is not supported due to AWS NLB dataplane limitations. • [Ingress] Rule optimizer - Fixed incorrect removal of regex-based listener rules that could cause routing failures • [HelmUpgrade] Webhook certificate regeneration - Fixed certificate regeneration issues during Helm upgrades. Reintroduce the keepTLSSecret parameter with improved logic that maintains cert-manager compatibility. • [Gateway] NPE on invalid parameters - Added null pointer protection and enhanced debugging for invalid parameter references Documentation Updates • Updated service.beta.kubernetes.io/aws-load-balancer-type annotation documentation • Moved QUIC documentation to L4 section for better organization • Updated Helm chart information Changelog since v3.0.0 • [feat aga] Add cross-namespace reference support for AGA by @shraddhabang in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4547 • fix TLS passthrough listener by @zac-nixon in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4559 • Fix NPE on invalid parameters ref, add more debugging details to accepted status by @zac-nixon in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4562 • add port defaulting for scheme by @zac-nixon in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4568 • move QUIC documentation to l4 by @zac-nixon in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4570 • Fix rule optimizer incorrectly removing regex-based listener rules by @shraddhabang in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4569 • correct regex value handling in gateway api by @zac-nixon in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4577 • Add k8s event for TGB failures by @vishwas121 in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4571 • Update docs for service.beta.kubernetes.io/aws-load-balancer-type annotation by @kellyyan in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4578 • update helm info by @zac-nixon in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4583 • Fix webhook certificate regeneration on Helm upgrades by @shraddhabang in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4581 • Filter RequeueNeeded errors to skip event triggers on TGB controller by @vishwas121 in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4584 • fix(gateway): normalize status hostname to lowercase by @TOGEP in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4591 New Contributors • @vishwas121 made their first contribution in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4571 • @TOGEP made their first contribution in https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/4591 Full Changelog: https://github.com/kubernetes-sigs/aws-load-balancer-controller/compare/v3.0.0...v3.1.0

kubernetes-sigs/aws-load-balancer-controller released v3.1.0 #eks #kubernetes

0 0 0 0
Preview
Deep dive: Simplifying resource orchestration with Amazon EKS Capabilities This blog post focuses on ACK and kro capabilities. For a deep dive on Amazon EKS capability for Argo CD, check out Deep dive: Streamlining GitOps with Amazon EKS capability for Argo CD.

Deep dive: Simplifying resource orchestration with Amazon EKS Capabilities #kro #eks #kubernetes

0 0 0 0
Amazon EKS Node Monitoring Agent is now open source <p>Amazon Elastic Kubernetes Service (Amazon EKS) Node Monitoring Agent is now open source. You can access the Amazon EKS Node Monitoring Agent source code and contribute to its development on <a title="GitHub" href="https://github.com/aws/eks-node-monitoring-agent">GitHub</a>.<br> <br> Running workloads reliably in Kubernetes clusters can be challenging. Cluster administrators often have to resort to manual methods of monitoring and repairing degraded nodes in their clusters. The Amazon EKS Node Monitoring Agent simplifies this process by automatically monitoring and publishing node-level system, storage, networking, and accelerator issues as node conditions, which are used by Amazon EKS for automatic node repair. With the Amazon EKS Node Monitoring Agent’s source code available on GitHub, you now have visibility into the agent’s implementation, can customize it to fit your requirements, and can contribute directly to its ongoing development.<br> <br> The Amazon EKS Node Monitoring Agent is included in Amazon EKS Auto Mode and is available as an Amazon EKS add-on in all AWS Regions where Amazon EKS is available.<br> <br> To learn more about the Amazon EKS Node Monitoring Agent and node repair, visit the <a href="https://docs.aws.amazon.com/eks/latest/userguide/node-health.html">Amazon EKS documentation</a>.<a title="GitHub" href="https://github.com/aws/eks-node-monitoring-agent"></a></p>

Amazon EKS Node Monitoring Agent is now open source #eksautomode #eks #kubernetes

0 0 0 0
Preview
Running containerized hybrid nodes with Amazon Elastic Kubernetes Service EKS hybrid nodes is a feature of Amazon Elastic Kubernetes Service (EKS) that allows you to use an EKS managed control plane with worker nodes that reside outside of the AWS cloud. In this blog post, we’ll explore how to run a Docker container that connects to an EKS cluster as a hybrid node.

Running containerized hybrid nodes with Amazon Elastic Kubernetes Service #eks #kubernetes

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

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

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

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

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

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

0 0 0 0
Preview
Why AWS Still Wins (Despite GCP's Better Design) Why AWS Still Wins (Despite GCP's Better Design) Introduction This is a...

Why AWS Still Wins (Despite GCP's Better Design) Why AWS Still Wins (Despite GCP's Better Design) Introduction This is a follow-up to my previous articles: AWS SRE's First Day with GCP:...

#aws #gcp #eks #gke

Origin | Interest | Match

1 0 0 0
Storage Strategies for GenAI on Amazon EKS | Fast Model Caching for Kubernetes
Storage Strategies for GenAI on Amazon EKS | Fast Model Caching for Kubernetes

Storage Strategies for GenAI on Amazon EKS | Fast Model Caching for Kubernetes #eks #kubernetes

0 0 0 0
Learn about AI driven robotics training & how to simplify Kubernetes ops!
Learn about AI driven robotics training & how to simplify Kubernetes ops!

Learn about AI driven robotics training & how to simplify Kubernetes ops! #eks #kubernetes

0 0 0 0
Preview
The Clean Way to Access AWS, Azure, and GCP From Kubernetes (No Secrets, No Rotations)

A multi-cloud strategy, building a distributed system, your Kubernetes pods need secure, passwordless authentication across AWS, Azure, and GCP. #eks

0 0 0 0
Preview
Building Multi-Cluster EKS Infrastructure: From Dashboard Visibility to Hybrid Node Management Master multi-cluster EKS operations with unified dashboards, hybrid nodes, Terraform patterns, and ArgoCD GitOps for platform teams at scale.

Building Multi-Cluster EKS Infrastructure: From Dashboard Visibility to Hybrid Node Management Your Kubernetes footprint just grew from three clusters to fifteen across four AWS regions, and sudden...

#eks #kubernetes #aws #helm

Origin | Interest | Match

0 0 0 0
awslabs/amazon-eks-ami released AMI Release v20260209 What's Changed • chore: create file system fake by @fletcherw in https://github.com/awslabs/amazon-eks-ami/pull/2610 • feat(nodeadm): pass nvidia gpu startup labels to kubelet by @fletcherw in https://github.com/awslabs/amazon-eks-ami/pull/2607 • chore: clean up kubelet config file logic by @fletcherw in https://github.com/awslabs/amazon-eks-ami/pull/2613 • Add SELinux context restoration by @prasad0896 in https://github.com/awslabs/amazon-eks-ami/pull/2615 • Log collector collect NMA pod logs by @eddominguez in https://github.com/awslabs/amazon-eks-ami/pull/2612 • fix: set the runtime-cgroup flag by @fletcherw in https://github.com/awslabs/amazon-eks-ami/pull/2617 New Contributors • @eddominguez made their first contribution in https://github.com/awslabs/amazon-eks-ami/pull/2612 Full Changelog: https://github.com/awslabs/amazon-eks-ami/compare/v20260128...v20260209

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

0 0 0 0