This case study shows how debugging a kubectl 401 error on EKS revealed that a two-year-old static IAM credential file was shadowing a valid instance profile in the AWS credential chain.
More: https://ku.bz/Mxrqy_WJg
Post #1876
174
- Sep 23, 2026This week on Learn Kubernetes Weekly 202: 🔥 We Replaced etcd with Google Cloud Spanner 😌…
- Sep 22, 2026This article explains what an attacker can really do with leaked Kubernetes credentials, f…
- Sep 22, 2026"When an agent goes loose, you might find yourself: your S3 bucket has been deleted by mis…
- Sep 21, 2026This article walks through making a container image safe before it ever reaches the cloud,…
- Sep 21, 2026We just published Kubernetes Architecture in Financial Services, a free technical book abo…
- Sep 18, 2026This case study shows how a team ran ServiceNow's MID Server on EKS as a StatefulSet and f…