home.social

#eks — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #eks, aggregated by home.social.

  1. Today's Challenge:

    auto upgrade 125 #eks / #kubernetes clusters from 1.33 to 1.34 and have zero problems.

  2. todays challenge:

    provide some #python output to categorize and provide upgrade paths for obscenely old #eks instances that are going EOL in weeks. #kubernetes #aws #terraform

  3. #AI разом з #AWS прийшли по душу #DevOps інженерів: анонсували
    WS DevOps Agent. Що він мож:
    - створювати CI/CD пайплайни
    - дебажити невдалі дейплої
    - пропонувати зміни в інфрастуктурі
    - аналізувати логі та інціндети
    - допомгати з Terraform та CloudFormation
    - рекомендувати оптимізацію витрат
    - виявляти та рекомендації по виправленню проблем з інфраструктурою.

    Це схоже на кастомного ШІ-агента, якого натренували вирішувати різні проблеми. Поки що перелік можливостей небагатий - во Франкфурті немає можливості #EKS підключити. Було б цікаво на прикладах подивитись, що він може. Будемо чекати
    aws.amazon.com/devops-agent/

  4. Od piątku 13 marca nasze kosy spalinowe niestrudzenie pracowały na zboczach Góry Sosnówki. Na pierwszej linii stanęło dwoje dzielnych kosiarzy – Magda Galus i Bartłomiej Bart Nurczyński. Wieczorem dotarły posiłki i przez weekend działaliśmy już w całkiem sporym zespole wolontariuszek i wolontariuszy 💪
    W akcji czynnej ochrony murawy kserotermicznej wzięło udział łącznie 29 osób!
    Dzięki współpracy z Regionalnym Centrum Wolontariatu w Kielcach - Europejski Korpus Solidarności Sosnówka gościła wolontariuszy z:
    🇦🇿 Azerbejdżanu
    🇹🇷 Turcji
    🇮🇹 Włoch
    🇫🇷 Reunion (Francja)
    Naszym wolontariuszem był również Prof. Jürgen Dengler z 🇩🇪 Niemiec.
    Dziękujemy za niesamowitą atmosferę podczas akcji! I cieszymy się, że pozytywny przekaz o ochronie polskiej przyrody idzie w świat – i to dosłownie!
    Razem możemy więcej! 🤝
    Marcowa akcja czynnej ochrony muraw kserotermicznych to efekt połączonych sił Centrum Ochrony Mokradeł oraz naszego lokalnego partnera Fundacji Vernalis.
    Fundacja Vernalis to organizacja założona przez wieloletniego członka Centrum Ochrony Mokradeł - Bartłomieja Nurczyńskiego. Fundacja to młoda, pełna pasji ekipa, która wykonuje kawał dobrej roboty na lokalnym podwórku.
    Dziękujemy za Wasze zaangażowanie, wysiłek włożony w ochronę murawy, inspirujące rozmowy, dobry nastrój i wspólnie spędzony czas! 💚
    #ochronaprzyrody #Sosnówka #Wolontariat #FundacjaVernalis #Kielce #CentrumWolontariatuKielce #EuropejskiKorpusSolidarności #EKS #Ekologia #ActiveConservation #NatureLovers #murawa #ngo

  5. AI-powered event response for Amazon EKS
    aws.amazon.com/blogs/architect
    AWS DevOps Agent is a fully managed autonomous AI Agent that resolves and proactively prevents incidents, continuously improving reliability and performance of applications in AWS, multicloud, and hybrid environments.
    #AWS #AwsDevOpsAgent #EKS #AI

  6. AWS has 200+ services. Most companies use about 15. The same ones show up in every project: EC2, S3, Lambda, RDS, DynamoDB, API Gateway, CloudFront, SQS, SNS, CloudWatch.
    That handles 80% of everything. Wrote a guide covering just the ones that matter.

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

    heyjoshlee.medium.com/the-80-2

  7. My dear #fediverse, does someone has a nice #ansible repo to setup an #EKS on aws? If I can avoid to start from scratch 😅

    #sysadmin #devops #linux #opensource #foss

  8. I wrote up a quick how-to for running data backups inside a Kubernetes cluster using CronJobs. I wish it was as simple as a crontab + bash script like the olden days, but it works well enough. It is nice how declarative and stateless it is though!

    nbailey.ca/post/backup-k8s-cro

    #kubernetes #backup #backups #cronjob #postgres #postgresql #kafka #aws #s3 #eks #bash #terraform #sysadmin #linux #blog #blogpost

  9. A multi-cloud strategy, building a distributed system, your Kubernetes pods need secure, passwordless authentication across AWS, Azure, and GCP. hackernoon.com/the-clean-way-t #eks

  10. So, like, #AWS #EKS.. the kernel defaults for the EKS nodes are by in large, consistent with 10mbps half duplex networking on a workstation. Judging by how many hoops you need to jump through to manage sysctl's on EKS and #K8S in general, I can only see one of two possible explanations:

    1) There's some magic kernel module installed for EKS or K8S that obviates the need to tune the kernel for server workloads.

    2) We stopped caring about synchronizing the network stack to the network it's connected to and the use of the server because it's cloud and/or K8S and wasting resources is just what we do for the convenience of buying Bezos a new spaceship or super yacht.

    I see a ton of network implicated slowdowns in pipelines on EKS.There's a fuckton of dropped packets, retransmits, and context switches. We can tell the kernel to spend a bit more time per cycle on processing network packets. We can increase the default and max buffer sizes for TCP and UDP sockets which are transmitting MASSIVE amounts of data for "15GBps" bursts. We can adjust the TCP timeout to match the AWS network to prevent half-open connections. We can increase the kernel backlog depth for busy services. Maybe, I mean, **I** can. It's a twisted, gnarly, and wholly undocumented nightmare for K8S and EKS mostly involving logging into the EKS nodes and manually setting the sysctls one at a time.. Does anyone have a better way? I've yet to read something that demonstrated how to do this in some sane manner.. FWIW, it was one `file` and one `exec` resource in Puppet to adjust an entire fleet consistently.

  11. Salesforce just completed a massive migration: 1,000+ Amazon EKS clusters moved from Kubernetes Cluster Autoscaler to Karpenter!

    The impact❓
    ⇨ Faster scaling ⇨ Simpler operations ⇨ Lower costs ⇨ More flexible, self-service infrastructure for internal dev teams

    Details here 👉 bit.ly/49xaKQy

    #Kubernetes #AWS #EKS #InfoQ

  12. Learn how to use EKS Pod Identity principal tags to isolate each tenant’s S3 access with a single shared IAM role. hackernoon.com/how-to-use-eks- #eks

  13. Как мы ускорили ввод новых узлов до 40 секунд: надежная работа на spot-инстансах в Kubernetes с Karpenter

    В нашей практике DevOps мы столкнулись с задачей оптимизации Kubernetes-кластера в AWS, включая перевод нагрузки на ARM64-инстансы с процессорами Graviton и эффективное использование spot-инстансов. Благодаря Amazon EKS и Karpenter нам удалось ускорить ввод новых узлов до всего 40 секунд и успевать переносить нагрузку при отборе узлов со стороны AWS. При этом мы сохранили привычный набор инструментов Deckhouse для мониторинга и управления — статья подробно рассказывает о нашем опыте и решениях.

    habr.com/ru/companies/flant/ar

    #kubernetes #karpenter #eks #amd64 #nodepool #optimization #graviton #оптимизация #spot_instances #spotинстанс

  14. Как мы ускорили ввод новых узлов до 40 секунд: надежная работа на spot-инстансах в Kubernetes с Karpenter

    В нашей практике DevOps мы столкнулись с задачей оптимизации Kubernetes-кластера в AWS, включая перевод нагрузки на ARM64-инстансы с процессорами Graviton и эффективное использование spot-инстансов. Благодаря Amazon EKS и Karpenter нам удалось ускорить ввод новых узлов до всего 40 секунд и успевать переносить нагрузку при отборе узлов со стороны AWS. При этом мы сохранили привычный набор инструментов Deckhouse для мониторинга и управления — статья подробно рассказывает о нашем опыте и решениях.

    habr.com/ru/companies/flant/ar

    #kubernetes #karpenter #eks #amd64 #nodepool #optimization #graviton #оптимизация #spot_instances #spotинстанс

  15. Как мы ускорили ввод новых узлов до 40 секунд: надежная работа на spot-инстансах в Kubernetes с Karpenter

    В нашей практике DevOps мы столкнулись с задачей оптимизации Kubernetes-кластера в AWS, включая перевод нагрузки на ARM64-инстансы с процессорами Graviton и эффективное использование spot-инстансов. Благодаря Amazon EKS и Karpenter нам удалось ускорить ввод новых узлов до всего 40 секунд и успевать переносить нагрузку при отборе узлов со стороны AWS. При этом мы сохранили привычный набор инструментов Deckhouse для мониторинга и управления — статья подробно рассказывает о нашем опыте и решениях.

    habr.com/ru/companies/flant/ar

    #kubernetes #karpenter #eks #amd64 #nodepool #optimization #graviton #оптимизация #spot_instances #spotинстанс

  16. Как мы ускорили ввод новых узлов до 40 секунд: надежная работа на spot-инстансах в Kubernetes с Karpenter

    В нашей практике DevOps мы столкнулись с задачей оптимизации Kubernetes-кластера в AWS, включая перевод нагрузки на ARM64-инстансы с процессорами Graviton и эффективное использование spot-инстансов. Благодаря Amazon EKS и Karpenter нам удалось ускорить ввод новых узлов до всего 40 секунд и успевать переносить нагрузку при отборе узлов со стороны AWS. При этом мы сохранили привычный набор инструментов Deckhouse для мониторинга и управления — статья подробно рассказывает о нашем опыте и решениях.

    habr.com/ru/companies/flant/ar

    #kubernetes #karpenter #eks #amd64 #nodepool #optimization #graviton #оптимизация #spot_instances #spotинстанс

  17. Just throwing this out there, anyone else using #eks for their #kubernetes environments and have CI/CD (and gitops of some flavor) that spins up eks clusters?

    It’s a hard 15m wait for the control plane to come up. Then if you’re using the addon api another almost definite 15m hard wait at least once.

    We heavily use pod security groups and nlbs, so using #kind or #talosLinux could work, but would likely be brittle.

    Just really want to stop eating that 15-30+ minutes.

    #devops #sysadmin

  18. High availability in EKS isn’t about running three replicas behind a Load Balancer. It’s about designing for invisible infrastructure failures: Spot loss, IP exhaustion, scaling bottlenecks, and blind spots in observability. These failures don’t crash your app — they silently degrade it.

    #kubernetes #k8s #aws #devops #technology #eks

  19. Does anyone in the world know how to get AWS fargate logs to AWS Cloudwatch reliably with FILTERING?

    I have found ways to get 100% of logs across every pod, but any time I try to filter using the docs, and 3 different LLMs complete failure.

    I know this is an AWS shithole, and am moving to work around it, but this seems like basic functionality that should work.

    #aws #container #kubernetes #eks

  20. Implement monitoring for Amazon EKS with managed services
    aws.amazon.com/blogs/architect
    EKS offers compelling solutions with EKS Auto Mode and AWS Fargate, each designed for different use cases. This solution demonstrates building an EKS platform that combines flexible compute options with enterprise-grade observability using AWS native services and OpenTelemetry.
    #AWS #EKS #ADOT #AmazonManagedServiceForPrometheus #CloudWatch

  21. The AWS EKS Terraform module has been updated to 21 (see github.com/terraform-aws-modul). It unblocks support of AWS terraform provider 6.

    The new module has quite a lot of breaking changes, and it was time to migrate from the removed AWS auth module to the new recommended EKS access entries to grant users access to Kubernetes API (docs.aws.amazon.com/eks/latest).

    I upgraded my clusters and did some cleanup with the removal of AWS auth module.

  22. Anybody worked out if it's possible to access AWS Certificate Manager certs in EKS Kubernetes as a TLS Secret? (I need to terminate in the pod not the LoadBalancer to access SNI)

    It feels like it should be possible with the Secrets Store CSI driver with the AWS plugin, but it looks it only has access to AWS Secrets Manager. I don't really want to have to export and import every time they need renewing

    #TLS #AWS #EKS #kubernetes #Secrets #k8s

  23. Optimize your #EKS cluster with Karpenter + Spot!

    Discover how to cut cloud costs and boost efficiency using #Karpenter with Spot Instances in #AWS EKS. Watch Le Kien Truc share a production-ready guide from real-world experience.

    Click here: youtu.be/AlOPjAB-5v4

  24. #AmazonEKSDashboard is now Generally Available!

    Get unified visibility across your #Kubernetes clusters deployed in multiple AWS regions and accounts.

    Learn more: bit.ly/45nExJU

    #InfoQ #AWS #EKS #Observability

  25. Upgrading from 1.31 to 1.32 on all my clusters went really smoothly. tool (github.com/doitintl/kube-no-tr) was helpful and the second check was done using the AWS own tool to detect API deprecated usage. Using to manage the nodes does provide high value when it’s time to upgrade to a new version.

  26. Kubernetes Storage Without the Pain: Simplyblock in 15 Minutes

    Whether you're building a high-performance cloud-native app or running data-heavy workloads in your own infrastructure, persistent storage is necessary. In Kubernetes, this means having storage that survives pod restarts, failures, and rescheduling events—and that’s precisely what simplyblock brings to the table: blazing-fast, scalable, and software-defined storage with cloud economics. A hyper-converged storage solution, like simplyblock enables Kubernetes storage par excellence. In […]

    simplyblock.io/blog/install-si

  27. 🥳 Hooray! 🤯 Another #thrilling 12-minute #read on *yet another* way to deploy #Kubernetes with #zero downtime! 🎉 Because clearly, the world was lacking in solutions for #AWS #EKS deployments... 🙄 Thanks, Jakob, for enlightening us with your revolutionary #insights that nobody asked for! 🌟
    glasskube.dev/blog/kubernetes- #downtime #deployment #HackerNews #ngated

  28. 📣 Hot off the press! 📣 The latest issue of my #LetsMakeCloud newsletter is live.

    🔍 Get the lowdown on the new features of HashiCorp's Terraform 1.5

    🔑 Learn how to streamline your Amazon EKS authentication process with Pinniped

    🛠️ And for those lost in the sea of open-source monitoring tools, a handy comparison of 10 top options, complete with pros and cons

    Don't miss out! 👉 letsmakecloud.beehiiv.com/p/is #CloudComputing #AWS #EKS #Terraform #Pinniped #MonitoringTools