In a SaaS environment, the compute, storage, and bandwidth resources are often shared among tenants, but this makes it challenging to deduce per tenant cost. A SaaS application running on a Kubernetes cluster on AWS adds a layer of further complexity as far as calculating the per tenant cost. Kubernetes is great at abstracting away the underlying pool of hardware. It almost gives us an illusion of having access to a single large compute resource.

Provision a Kubernetes Cluster in AWS. Configure the AWS CLI to provide IAM credentials to Terraform, clone an example repository, and deploy the cluster. Configure kubectl and the Kubernetes dashboard. Finally destroy the cluster.

To meet user demand, dynamic HTTP-based applications require constant scaling of Kubernetes pods. For applications exposed through Kubernetes ingress objects, the AWS Application Load Balancer (ALB) distributes incoming traffic automatically across the newly scaled replicas. When Kubernetes applications scale down due to a decline in demand, certain situations will result in brief interruptions for end […]

Overview Data transfer costs can play a significant role in determining the overall design of a system. Amazon Elastic Container Registry (Amazon ECR), Amazon Elastic Container Service (Amazon ECS), and Amazon Elastic Kubernetes Service (Amazon EKS) can incur data transfer charges depending on a variety of factors. It can be difficult to visualize what that means […]

Data transfer charges are often overlooked when operating Amazon Elastic Kubernetes Service (Amazon EKS) clusters; understanding these charges would help reduce cost while operating your workload on Amazon EKS at production scale. Common scenarios for data transfer charges on EKS Understanding general data transfer charges on AWS will help you better understand the EKS networking […]

Networking plugin repository for pod networking in Kubernetes using Elastic Network Interfaces on AWS - amazon-vpc-cni-k8s/README.md at master · aws/amazon-vpc-cni-k8s

Contribute to awslabs/soci-snapshotter development by creating an account on GitHub.

Topology Aware Hints (TAH) is a feature that available in Amazon EKS version 1.24. It’s intended to provide a mechanism that attempts to keep traffic closer to its origin within the same AZ on in another location. In this post, we’ll explore how this feature can be used with Amazon EKS, its effects on how traffic is routed between pods within an Amazon EKS cluster when using multiple AZs, and whether this functionality allows Amazon EKS customers to optimize the latency and inter-AZ data transfer costs in this architecture.

This post was co-authored by Nikhil Sharma and Ravishen Jain of OLX Autos Introduction We, at OLX Autos run more than 100 non-production (non-prod) environments in parallel for different use-cases on home grown Internal Developer Platform (IDP), ORION. ORION runs on Amazon Elastic Kubernetes Service (Amazon EKS). Each of the Autos environment consists of at […]

EKS Node Viewer. Contribute to awslabs/eks-node-viewer development by creating an account on GitHub.

AWS Fargate is a serverless compute engine for containerized workloads running on Amazon Elastic Container Service (Amazon ECS) and Amazon Elastic Kubernetes Service (Amazon EKS). Once a containerized workload has been scheduled by a container orchestrator, AWS Fargate provides a serverless compute environment to run that workload removing the operational overhead to secure, scale, and […]

Hi, I am currently attempting to create a simple AWS EKS cluster and the nodes always run into the creation failure health issue. Could someone point me in the right direction? Details below: Envir...

This post is contributed by Chris Foote, Sr. EC2 Spot Specialist Solutions Architect Running your Kubernetes and containerized workloads on Amazon EC2 Spot Instances is a great way to save costs. Kubernetes is a popular open-source container management system that allows you to deploy and manage containerized applications at scale. AWS makes it easy to run […]

This is official Amazon Web Services (AWS) documentation for Amazon Elastic Kubernetes Service (Amazon EKS). Amazon EKS is a managed service that makes it easy for you to run Kubernetes on AWS without needing to install and operate your own Kubernetes clusters. Kubernetes is an open-source system for automating the deployment, scaling, and management of containerized applications.

Mac Chaffee's tech blog

Overview Karpenter is a high-performance Kubernetes cluster autoscaler that can help you autoscale your groupless nodes by letting you schedule layered constraints using the Provisioner API. Karpenter also makes node upgrades easy through the node expiry TTL value ttlSecondsUntilExpired. This blog post will walk you through all of the steps to make this possible, and […]

Just-in-time Nodes for Any Kubernetes Cluster

GitHub Gist: instantly share code, notes, and snippets.

FEATURE STATE: Kubernetes v1.21 [deprecated] Note: This feature, specifically the alpha topologyKeys API, is deprecated since Kubernetes v1.21. Topology Aware Hints, introduced in Kubernetes v1.21, provide similar functionality. Service Topology enables a service to route traffic based upon the Node topology of the cluster. For example, a service can specify that traffic be preferentially routed to endpoints that are on the same Node as the client, or in the same availability zone.

FEATURE STATE: Kubernetes v1.23 [beta] Topology Aware Hints enable topology aware routing by including suggestions for how clients should consume endpoints. This approach adds metadata to enable consumers of EndpointSlice and / or Endpoints objects, so that traffic to those network endpoints can be routed closer to where it originated. For example, you can route traffic within a locality to reduce costs, or to improve network performance. Motivation Kubernetes clusters are increasingly deployed in multi-zone environments.

Overview Karpenter is a dynamic, high performance cluster auto scaling solution for the Kubernetes platform introduced at re:Invent 2021. Customers choose an auto scaling solution for a number of reasons, including improving the high availability and reliability of their workloads at the same reduced costs. With the introduction of Amazon EC2 Spot Instances, customers can […]

Networking plugin repository for pod networking in Kubernetes using Elastic Network Interfaces on AWS - amazon-vpc-cni-k8s/eni-and-ip-target.md at master · aws/amazon-vpc-cni-k8s

FEATURE STATE: Kubernetes v1.18 [stable] This page provides an overview of NodeLocal DNSCache feature in Kubernetes. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgrounds:

Networking plugin repository for pod networking in Kubernetes using Elastic Network Interfaces on AWS - amazon-vpc-cni-k8s/troubleshooting.md at master · aws/amazon-vpc-cni-k8s

AWS EKS Review

What are unsafe sysctls?

Packer configuration for building a custom EKS AMI - amazon-eks-ami/bootstrap.sh at master · awslabs/amazon-eks-ami