|
- Best practices for running Spark on Amazon EKS | Containers
The ConfigMap used for both driver and executors Pod Template contains two Pod specs specifying different Node Selector for Spark driver and executors, and a Spot Toleration for the executors (the Pod template is mounted in a Kubernetes Volume as described previously)
- Multi-tenant design considerations for Amazon EKS clusters
With this taint, nodes that do not have a toleration for this taint, will not be scheduled on this Node Group Another possibility is to use AWS Fargate on EKS
- Deploying Amazon EKS Windows managed node groups
Note: We include a toleration within our deployment manifest that allows the scheduler to schedule pods with matching taints, which in our case, is os=windows Node selector is applied within a single template asking the scheduler to run the pods on a set of nodes
- Automating Amazon EKS cluster testing with custom machine images
Provision the “Test” worker node group by running the Test AMI and deploy a test application When test is set to true the nodes are tainted with DeployGroup=Test:NoSchedule The test application is being deployed with tolerations The toleration is set in this file: scripts nginx-deployment-testapp yaml
- Amazon EKS add-ons: Advanced configuration | Containers
This post is a follow-up to our previous post, Amazon EKS add-ons preserve customer edits Introduction In October 2022, the Amazon Elastic Kubernetes Service (Amazon EKS) add-ons team introduced the ability to preserve edits, enabling customers to safely modify the configuration of Amazon EKS add-ons by using the Kubernetes application programming interface (API) This enhancement […]
- Deploying Karpenter Nodes with Multus on Amazon EKS
2 Evaluating scheduling constraints (resource requests, nodeselectors, affinities, toleration, and topology spread constraints) requested by the pods; 3 Provisioning nodes that meet the requirements of the pods; and 4 Removing the nodes when the nodes are no longer needed
- Amazon EKS and Spot Instances in action at Delivery Hero
Since Spot Instances can be interrupted at any time (when Amazon EC2 needs the capacity back), users will often taint their preemptible nodes, requiring an explicit pod toleration to the preemption behavior
- Managing Team Workloads in shared Amazon EKS cluster using Loft . . .
Uses node pool taint with vCluster name Adds toleration to syncer Makes sure that pods synced by vCluster are scheduled on designated NodePool nodes Target Node Pool Based on vCluster Pod Labels: Uses exists operator in Karpenter nodePool spec requirements Allows fine-grained control over which node pool a vCluster’s pods are scheduled on
|
|
|