Learn how to securely store and retrieve database credentials, API keys, and tokens in Amazon EKS by integrating AWS Secrets Manager with the Secrets Store CSI driver, configuring IAM Roles for Service Accounts, and mounting secrets via a SecretProviderClass, all illustrated with step‑by‑step commands and examples.
This guide shows how to enable EKS audit logging, filter for risky kubectl exec and port-forward actions, create CloudWatch metric filters, and set up real‑time alarms so any high‑risk command triggers an immediate notification.
This guide explains why an AWS EKS ALB Ingress with target‑type ip can mark pods as unhealthy despite internal connectivity, and provides step‑by‑step instructions to correctly configure the ALB and pod security groups, health‑check sources, NACLs, and debugging tips.
This article explains the AWS CloudWatch Container Insights pod_cpu_utilization metric, its calculation as a percentage of node CPU, compares it with kubectl top, and introduces the related Pod CPU utilization over pod limit metric for effective Kubernetes resource monitoring.
The author recounts the high hopes and subsequent frustrations of adopting the community‑maintained terraform‑aws‑eks module for AWS EKS, detailing hidden complexities, limited AI assistance, and practical lessons on embracing complexity, critical use of open‑source modules, and the importance of rest during tough debugging sessions.
This guide explains why an EKS cluster can fail to provision EBS volumes due to a missing OIDC provider, describes the role of the aws_iam_openid_connect_provider resource, and provides step‑by‑step Terraform code to create the provider, configure IAM roles, and verify the fix.
When using AWS EKS API authentication, many users encounter the “the server has asked for the client to provide credentials” error despite having AdministratorAccess, because the newer API mode requires explicit Access Entries for each IAM identity, a detail often missed in documentation and troubleshooting.
This step‑by‑step guide walks you through AWS EKS core concepts, cluster provisioning with eksctl, kubectl configuration, node monitoring, taints and tolerations, GitLab deployment via Helm, persistent storage with EBS, optional object storage, Istio service‑mesh installation, and troubleshooting API server access issues.
This guide explains why an Istio Ingress Gateway on AWS EKS often remains in EXTERNAL-IP pending state, analyzes root causes such as subnet tags, IAM permissions, and resource quotas, and provides step‑by‑step remediation to get a functional load balancer.
This article presents OPPO's CloudCamel solution for big data cost optimization on public cloud, detailing domestic and overseas architectures, elastic redesigns, component innovations, migration considerations, performance metrics, and future technical and operational directions.
This article explains why EKS clusters can run out of pod IP addresses or have low pod density per node, describes how AWS ENI and address‑prefix features affect IP allocation, and provides practical steps such as secondary CIDR allocation and subnet reservation to overcome these limits.
This article explains how Kubernetes nodes reserve CPU and memory for the operating system, system daemons, and eviction thresholds, showing concrete examples across AWS EKS, Azure AKS, and Google GKE, and provides tools to inspect and calculate these hidden resource costs.
This article details Ctrip’s migration of its hotel direct‑connect service to AWS, describing the background challenges, cloud‑native architectural redesign with EKS, bandwidth and latency optimizations, use of spot instances, DNS caching, cross‑AZ traffic reduction, and the resulting performance and cost benefits.
This guide walks through installing kubectl on an EC2 instance, configuring the kubeconfig to point to a specific Amazon EKS cluster, and verifying the setup by listing cluster nodes, providing all commands and expected outputs.
Tencent Cloud’s Elastic Container Service (EKS) delivers a nodeless, Kubernetes‑compatible platform that blends serverless convenience with serverful flexibility, letting users migrate existing clusters with a single click, run hybrid and big‑data workloads across virtual nodes, and anticipate future usage‑based billing for truly elastic scaling.
