#eks — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #eks, aggregated by home.social.
-
Kubernetes — это эксплуатация, а не деплой. Мы шли к этому пониманию 7 лет
Kubernetes называют инструментом автоматизации. Ирония в том, что первые годы его эксплуатации в облаке — это история ручного труда: сертификаты, которые никто не обновлял, кластеры, которые деградировали молча, клиенты, которые ждали поддержки там, где мы предполагали самообслуживание. Мы начали делать managed Kubernetes в 2018 году, когда на российском рынке этого сервиса почти не существовало. Эта статья о том, что значит слово «managed» на самом деле — и какую архитектуру оно в итоге требует.
https://habr.com/ru/companies/k2tech/articles/1064272/
#devops #kubernetes #системное_администрирование #архитектура_системы #cluster_management #csi #managedkubernetes #node #control_plane #eks
-
Ctrl+Z has reached Kubernetes, and that’s really good news for some folks! AWS now lets you roll back EKS version upgrades because regret should never be part of your deployment strategy. #TheCloudPod #Kubernetes #TheCloudPod #EKS
https://www.thecloudpod.net/podcast/362-mechanical-turk-api/
-
Ctrl+Z has reached Kubernetes, and that’s really good news for some folks! AWS now lets you roll back EKS version upgrades because regret should never be part of your deployment strategy. #TheCloudPod #Kubernetes #TheCloudPod #EKS
https://www.thecloudpod.net/podcast/362-mechanical-turk-api/
-
Deploy a production-ready Amazon EKS cluster with managed node groups using the Terraform AWS EKS module. Automate worker node patching, scaling, and lifecycle management via launch templates. Includes IAM roles and eks_node_group resources. #terraform #aws #eks
https://www.valtersit.com/vault/terraform-aws-eks-module-with-managed-node-groups-3fac5d/
-
On dozens of occasions since 2019, monitoring stations have recorded simultaneous GPS interference across a vast area covering Europe, Canada and Greenland. The incidents - which typically last just a few seconds - appear to originate from a single source.
-
On dozens of occasions since 2019, monitoring stations have recorded simultaneous GPS interference across a vast area covering Europe, Canada and Greenland. The incidents - which typically last just a few seconds - appear to originate from a single source.
-
Today's Challenge:
auto upgrade 125 #eks / #kubernetes clusters from 1.33 to 1.34 and have zero problems.
-
Today's Challenge:
auto upgrade 125 #eks / #kubernetes clusters from 1.33 to 1.34 and have zero problems.
-
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
-
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
-
#AI разом з #AWS прийшли по душу #DevOps інженерів: анонсували
WS DevOps Agent. Що він мож:
- створювати CI/CD пайплайни
- дебажити невдалі дейплої
- пропонувати зміни в інфрастуктурі
- аналізувати логі та інціндети
- допомгати з Terraform та CloudFormation
- рекомендувати оптимізацію витрат
- виявляти та рекомендації по виправленню проблем з інфраструктурою.Це схоже на кастомного ШІ-агента, якого натренували вирішувати різні проблеми. Поки що перелік можливостей небагатий - во Франкфурті немає можливості #EKS підключити. Було б цікаво на прикладах подивитись, що він може. Будемо чекати
https://aws.amazon.com/devops-agent/ -
#AI разом з #AWS прийшли по душу #DevOps інженерів: анонсували
WS DevOps Agent. Що він мож:
- створювати CI/CD пайплайни
- дебажити невдалі дейплої
- пропонувати зміни в інфрастуктурі
- аналізувати логі та інціндети
- допомгати з Terraform та CloudFormation
- рекомендувати оптимізацію витрат
- виявляти та рекомендації по виправленню проблем з інфраструктурою.Це схоже на кастомного ШІ-агента, якого натренували вирішувати різні проблеми. Поки що перелік можливостей небагатий - во Франкфурті немає можливості #EKS підключити. Було б цікаво на прикладах подивитись, що він може. Будемо чекати
https://aws.amazon.com/devops-agent/ -
Учора до ночі провозився з #clouddriver від #Spinnaker: це компонент, який відповідає за опрос стану хмарних сервісів (Kubernetes кластера, Docker регістрі). Под почав крашитись після перевода на нову #EKS ноду та вижирати доступні CPU ресурси.
Раніше я виявив, що така поведінка через накопичення команд опросу EKS кластерів та Docker регістрі. Справа у тому, що для обох процесів треба отрмати #AWS токени.
Для EKS це була команда:
```
aws eks get-token --cluster-name XXX --output json
```
Але в поді іноді її виконання займало до 10 секунд. AWS CLI написаний на #Python, тому працює повільно. Заміним цю команду на aws-iam-authenticator, який написаний на #Go та працює в 5-6 разів швидше:
```
aws-iam-authenticator token -i XXX
```
Наступна проблема з #Docker. Команда автентифікації була
```
aws ecr get-authorization-token --output text --query 'authorizationData[].authorizationToken' | base64 -d | sed 's/^AWS://'
```
Ця команда теж іноді по 10-15 секунд виконувалась та віджирала CPU. Токен дійсний на 12 годин, але опрос запускається кожні 5 хвилин, тому є сенс кеширувати його. Вигадав таку команду, не лякайтесь ;-) Її треба було саме однорядкову, тому що вона буде додана в #YAML конфіг #Spinnaker:
```
[ ! -f /tmp/ecr-token ] || \
[ $(( $(date +%s) - $(date +%s -r /tmp/ecr-token) )) -gt 36000 ] \
&& aws ecr get-authorization-token --output text \
--query "authorizationData[].authorizationToken" | \
base64 -d | sed "s/^AWS://" > /tmp/ecr-token; \
cat /tmp/ecr-token
```
Вона перевіряє наявність файла, якщо нема кешированого токена створює його та оновлює його якщо він старий, після просто видає його.
Після цього команди перестали накопичуватись на навантаження на под значнно впало.
Ліг спати щасливий як ніколи ;-)
#devops #troubleshooting -
AI-powered event response for Amazon EKS
https://aws.amazon.com/blogs/architecture/ai-powered-event-response-for-amazon-eks/
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 -
AI-powered event response for Amazon EKS
https://aws.amazon.com/blogs/architecture/ai-powered-event-response-for-amazon-eks/
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 -
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
https://heyjoshlee.medium.com/the-80-20-of-aws-the-services-that-actually-matter-13509ff90115
-
My dear #fediverse, does someone has a nice #ansible repo to setup an #EKS on aws? If I can avoid to start from scratch 😅
-
My dear #fediverse, does someone has a nice #ansible repo to setup an #EKS on aws? If I can avoid to start from scratch 😅
-
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!
https://nbailey.ca/post/backup-k8s-cronjob/
#kubernetes #backup #backups #cronjob #postgres #postgresql #kafka #aws #s3 #eks #bash #terraform #sysadmin #linux #blog #blogpost
-
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!
https://nbailey.ca/post/backup-k8s-cronjob/
#kubernetes #backup #backups #cronjob #postgres #postgresql #kafka #aws #s3 #eks #bash #terraform #sysadmin #linux #blog #blogpost
-
A multi-cloud strategy, building a distributed system, your Kubernetes pods need secure, passwordless authentication across AWS, Azure, and GCP. https://hackernoon.com/the-clean-way-to-access-aws-azure-and-gcp-from-kubernetes-no-secrets-no-rotations #eks
-
A multi-cloud strategy, building a distributed system, your Kubernetes pods need secure, passwordless authentication across AWS, Azure, and GCP. https://hackernoon.com/the-clean-way-to-access-aws-azure-and-gcp-from-kubernetes-no-secrets-no-rotations #eks
-
Як так виходить, що DevOps кандидат, який працював декілька років в #EPAM, потім в #LuxSoft, а зараз знов в #EPAM, маючи декілька сертифікації #AWS (отриманих в том же ЕПАМ), а також сертифікацію по #Kubernetes #SKAD, не знає відповіді на питання:
- що треба зробити в новому кластері #EKS щоб створити балансер для деплоймента?
Не без труда кандидат відповів, що треба зробити #ingress з типом #nginx, але не зміг відповісти чому після цього балансер не створився (бо в новому кластері немає nginx ingress controller). Ну, й я б ставив ALB ingress controller, не nginx.
При чому це був типу strong middle по скілах. Мені здається, що у мене стронг джуни знають відповідь, бо кожний грається з кластером та самі усе потрібне в нього ставлять. -
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.
-
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.
-
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 teamsDetails here 👉 https://bit.ly/49xaKQy
-
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 teamsDetails here 👉 https://bit.ly/49xaKQy
-
Learn how to use EKS Pod Identity principal tags to isolate each tenant’s S3 access with a single shared IAM role. https://hackernoon.com/how-to-use-eks-pod-identity-to-isolate-tenant-data-in-s3-with-a-shared-iam-role #eks
-
Learn how to use EKS Pod Identity principal tags to isolate each tenant’s S3 access with a single shared IAM role. https://hackernoon.com/how-to-use-eks-pod-identity-to-isolate-tenant-data-in-s3-with-a-shared-iam-role #eks
-
Last but certainly not least, my roundup of all the #AWS #CloudOps news from #reinvent, including the new #multicloud Interconnect, #EKS Capabilities, #observability and #logmanagement updates for #cloudwatch, and more. https://www.techtarget.com/searchcloudcomputing/news/366636053/AWS-CloudOps-hones-multi-cloud-support-for-AI-resilience
-
Last but certainly not least, my roundup of all the #AWS #CloudOps news from #reinvent, including the new #multicloud Interconnect, #EKS Capabilities, #observability and #logmanagement updates for #cloudwatch, and more. https://www.techtarget.com/searchcloudcomputing/news/366636053/AWS-CloudOps-hones-multi-cloud-support-for-AI-resilience
-
Как мы ускорили ввод новых узлов до 40 секунд: надежная работа на spot-инстансах в Kubernetes с Karpenter
В нашей практике DevOps мы столкнулись с задачей оптимизации Kubernetes-кластера в AWS, включая перевод нагрузки на ARM64-инстансы с процессорами Graviton и эффективное использование spot-инстансов. Благодаря Amazon EKS и Karpenter нам удалось ускорить ввод новых узлов до всего 40 секунд и успевать переносить нагрузку при отборе узлов со стороны AWS. При этом мы сохранили привычный набор инструментов Deckhouse для мониторинга и управления — статья подробно рассказывает о нашем опыте и решениях.
https://habr.com/ru/companies/flant/articles/955302/
#kubernetes #karpenter #eks #amd64 #nodepool #optimization #graviton #оптимизация #spot_instances #spotинстанс
-
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.
-
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.
-
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.
-
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.
-
初心者でも構築できる！EKS道場【Day14】完走おめでとう！14日間のEKS修行を振り返ろう
https://qiita.com/Yoshi1001/items/9e3c016d675268ba33b7?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
初心者でもわかる！EKS道場【Day12】Prometheus + Grafana を用いたモニタリングとダッシュボード作成の道
https://qiita.com/Yoshi1001/items/0202e509e3d2c179d561?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
The AWS EKS Terraform module has been updated to 21 (see https://github.com/terraform-aws-modules/terraform-aws-eks/releases/tag/v21.0.0). 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 (https://docs.aws.amazon.com/eks/latest/userguide/access-entries.html).
I upgraded my clusters and did some cleanup with the removal of AWS auth module.
-
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
-
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
-
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: https://youtu.be/AlOPjAB-5v4
-
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: https://youtu.be/AlOPjAB-5v4
-
#AmazonEKSDashboard is now Generally Available!
Get unified visibility across your #Kubernetes clusters deployed in multiple AWS regions and accounts.
Learn more: https://bit.ly/45nExJU