content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
on a cluster with 3 c5.large nodes (3 ENIs and max 10 IPs per ENI), when the cluster starts up and has 2 CoreDNS pods, the CNI will consume 50 IP addresses and keep 43 IPs in warm pool. The warm pool enables faster Pod launches when the application is deployed. Node 1 (with CoreDNS pod): 2 ENIs, 20 IPs assigned Node 2 ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
-0.024891255423426628,
-0.0035699314903467894,
0.002599547151476145,
0.0016811685636639595,
0.03469811752438545,
-0.04204890877008438,
0.0005575185641646385,
-0.058093566447496414,
-0.005654006730765104,
0.04170556738972664,
-0.023735184222459793,
-0.0892670601606369,
0.058943942189216614,
... | 0.16479 |
frequently used fields such as WARM\_ENI\_TARGET, WARM\_IP\_TARGET, and MINIMUM\_IP\_TARGET are not managed and will not be reconciled. The changes to these fields will be preserved upon updating of the add-on. We suggest testing the add-on behavior in your non-production clusters for a specific configuration before up... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
-0.012989449314773083,
-0.016390327364206314,
0.052739813923835754,
0.0355687215924263,
0.07325688004493713,
0.0092091653496027,
-0.05113046616315842,
-0.10444999486207962,
0.03031045012176037,
0.07811152935028076,
0.05047029256820679,
-0.06938916444778442,
0.03975510969758034,
-0.07396815... | 0.083909 |
is a long-running process responsible for IP address management at the node level. The aws-node runs in `hostNetwork` mode and allows access to the loopback device, and network activity of other pods on the same node. The aws-node init-container runs in privileged mode and mounts the CRI socket allowing the Daemonset t... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
-0.012410355731844902,
0.06910764425992966,
-0.006750825326889753,
-0.00037085628719069064,
0.065392404794693,
0.013555284589529037,
0.012724020518362522,
-0.042612429708242416,
0.0361546128988266,
0.12290485948324203,
-0.042717963457107544,
-0.055916376411914825,
0.03973336145281792,
-0.0... | 0.101325 |
iptables forward policy to ACCEPT under https://github.com/awslabs/amazon-eks-ami/blob/master/files/kubelet.service#L8[kubelet.service]. Many systems set the iptables forward policy to DROP. You can build custom AMI using https://packer.io/intro/why.html[HashiCorp Packer] and a build specification with resources and co... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
-0.030050525441765785,
0.05205415561795235,
-0.010915625840425491,
-0.07899795472621918,
0.01966979168355465,
0.010501757264137268,
-0.05592691898345947,
0.006683131214231253,
0.05790381878614426,
0.03467531502246857,
0.04726565256714821,
-0.07485876977443695,
0.04797513782978058,
-0.05972... | 0.073703 |
//!!NODE\_ROOT [."topic"] [[sgpp,sgpp.title]] = Security Groups Per Pod :info\_doctype: section :info\_title: Security Groups Per Pod :info\_abstract: Security Groups Per Pod :info\_titleabbrev: Security Groups Per Pod :imagesdir: images/networking/ [abstract] -- Security Groups Per Pod -- TIP: https://aws-experience.c... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/sgpp.adoc | mainline | aws-eks-best-practices | [
-0.007252009119838476,
0.031934745609760284,
-0.032486021518707275,
0.021411193534731865,
0.11570609360933304,
-0.010002953000366688,
0.035965729504823685,
-0.04839736223220825,
0.0995883196592331,
-0.012921660207211971,
0.05382048338651657,
-0.04542747139930725,
0.06123163178563118,
-0.05... | 0.198432 |
max-pods for nodes. When security groups for Pods are used in combination with https://docs.aws.amazon.com/eks/latest/userguide/cni-custom-network.html[custom networking], the security group defined in security groups for Pods is used rather than the security group specified in the ENIConfig. As a result, when custom n... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/sgpp.adoc | mainline | aws-eks-best-practices | [
0.06529010832309723,
0.048916008323431015,
0.0511687733232975,
0.006640751380473375,
-0.052215609699487686,
-0.015309732407331467,
-0.03430142626166344,
-0.027914488688111305,
0.07920898497104645,
0.0681787058711052,
-0.04874323680996895,
-0.067233607172966,
0.028895152732729912,
-0.072744... | 0.118334 |
can now run Kubernetes services of type NodePort and LoadBalancer using instance targets with an externalTrafficPolicy set to Local in the standard mode. `Local` preserves the client source IP and avoids a second hop for LoadBalancer and NodePort type Services. \*Deploying NodeLocal DNSCache\* When using security group... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/sgpp.adoc | mainline | aws-eks-best-practices | [
-0.0010462065692991018,
0.008159947581589222,
0.07918756455183029,
0.012575686909258366,
-0.04973762482404709,
0.0048486716113984585,
-0.03168322890996933,
-0.029738515615463257,
0.057491008192300797,
0.058039430528879166,
-0.07255413383245468,
-0.03286370262503624,
-0.025749847292900085,
... | 0.152974 |
AWS Loadbalancer Controller to update the rules of security groups to route traffic to the Pods. If just one security group is given to a Pod, the assignment of a tag is optional. Permissions set in a security group are additive, therefore tagging a single security group is sufficient for the loadbalancer controller to... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/sgpp.adoc | mainline | aws-eks-best-practices | [
-0.029353970661759377,
0.011602304875850677,
-0.03356817737221718,
0.0013537536142393947,
0.04955344647169113,
0.00539804482832551,
-0.0046862224116921425,
-0.018931467086076736,
0.054783422499895096,
0.04475914314389229,
-0.040372561663389206,
-0.05772765725851059,
0.014353200793266296,
-... | 0.103782 |
//!!NODE\_ROOT [."topic"] [[prefix-mode-linux,prefix-mode-linux.title]] = Prefix Mode for Linux :info\_doctype: section :info\_title: Prefix Mode for Linux :info\_abstract: Prefix Mode for Linux :info\_titleabbrev: Prefix Mode for Linux :imagesdir: images/networking/ [abstract] -- Prefix Mode for Linux -- TIP: https://... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/prefix-mode_linux.adoc | mainline | aws-eks-best-practices | [
0.015577152371406555,
-0.025589851662516594,
-0.013591470196843147,
-0.01630735769867897,
0.06866034865379333,
-0.019735820591449738,
-0.04425947740674019,
0.01722380332648754,
0.0545329786837101,
0.017804153263568878,
0.03432619571685791,
0.004782371688634157,
0.038659512996673584,
-0.044... | 0.124555 |
Recommendations === Use Prefix Mode when Use prefix mode if you are experiencing Pod density issue on the worker nodes. To avoid VPC CNI errors, we recommend examining the subnets for contiguous block of addresses for /28 prefix before migrate to prefix mode. Please refer "`https://docs.aws.amazon.com/vpc/latest/usergu... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/prefix-mode_linux.adoc | mainline | aws-eks-best-practices | [
-0.015079066157341003,
-0.022483034059405327,
0.02907625027000904,
0.028033537790179253,
0.034994956105947495,
-0.009648721665143967,
-0.04107700660824776,
-0.03892079368233681,
0.007817570120096207,
0.05150638893246651,
-0.020463962107896805,
-0.07550854235887527,
0.023606978356838226,
-0... | 0.031116 |
you can afford (in the worst case) up to 15 unused IPs per node, we strongly recommend using the newer prefix assignment networking mode, and realizing the performance and efficiency gains that come with it. === Use Subnet Reservations to Avoid Subnet Fragmentation (IPv4) When EC2 allocates a /28 IPv4 prefix to an ENI,... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/prefix-mode_linux.adoc | mainline | aws-eks-best-practices | [
0.0003316209476906806,
-0.01394698116928339,
0.0034787289332598448,
-0.009587680920958519,
0.06630492955446243,
0.004631257150322199,
-0.0699872076511383,
-0.014569615013897419,
0.0485881082713604,
0.032029889523983,
0.027695633471012115,
-0.07414845377206802,
0.03513657674193382,
-0.02630... | -0.015158 |
//!!NODE\_ROOT [."topic"] [[load-balancing,load-balancing.title]] = Load Balancing :info\_titleabbrev: Load Balancing :info\_doctype: section :imagesdir: images/networking/ TIP: https://aws-experience.com/emea/smb/events/series/get-hands-on-with-amazon-eks?trk=4a9b4147-2490-4c63-bc9f-f8a84b122c8c≻\_channel=el[Explore] ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
-0.058944541960954666,
0.03294752165675163,
0.004231492523103952,
0.006066157948225737,
-0.03165058419108391,
0.003158970968797803,
0.025162961333990097,
-0.02782365120947361,
0.13677315413951874,
0.05210153013467789,
-0.09676623344421387,
-0.049315132200717926,
0.03950227424502373,
-0.061... | 0.156892 |
\* Leveraging the AWS Load Balancer Controller (recommended) By default, the Kubernetes Service Controller, also known as the in-tree controller, reconciles the Kubernetes Service resource of type LoadBalancer. This controller is built into the link:https://github.com/kubernetes/cloud-provider-aws[AWS Cloud Provider] c... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
-0.03427764028310776,
0.01056115236133337,
0.02709798328578472,
-0.029368221759796143,
-0.0006665270193479955,
0.036362580955028534,
0.03313412144780159,
-0.025406615808606148,
0.14053967595100403,
0.08353327959775925,
-0.054145701229572296,
-0.02813234180212021,
0.016697414219379425,
-0.0... | 0.118943 |
pod, this simplifies the network path as it bypasses the previous extra hops of Worker Nodes and Service Cluster IP, it reduces latency that would otherwise have been incurred if the Service forwarded traffic to a pod in another AZ and lastly it removes the iptables rules overhead processing on the Worker Nodes. \* The... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
0.03472960740327835,
0.06235814839601517,
0.01953529380261898,
0.024735836312174797,
0.07114363461732864,
-0.031995296478271484,
0.04486667364835739,
-0.031105078756809235,
0.07871422916650772,
0.08726580440998077,
-0.05505122244358063,
0.03235836327075958,
0.017191922292113304,
-0.0861060... | 0.288206 |
https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-readiness-status[all the containers within a Pod are running] the https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions[Pod condition] is considered to be "`Ready`". However the application may still not be able to process ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
0.033080291002988815,
0.016149992123246193,
0.0219364482909441,
-0.020656157284975052,
0.001897183246910572,
-0.03731293976306915,
-0.029693108052015305,
-0.03699906915426254,
0.0660301148891449,
0.11055804044008255,
-0.018848901614546776,
0.027534468099474907,
-0.017583632841706276,
-0.01... | 0.168049 |
prevent the rolling update of a deployment from terminating old pods until the newly created Pods target status turn "`Healthy`" on the AWS ELB. === Gracefully shutdown applications Your application should respond to a SIGTERM signal by starting its graceful shutdown so that clients do not experience any downtime. What... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
0.0549640879034996,
0.026301855221390724,
0.08133180439472198,
-0.0035530172754079103,
-0.01881934329867363,
-0.05718475952744484,
-0.032772794365882874,
0.005079421680420637,
0.04422098398208618,
0.06038600206375122,
-0.024070877581834793,
0.0038634908851236105,
-0.04946275055408478,
-0.1... | 0.14422 |
takes for the application to close out the connections gracefully. Hence the not so perfect but most feasible approach here is to use a PreStop hook to delay the SIGTERM signal until the iptables rules are updated to make sure that no new client requests are sent to the application rather, only existing connections car... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
0.008927551098167896,
0.0549449659883976,
0.01618966832756996,
-0.016954775899648666,
0.008998709730803967,
-0.014906050637364388,
0.032421696931123734,
-0.012442103587090969,
0.10596819967031479,
0.06986337900161743,
-0.06017501652240753,
-0.015352921560406685,
0.019948020577430725,
-0.11... | 0.087682 |
container runtime to start the containers defined in the Pod spec. . When the containers starts running, the kubelet updates the https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions[Pod condition] as `Ready` in the Pod object in the Kubernetes API. . The https://kubernetes.io/docs/concepts/o... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
0.023481642827391624,
0.008150296285748482,
0.008913019672036171,
0.0003507430083118379,
-0.022408582270145416,
0.016558948904275894,
-0.01820331998169422,
-0.040331896394491196,
0.09520522505044937,
0.07653463631868362,
-0.005994731560349464,
0.02899508737027645,
-0.03634851053357124,
-0.... | 0.156818 |
//!!NODE\_ROOT [."topic"] [[custom-networking,custom-networking.title]] = Custom Networking :info\_doctype: section :imagesdir: images/networking/ :info\_title: Custom Networking :info\_abstract: Custom Networking :info\_titleabbrev: Custom Networking [abstract] -- Custom Networking -- TIP: https://aws-experience.com/... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/custom-networking.adoc | mainline | aws-eks-best-practices | [
-0.009417776949703693,
0.010673176497220993,
0.0067833405919373035,
-0.0005910249892622232,
0.03139400854706764,
0.03401416540145874,
-0.013564251363277435,
-0.02513514645397663,
0.05634104460477829,
0.07524830847978592,
-0.01230337843298912,
-0.040328845381736755,
0.03750953823328018,
-0.... | 0.113779 |
challenges. Please consider using prefix delegation with custom networking to increase the Pods density on a node. You might consider custom networking if you have a security requirement to run Pods on a different network with different security group requirements. When custom networking enabled, the pods use different... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/custom-networking.adoc | mainline | aws-eks-best-practices | [
0.008364556357264519,
0.0036785872653126717,
0.01772245205938816,
0.036131974309682846,
-0.014916393905878067,
0.025683477520942688,
-0.03055666573345661,
0.009275581687688828,
0.0368032231926918,
0.09049516916275024,
-0.08602694422006607,
-0.07092075049877167,
0.042992766946554184,
-0.046... | 0.155043 |
address ranges, customers have the option of using VPC Peering to interconnect such VPCs. This method could provide potential cost savings as all data transit within an Availability Zone via a VPC peering connection is now free. image::cn-image-3.png[illustration of network traffic using private NAT gateway] ==== Uniqu... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/custom-networking.adoc | mainline | aws-eks-best-practices | [
0.00909245666116476,
-0.009804265573620796,
-0.0023446260020136833,
0.05969822779297829,
0.014767852611839771,
0.056594137102365494,
0.0026018228381872177,
-0.042844004929065704,
0.03605448082089424,
0.04628355801105499,
-0.02715454436838627,
-0.02868863008916378,
0.04755891114473343,
-0.0... | 0.088081 |
primary ENI is no longer used to assign Pod IP addresses, there is a decrease in the number of Pods you can run on a given EC2 instance type. To work around this limitation you can use prefix assignment with custom networking. With prefix assignment, each secondary IP is replaced with a /28 prefix on secondary ENIs. Co... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/custom-networking.adoc | mainline | aws-eks-best-practices | [
0.0411822535097599,
-0.012476414442062378,
0.06792476773262024,
-0.04487057030200958,
-0.03352782502770424,
-0.0463559664785862,
-0.06296414136886597,
0.006569091696292162,
0.014841618947684765,
0.04436229541897774,
-0.007685184478759766,
-0.06757906079292297,
0.03816100209951401,
-0.05109... | 0.169252 |
//!!NODE\_ROOT [."topic"] [[ip-opt,ip-opt.title]] = Optimizing IP Address Utilization :imagesdir: images/networking/ :info\_doctype: section TIP: https://aws-experience.com/emea/smb/events/series/get-hands-on-with-amazon-eks?trk=4a9b4147-2490-4c63-bc9f-f8a84b122c8c≻\_channel=el[Explore] best practices through Amazon EK... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/ip-optimization-strategies.adoc | mainline | aws-eks-best-practices | [
0.025898389518260956,
0.026470663025975227,
0.0336274616420269,
0.018433917313814163,
0.08375034481287003,
-0.0014747369568794966,
0.005456765182316303,
-0.03956461325287819,
0.0710752084851265,
0.06768331676721573,
-0.02094556763768196,
0.0017278242157772183,
0.030175210908055305,
-0.0630... | 0.138388 |
deployments on EKS. For detailed information please see the xref:ipv6[Running IPv6 EKS Clusters] section and for hands-on experience please see the https://catalog.workshops.aws/ipv6-on-aws/en-US/lab-6[Understanding IPv6 on Amazon EKS] section of the https://catalog.workshops.aws/ipv6-on-aws/en-US[Get hands-on with IPv... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/ip-optimization-strategies.adoc | mainline | aws-eks-best-practices | [
0.02730454131960869,
0.07019861787557602,
0.010691407136619091,
0.013256397098302841,
0.013598307967185974,
0.009756564162671566,
-0.07055915147066116,
-0.06476791203022003,
0.022203460335731506,
0.0551014170050621,
-0.046665649861097336,
-0.012929899618029594,
-0.05012587457895279,
-0.070... | 0.137943 |
the current workloads can keep running on the same subnets and Amazon Elastic Kubernetes Service (Amazon EKS) can now schedule additional pods on the new "usable subnet(s)". If your cluster's current subnets are running out of IP addresses, you can simply add additional subnets to your Amazon EKS cluster as follows: . ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/ip-optimization-strategies.adoc | mainline | aws-eks-best-practices | [
-0.006925197318196297,
-0.04014681652188301,
0.01592252030968666,
0.04899168759584427,
0.04670698940753937,
0.04470781981945038,
-0.03979410231113434,
-0.09805642068386078,
0.07886526733636856,
0.05760842561721802,
-0.08343447744846344,
-0.014528890140354633,
0.011469502933323383,
-0.03608... | 0.123338 |
maximum number of ENIs the cluster can support \* number of ENIs already allocated \* number of IP addresses currently assigned to Pods \* total and maximum number of IP address available You can also set https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html[CloudWatch alarms] to get n... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/ip-optimization-strategies.adoc | mainline | aws-eks-best-practices | [
0.018635878339409828,
-0.04145076870918274,
0.026262829080224037,
0.013035590760409832,
0.07541164755821228,
-0.0013476156163960695,
0.007128990720957518,
-0.07527054846286774,
0.06778718531131744,
0.058827903121709824,
-0.09169072657823563,
-0.03971070796251297,
0.04270944744348526,
-0.07... | 0.118284 |
//!!NODE\_ROOT [."topic"] [[prefix-mode-win,prefix-mode-win.title]] = Prefix Mode for Windows :info\_doctype: section :imagesdir: images/networking/ In Amazon EKS, each Pod that runs on a Windows host is assigned a secondary IP address by the https://github.com/aws/amazon-vpc-resource-controller-k8s[VPC resource contro... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/prefix-mode_windows.adoc | mainline | aws-eks-best-practices | [
0.03653370216488838,
0.0006271180463954806,
-0.03258715942502022,
0.02091149054467678,
0.04311380535364151,
0.009587284177541733,
-0.008869444951415062,
-0.028978930786252022,
0.06898995488882065,
0.06121009588241577,
-0.010736322030425072,
-0.02874772809445858,
0.046918999403715134,
-0.01... | 0.136829 |
== Recommendations === Use Prefix Delegation when Use prefix delegation if you are experiencing Pod density issues on the worker nodes. To avoid errors, we recommend examining the subnets for contiguous block of addresses for /28 prefix before migrating to prefix mode. Please refer "`https://docs.aws.amazon.com/vpc/lat... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/prefix-mode_windows.adoc | mainline | aws-eks-best-practices | [
0.030525339767336845,
-0.005040237680077553,
0.028070470318198204,
0.04417473450303078,
0.011837865225970745,
-0.008842515759170055,
-0.02865077741444111,
-0.010754435323178768,
-0.040934208780527115,
0.05091472342610359,
-0.046115703880786896,
-0.0340021550655365,
0.027466420084238052,
0.... | 0.007091 |
drain all the existing nodes to safely evict all of your existing Pods. To prevent service disruptions, we suggest implementing https://kubernetes.io/docs/tasks/run-application/configure-pdb[Pod Disruption Budgets] on your production clusters for critical workloads. \* After you confirm the Pods are running, you can de... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/prefix-mode_windows.adoc | mainline | aws-eks-best-practices | [
0.04049430415034294,
0.02045491151511669,
0.0955609381198883,
0.01145510096102953,
0.032825544476509094,
0.006985807791352272,
-0.06150679662823677,
-0.09664760529994965,
0.051620304584503174,
0.10108117759227753,
-0.011159111745655537,
-0.05478375032544136,
0.009683936834335327,
-0.074641... | 0.106955 |
//!!NODE\_ROOT [."topic"] [[subnets,subnets.title]] = VPC and Subnet Considerations :info\_doctype: section :info\_title: VPC and Subnet Considerations :info\_abstract: VPC and Subnet Considerations :info\_titleabbrev: VPC and Subnets Considerations :imagesdir: images/networking/ [abstract] -- VPC and Subnet Considera... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/subnets.adoc | mainline | aws-eks-best-practices | [
-0.04774010181427002,
-0.0025118226185441017,
-0.020364219322800636,
0.04204126074910164,
0.03796975314617157,
0.03948367387056351,
-0.016030671074986458,
-0.016939466819167137,
0.05478115752339363,
0.028033876791596413,
-0.04663975536823273,
-0.03429434448480606,
0.023911552503705025,
-0.... | 0.10191 |
public IP address and a route to an internet gateway or a route to a NAT gateway where they can use the public IP address of the NAT gateway. ==== Public and Private Endpoint When both the public and private endpoints are enabled, Kubernetes API requests from within the VPC communicate to the control plane via the X-EN... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/subnets.adoc | mainline | aws-eks-best-practices | [
0.024837078526616096,
0.013430011458694935,
-0.04511985927820206,
0.03067079745233059,
0.0027118392754346132,
0.06942207366228104,
-0.0071302754804492,
-0.03739548847079277,
0.09100644290447235,
0.07246092706918716,
-0.025884006172418594,
-0.07010819017887115,
0.010778280906379223,
-0.0752... | 0.138352 |
public or a private subnet. Whether a subnet is public or private refers to whether traffic within the subnet is routed through an https://docs.aws.amazon.com/vpc/latest/userguide/VPC\_Internet\_Gateway.html[internet gateway]. Public subnets have a route table entry to the internet through the internet gateway, but pri... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/subnets.adoc | mainline | aws-eks-best-practices | [
0.021371349692344666,
-0.039476606994867325,
-0.06167566776275635,
0.031794846057891846,
0.09045218676328659,
0.010170705616474152,
0.03562884405255318,
-0.047260817140340805,
0.07431921362876892,
0.0636480301618576,
-0.02181580848991871,
0.01638220064342022,
0.0036918881814926863,
-0.0992... | 0.077014 |
are the service provider and would want to share your Kubernetes service and ingress (either ALB or NLB) with your customer VPC in separate accounts. [[subnets-multiple-accounts, subnets-multiple-accounts.title]] === Sharing VPC across multiple accounts Many enterprises adopted shared Amazon VPCs as a means to streamli... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/subnets.adoc | mainline | aws-eks-best-practices | [
-0.007116883993148804,
-0.024787133559584618,
-0.021970776841044426,
-0.009913560003042221,
0.007142726331949234,
0.06818916648626328,
0.029877033084630966,
-0.022731756791472435,
0.13210801780223846,
0.018454790115356445,
-0.064167320728302,
-0.03462032601237297,
0.07159995287656784,
-0.0... | 0.15833 |
or NLB) to route traffic to k8s pods either in application or central networking accounts. Refer to https://aws.amazon.com/blogs/containers/expose-amazon-eks-pods-through-cross-account-load-balancer/[Expose Amazon EKS Pods Through Cross-Account Load Balancer] walkthrough for detailed instructions on deploying the ELB r... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/subnets.adoc | mainline | aws-eks-best-practices | [
0.0025934658478945494,
-0.01732971891760826,
-0.026483697816729546,
0.0031645535491406918,
-0.0071267480961978436,
0.03734355419874191,
0.01924147829413414,
-0.0029582043644040823,
0.056193672120571136,
0.07094135880470276,
-0.06208061799407005,
-0.10095888376235962,
0.05560166761279106,
-... | 0.150782 |
route table of a public subnet contains a route to an internet gateway . Pods are able to interact with the Internet via a NAT gateway. Private subnets are supported by https://docs.aws.amazon.com/vpc/latest/userguide/egress-only-internet-gateway.html[egress-only internet gateways] in the IPv6 environment (EIGW). Insta... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/subnets.adoc | mainline | aws-eks-best-practices | [
0.029239481315016747,
-0.005375977139919996,
0.00941329076886177,
0.009776851162314415,
-0.010530803352594376,
0.04790545627474785,
0.03589532524347305,
-0.013025723397731781,
0.05797277018427849,
0.05603374168276787,
-0.06363934278488159,
-0.018795764073729515,
-0.030576689168810844,
-0.0... | 0.144891 |
//!!NODE\_ROOT [."topic"] [[ipv6,ipv6.title]] = IPv6 :info\_doctype: section :info\_title: Running IPv6 EKS Clusters :info\_abstract: Running IPv6 EKS Clusters :info\_titleabbrev: Running IPv6 Clusters :imagesdir: images/networking/ [abstract] -- Running IPv6 EKS Clusters -- EKS in IPv6 mode solves the IPv4 exhaustion ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/ipv6.adoc | mainline | aws-eks-best-practices | [
-0.009854000993072987,
0.03191103786230087,
0.04566793143749237,
0.002851727418601513,
0.0297816451638937,
0.03846510499715805,
-0.10465656965970993,
-0.046816736459732056,
0.047180432826280594,
0.018743377178907394,
-0.01632351242005825,
0.016811642795801163,
-0.044867247343063354,
-0.051... | 0.136122 |
but Pod density (Resources wise). IPv6 prefix assignment only occurs at the EKS worker-node bootstrap time. This behaviour is known to mitigate scenarios where high Pod churn EKS/IPv4 clusters are often delayed in Pod scheduling due to throttled API calls generated by the VPC CNI plug-in (ipamd) aimed to allocate Priva... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/ipv6.adoc | mainline | aws-eks-best-practices | [
-0.04288453236222267,
0.03129911422729492,
0.04769333824515343,
0.03910861536860466,
0.050298936665058136,
0.013702794909477234,
-0.06022351607680321,
-0.13481485843658447,
0.06794228404760361,
0.06378525495529175,
-0.019804099574685097,
-0.004482698626816273,
-0.026568017899990082,
-0.060... | 0.100333 |
assigned during EKS cluster creation stage and cannot be modified. The following diagram depict the Pod to Kubernetes Service flow: image::ipv6\_Pod-to-service-ipv6.png[EKS/IPv6, IPv6 Pod to IPv6 k8s service (ClusterIP ULA) flow] Services are exposed to the internet using an AWS load balancer. The load balancer receive... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/ipv6.adoc | mainline | aws-eks-best-practices | [
-0.013114800676703453,
0.037538908421993256,
0.008284462615847588,
0.003931770101189613,
-0.03899434208869934,
0.03527144342660904,
-0.03094640001654625,
-0.06993918120861053,
0.08845215290784836,
0.05730760097503662,
-0.04802129045128822,
-0.039928365498781204,
-0.03518875315785408,
-0.07... | 0.198982 |
available IPv4 and IPv6 addresses. It is recommended to size your dual-stack subnets/VPC CIDRs for future growth. You will not be able to schedule new Fargate Pods if the underlying subnet does not contain an available IPv4 address, irrespective of IPv6 available addresses. === Deploy the AWS Load Balancer Controller (... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/ipv6.adoc | mainline | aws-eks-best-practices | [
-0.01701653189957142,
-0.04766250401735306,
0.013832276687026024,
-0.008930615149438381,
-0.009544450789690018,
0.039105337113142014,
-0.1119854599237442,
-0.05345189943909645,
0.0761583000421524,
0.020367147400975227,
-0.057536374777555466,
-0.05438687652349472,
-0.08039822429418564,
-0.1... | 0.013041 |
//!!NODE\_ROOT [[networking,networking.title]] = Amazon EKS Best Practices Guide for Networking :doctype: book :sectnums: :toc: left :icons: font :experimental: :idprefix: :idseparator: - :sourcedir: . :info\_doctype: chapter :info\_title: Best Practices for Networking :info\_abstract: Best Practices for Networking :in... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/index.adoc | mainline | aws-eks-best-practices | [
-0.011001684702932835,
-0.0033959627617150545,
0.02214837074279785,
0.02461279183626175,
0.023900093510746956,
0.06318174302577972,
-0.013158459216356277,
-0.03304392471909523,
0.03689371794462204,
0.06671321392059326,
-0.023013034835457802,
0.034718483686447144,
0.007244536653161049,
-0.0... | 0.22456 |
EKS clusters. VPC CNI add-on is installed by default when you provision EKS clusters. VPC CNI runs on Kubernetes worker nodes. The VPC CNI add-on consists of the CNI binary and the IP Address Management (ipamd) plugin. The CNI assigns an IP address from the VPC network to a Pod. The ipamd manages AWS Elastic Networking... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/index.adoc | mainline | aws-eks-best-practices | [
-0.05338781327009201,
-0.05292189121246338,
-0.02943030558526516,
0.00029378646286204457,
0.036172691732645035,
0.045068610459566116,
-0.025150399655103683,
-0.07507116347551346,
0.06801372021436691,
0.0728420540690422,
-0.011060182005167007,
-0.05256092548370361,
0.01760784164071083,
-0.0... | 0.167326 |
EKS has prioritized IPv6-only Pods over dual-stack Pods. That is, Pods may be able to access IPv4 resources, but they are not assigned an IPv4 address from VPC CIDR range. The VPC CNI assigns IPv6 addresses to Pods from the AWS managed VPC IPv6 CIDR block. == Subnet Calculator This project includes a https://github.com... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/index.adoc | mainline | aws-eks-best-practices | [
-0.017519457265734673,
0.018979456275701523,
0.03332353010773659,
0.029490826651453972,
0.007325059734284878,
0.017985815182328224,
-0.07385454326868057,
-0.07326383143663406,
0.06601516157388687,
0.03070344403386116,
-0.03356603533029556,
-0.06605411320924759,
0.0033388459123671055,
-0.05... | 0.090739 |
[."topic"] [#ipvs] = Running kube-proxy in IPVS Mode :info\_doctype: section EKS in IP Virtual Server (IPVS) mode solves the https://docs.aws.amazon.com/eks/latest/best-practices/control-plane.html#reliability\_cprunning\_large\_clusters[network latency issue] often seen when running large clusters with over 1,000 serv... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/ipvs.adoc | mainline | aws-eks-best-practices | [
0.04976475611329079,
0.017557429149746895,
0.018702859058976173,
0.030742421746253967,
0.0011166490148752928,
-0.0354592464864254,
-0.014685073867440224,
-0.0639452338218689,
0.04868713393807411,
0.04911211133003235,
-0.06648172438144684,
-0.006718411576002836,
-0.007858110591769218,
-0.08... | 0.071781 |
making these changes during initial EKS cluster creation to minimize impacts. ==== You can issue an AWS CLI command to enable IPVS by updating the `kube-proxy` EKS Add-on. [,bash] ---- aws eks update-addon --cluster-name $CLUSTER\_NAME --addon-name kube-proxy \ --configuration-values '{"ipvs": {"scheduler": "rr"}, "mod... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/ipvs.adoc | mainline | aws-eks-best-practices | [
-0.0244174562394619,
0.03872913867235184,
0.04251165688037872,
0.03165319561958313,
-0.05903692543506622,
0.017865166068077087,
-0.04310326650738716,
-0.05079841986298561,
0.07531317323446274,
0.07802587747573853,
-0.07490437477827072,
-0.06075286865234375,
0.020629392936825752,
-0.0538470... | 0.059741 |
//!!NODE\_ROOT [."topic"] = Monitoring EKS workloads for Network performance issues :info\_doctype: section :imagesdir: images/networking/ :info\_titleabbrev: Monitoring for Network performance issues == Monitoring CoreDNS traffic for DNS throttling issues Running DNS intensive workloads can sometimes experience interm... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/monitoring.adoc | mainline | aws-eks-best-practices | [
-0.012134058400988579,
0.012074415571987629,
0.07204220443964005,
-0.007514874916523695,
-0.0506143793463707,
-0.037121713161468506,
-0.03651566430926323,
-0.03325258195400238,
0.07188165932893753,
0.05994865670800209,
-0.05260549858212471,
-0.039160002022981644,
0.016977347433567047,
-0.0... | 0.165382 |
new connections could not be established. == Other important Network performance metrics Other important network performance metrics include: `bw\_in\_allowance\_exceeded` (ideal value of the metric should be zero) is the number of packets queued and/or dropped because the inbound aggregate bandwidth exceeded the maxim... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/monitoring.adoc | mainline | aws-eks-best-practices | [
-0.02350492589175701,
-0.03878980129957199,
-0.004291980527341366,
0.03860778734087944,
0.003257608041167259,
-0.025116397067904472,
0.027232833206653595,
-0.03432096913456917,
0.07995714992284775,
0.08718075603246689,
-0.04252013564109802,
-0.04230263829231262,
0.032912228256464005,
-0.00... | 0.026339 |
the metrics discussed so far. We will use the https://github.com/aws-controllers-k8s/prometheusservice-controller[ACK Controller for Amazon Managed Service for Prometheus] to provision the alerting and recording rules. Let's deploy the ACL controller for the Amazon Managed Service for Prometheus service: ---- export SE... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/monitoring.adoc | mainline | aws-eks-best-practices | [
-0.1004151850938797,
0.041338350623846054,
-0.07876280695199966,
0.0077569084241986275,
0.04050397872924805,
-0.085171639919281,
0.006234972737729549,
-0.012927748262882233,
0.06918957084417343,
0.04618752375245094,
0.015372399240732193,
-0.06618372350931168,
0.03831776976585388,
-0.021625... | 0.112842 |
Prometheus as a datasource] Let's explore the metrics in Amazon Managed Grafana now: Click the explore button, and search for ethtool: image::mon\_explore\_metrics.png[Node\_ethtool metrics] Let's build a dashboard for the linklocal\_allowance\_exceeded metric by using the query `rate(node\_net\_ethtool{device="eth0",t... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/monitoring.adoc | mainline | aws-eks-best-practices | [
-0.04142799973487854,
0.050556644797325134,
-0.029885955154895782,
0.021496394649147987,
0.04647715389728546,
-0.11573324352502823,
-0.004584318492561579,
-0.0026614840608090162,
-0.010909853503108025,
0.0616622194647789,
0.0013701313873752952,
-0.11245500296354294,
0.051702726632356644,
0... | 0.104476 |
= Optimizing over time (Right Sizing) Right Sizing as per the AWS Well-Architected Framework, is "`... using the lowest cost resource that still meets the technical specifications of a specific workload`". When you specify the resource `requests` for the Containers in a Pod, the scheduler uses this information to decid... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/optimizing.adoc | mainline | aws-eks-best-practices | [
0.03822128847241402,
0.11919623613357544,
0.05083239823579788,
0.031206898391246796,
-0.04768720269203186,
-0.027948442846536636,
-0.021745862439274788,
-0.011469566263258457,
0.06805875152349472,
-0.019494641572237015,
-0.09960748255252838,
-0.017563462257385254,
-0.0239451564848423,
-0.0... | 0.120289 |
applications and microservices running on Amazon Elastic Kubernetes Service. The metrics include utilization for resources such as CPU, memory, disk, and network - which can help with right-sizing Pods and save costs. https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-metrics.ht... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/optimizing.adoc | mainline | aws-eks-best-practices | [
-0.022125622257590294,
0.01912551559507847,
-0.010593018494546413,
0.03157547488808632,
0.03378630056977272,
-0.07899374514818192,
0.03599206358194351,
-0.042312685400247574,
0.07769308984279633,
0.03509771078824997,
-0.06485287100076675,
-0.06388984620571136,
0.009727898053824902,
-0.0225... | 0.245132 |
//!!NODE\_ROOT [."topic"] [[cost-opt-observability,cost-opt-observability.title]] = Cost Optimization - Observability :info\_doctype: section :imagesdir: images/ :info\_title: Observability :info\_abstract: Observability :info\_titleabbrev: Observability :authors: ["Rachel Leekin", "Nirmal Mehta"] :date: 2023-09-29 == ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_observability.adoc | mainline | aws-eks-best-practices | [
-0.016354409977793694,
0.05855851620435715,
0.0012569804675877094,
0.0004087718261871487,
0.030705157667398453,
-0.13658057153224945,
0.027438953518867493,
0.035522930324077606,
-0.012062196619808674,
0.05993705242872238,
-0.0358213447034359,
-0.06198355183005333,
0.03074544295668602,
0.03... | 0.21459 |
can customize the retention policy for each log group based on your workload requirements. In a development environment, a lengthy retention period may not be necessary. But in a production environment, you can set a longer retention policy to meet troubleshooting, compliance, and capacity planning requirements. For ex... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_observability.adoc | mainline | aws-eks-best-practices | [
0.006696177180856466,
0.009334747679531574,
-0.01782223768532276,
0.0551784485578537,
0.08971289545297623,
-0.011158931069076061,
-0.003798738354817033,
-0.056600604206323624,
0.05381540581583977,
0.04848286882042885,
-0.013951726257801056,
0.026048464700579643,
0.02837342955172062,
0.0465... | 0.012354 |
default. For your application logs, adjust the log levels to align with the criticality of the workload and environment. For example, the java application below is outputting `INFO` logs which is the typical default application configuration and depending on the code can result in a high volume of log data. ---- import... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_observability.adoc | mainline | aws-eks-best-practices | [
0.09264124184846878,
0.028072061017155647,
-0.02675546519458294,
-0.03648824617266655,
0.023772623389959335,
-0.11973904818296432,
-0.02188420668244362,
0.08142993599176407,
0.03006366640329361,
0.044351689517498016,
-0.01081933081150055,
-0.019503528252243996,
0.007568068336695433,
0.0116... | 0.068877 |
health of resources, allowing you to take proactive measures when necessary. Generally observability costs scale with telemetry data collection and retention. Below are a few strategies you can implement to reduce the cost of metric telemetry: collecting only metrics that matter, reducing the cardinality of your teleme... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_observability.adoc | mainline | aws-eks-best-practices | [
0.00110450794454664,
0.051154568791389465,
-0.01847846433520317,
0.003918839152902365,
-0.028639862313866615,
-0.07994116842746735,
0.03721034154295921,
-0.0064039938151836395,
0.04634389653801918,
0.06747018545866013,
-0.017040830105543137,
-0.03723946213722229,
0.022821133956313133,
-0.0... | 0.08714 |
can run the following PROMQL query to determine which scrape targets have the highest number of metrics (cardinality): [,promql] ---- topk\_max(5, max\_over\_time(scrape\_samples\_scraped[1h])) ---- and the following PROMQL query can help you determine which scrape targets have the highest metrics churn (how many new m... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_observability.adoc | mainline | aws-eks-best-practices | [
-0.0322546660900116,
-0.06417679041624069,
-0.08684051781892776,
0.001090398756787181,
-0.010709569789469242,
-0.10296700149774551,
-0.013089601881802082,
-0.022309821099042892,
0.007042968180030584,
-0.0022994312457740307,
-0.028107110410928726,
-0.08547920733690262,
0.027671145275235176,
... | 0.042196 |
and 10% of the requests to a payment page this might leave you with 300 traces for an 30 minute period. With an ADOT Tail Sampling rule of that filters specific errors, you could be left with 200 traces which decreases the number of traces stored. ---- processors: groupbytrace: wait\_duration: 10s num\_traces: 300 tail... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_observability.adoc | mainline | aws-eks-best-practices | [
-0.04211380332708359,
-0.008865350857377052,
-0.03380917012691498,
0.011571145616471767,
0.038571249693632126,
-0.05256280303001404,
0.0025809556245803833,
-0.05795443803071976,
0.00747215049341321,
0.04332711547613144,
-0.015735870227217674,
-0.0530022494494915,
-0.002177305519580841,
-0.... | -0.009222 |
[."topic"] [#cost-opt-networking] = Cost Optimization - Networking :info\_doctype: section :authors: ["Lukonde Mwila"] :date: 2023-09-22 :info\_titleabbrev: Network :imagesdir: images/ Architecting systems for high availability (HA) is a best practice in order to accomplish resilience and fault-tolerance. In practice, ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_networking.adoc | mainline | aws-eks-best-practices | [
-0.004234744235873222,
0.05019473284482956,
0.009057426825165749,
0.048530466854572296,
0.036771345883607864,
-0.00953591987490654,
-0.00823136419057846,
0.031358908861875534,
0.038262419402599335,
0.06296990811824799,
-0.03801954910159111,
-0.02929100953042507,
0.0901591032743454,
-0.0714... | 0.162252 |
also set a \_hint\_ for the zone. \_Hints\_ describe which zone an endpoint should serve traffic for. `kube-proxy` will then route traffic from a zone to an endpoint based on the \_hints\_ that get applied. The diagram below shows how EndpointSlices with hints are organized in such a way that `kube-proxy` can know what... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_networking.adoc | mainline | aws-eks-best-practices | [
0.0016624678391963243,
-0.03814692422747612,
0.029447374865412712,
-0.062132950872182846,
-0.03391559422016144,
-0.02249520644545555,
0.0709046944975853,
-0.04288056492805481,
0.062268342822790146,
0.034531038254499435,
-0.062094420194625854,
-0.04208016395568848,
-0.022462690249085426,
-0... | 0.110571 |
the increased load in the affected zone. \* This situation in turn can lead to resource inefficiency. When cluster autoscalers like Karpenter detect the pod scale-out across different AZs, they may provision additional nodes in the unaffected AZs, resulting in unnecessary resource allocation. To overcome this challenge... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_networking.adoc | mainline | aws-eks-best-practices | [
-0.0031008454971015453,
0.024472763761878014,
-0.0005032152985222638,
0.035328563302755356,
-0.021558748558163643,
-0.0753229483962059,
-0.0033547242637723684,
0.017896005883812904,
-0.039115216583013535,
0.0657082125544548,
-0.047346845269203186,
-0.048885319381952286,
0.006438885349780321,... | 0.175841 |
A could go to any replica of Microservice B on any given node across the different AZs. However, with the Service's internal traffic policy set to `Local`, traffic will be restricted to endpoints on the node that the traffic originated from. This policy dictates the exclusive use of node-local endpoints. By implication... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_networking.adoc | mainline | aws-eks-best-practices | [
0.06344802677631378,
0.0013572475872933865,
0.010645482689142227,
-0.03857040032744408,
-0.025022407993674278,
-0.0060895830392837524,
0.02702282927930355,
-0.06295091658830643,
0.04927524924278259,
0.0745997428894043,
-0.07601305842399597,
-0.03056889772415161,
0.032350245863199234,
0.027... | 0.120949 |
cluster. Your architecture may comprise internal and/or external facing load balancers. Depending on your architecture and network traffic configurations, the communication between load balancers and Pods can contribute a significant amount to data transfer charges. You can use the https://kubernetes-sigs.github.io/aws... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_networking.adoc | mainline | aws-eks-best-practices | [
0.037151090800762177,
0.04232928156852722,
-0.0009708321886137128,
0.078410305082798,
0.0053153266198933125,
-0.028637979179620743,
0.04014722257852554,
-0.003343455959111452,
0.1388615518808365,
0.09416133910417557,
-0.0352964922785759,
-0.09394697844982147,
0.06604069471359253,
-0.076795... | 0.212481 |
data transfer costs from a container registry to the EKS worker nodes. == Data Transfer to Internet & AWS Services It's a common practice to integrate Kubernetes workloads with other AWS services or third-party tools and platforms via the Internet. The underlying network infrastructure used to route traffic to and from... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_networking.adoc | mainline | aws-eks-best-practices | [
0.019447732716798782,
0.06972750276327133,
0.022504664957523346,
0.03918294608592987,
0.028430279344320297,
-0.020821118727326393,
0.054555971175432205,
-0.007481216453015804,
0.10408969968557358,
0.07881031185388565,
-0.05296747013926506,
-0.03883802145719528,
0.014995519071817398,
-0.074... | 0.240463 |
Internet Gateways to establish communication between workloads in different VPCs. image::between\_vpcs.png[Between VPCs] === VPC Peering Connections To reduce costs for such use cases, you can make use of https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html[VPC Peering]. With a VPC Peering connection... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_networking.adoc | mainline | aws-eks-best-practices | [
-0.024154311046004295,
-0.035079337656497955,
-0.059806447476148605,
0.040296994149684906,
-0.012172120623290539,
0.015136437490582466,
0.04790867120027542,
-0.04086140915751457,
0.09949033707380295,
0.056262340396642685,
-0.10109914094209671,
-0.007078548427671194,
0.046800047159194946,
0... | 0.014764 |
to Pod replicas in different AZs. Below is a code block example of a Destination Rule resource in Istio. As can be seen below, this resource specifies weighted configurations for incoming traffic from 3 different AZs in the `eu-west-1` region. These configurations declare that a majority of the incoming traffic (70% in... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_networking.adoc | mainline | aws-eks-best-practices | [
0.04168803617358208,
0.00116645242087543,
-0.00722740963101387,
0.01864881068468094,
-0.030304672196507454,
-0.07888095825910568,
0.06521324813365936,
-0.020507721230387688,
0.022913966327905655,
0.0967162474989891,
-0.07509668916463852,
-0.06671178340911865,
0.007750424090772867,
0.062195... | 0.401932 |
A\*\* (on \*NODE 3) to\* \*\*APP C\*\* fails because there are no available \_node-local endpoints\_ for \*\*APP C\*\*. As the diagram shows, APP C has no replicas on NODE 3. \*\*\*\* The screenshots below are captured from a live example of this approach. The first set of screenshots demonstrate a successful external ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_networking.adoc | mainline | aws-eks-best-practices | [
-0.05359852313995361,
0.008828729391098022,
0.009973762556910515,
0.025782126933336258,
-0.011667119339108467,
-0.08765348792076111,
-0.03591490909457207,
-0.0364835299551487,
0.001953780883923173,
0.10038191080093384,
-0.03671618551015854,
-0.0862855464220047,
0.04722947999835014,
0.01638... | 0.230331 |
[."topic"] [#cost-opt-framework] = Cost Optimization Framework :info\_doctype: section :info\_titleabbrev: Framework :imagesdir: images/ AWS Cloud Economics is a discipline that helps customers increase efficiency and reduce their costs through the adoption of modern compute technologies like Amazon EKS. The discipline... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cfm_framework.adoc | mainline | aws-eks-best-practices | [
0.047959212213754654,
0.026855865493416786,
-0.057005252689123154,
0.027136078104376793,
0.10361072421073914,
-0.03291745111346245,
0.05052424594759941,
0.027873320505023003,
0.040002573281526566,
0.07250934094190598,
-0.024782145395874977,
-0.050320062786340714,
0.06107631325721741,
-0.00... | 0.112495 |
be considered as part of the workload. For considerations relating to EKS storage costs, please consult the xref:cost-opt-storage[Cost Optimization - Storage] section of this guide. == The Plan pillar: Planning and forecasting Once the recommendations in the See pillar are implemented, clusters are optimized on an on-g... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cfm_framework.adoc | mainline | aws-eks-best-practices | [
0.01630621775984764,
0.0811171680688858,
-0.027437282726168633,
0.06866355240345001,
0.03502364084124565,
-0.039060287177562714,
-0.043293315917253494,
0.023336339741945267,
0.0754631981253624,
0.10297567397356033,
-0.06199163198471069,
-0.053366757929325104,
0.04495146498084068,
-0.024969... | 0.156452 |
//!!NODE\_ROOT [[cost-opt,cost-opt.title]] = Cost Optimization - Introduction :doctype: book :sectnums: :toc: left :icons: font :experimental: :idprefix: :idseparator: - :sourcedir: . :info\_doctype: chapter :info\_title: Best Practices for Cost Optimization :info\_abstract: Best Practices for Cost Optimization :info\_... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_optimization_index.adoc | mainline | aws-eks-best-practices | [
0.007434320170432329,
0.08583728224039078,
0.018109483644366264,
0.0209671501070261,
0.018979426473379135,
-0.04661575332283974,
-0.04582856222987175,
0.017727747559547424,
0.062058623880147934,
0.056676194071769714,
-0.04795417562127113,
-0.04395660012960434,
0.056375082582235336,
-0.0440... | 0.098607 |
This guide is being released on GitHub so as to collect direct feedback and suggestions from the broader EKS/Kubernetes community. If you have a best practice that you feel we ought to include in the guide, please file an issue or submit a PR in the GitHub repository. Our intention is to update the guide periodically a... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_optimization_index.adoc | mainline | aws-eks-best-practices | [
-0.03220519423484802,
-0.004003992769867182,
0.0005101196584291756,
0.061855822801589966,
-0.0034263639245182276,
-0.033106982707977295,
0.022130893543362617,
0.029505552724003792,
0.00358534581027925,
0.06698553264141083,
0.02759789302945137,
-0.07367825508117676,
-0.027530387043952942,
-... | 0.199362 |
//!!NODE\_ROOT [."topic"] [[cost-opt-storage,cost-opt-storage.title]] = Cost Optimization - Storage :info\_doctype: section :imagesdir: images/ :info\_title: Storage :info\_abstract: Storage :info\_titleabbrev: Storage :authors: ["Chance Lee"] :date: 2023-10-31 == Overview There are scenarios where you may want to run ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_storage.adoc | mainline | aws-eks-best-practices | [
-0.0025762226432561874,
0.060700129717588425,
0.05574662610888481,
0.028758130967617035,
0.0004864196525886655,
-0.01989300362765789,
-0.04414507374167442,
0.06771289557218552,
0.11133178323507309,
0.05991470441222191,
-0.01425235066562891,
-0.006170880049467087,
0.06978151947259903,
0.023... | 0.117899 |
to preserve persistent data or information from one request to the next. Databases are a common example for such use cases. However, Pods, and the containers or processes inside them, are ephemeral in nature. To persist data beyond the lifetime of a Pod, you can use PVs to define access to storage at a specific locatio... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_storage.adoc | mainline | aws-eks-best-practices | [
-0.019493233412504196,
0.024279629811644554,
-0.0007385950302705169,
0.0365745984017849,
0.03394913673400879,
0.003863930469378829,
-0.003720691427588463,
0.019924215972423553,
0.1471942663192749,
0.08226311951875687,
-0.03361310437321663,
0.06549631804227829,
0.027368614450097084,
-0.0666... | 0.194864 |
your storage performance and cost to the needs of your applications. ==== Monitor and optimize over time It's important to understand your application's baseline performance and monitor it for selected volumes to check if it's meeting your requirements/expectations or if it's over-provisioned (e.g. a scenario where pro... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_storage.adoc | mainline | aws-eks-best-practices | [
0.02626330405473709,
0.09505542367696762,
0.03209686651825905,
0.00568170053884387,
0.009058828465640545,
-0.05108611658215523,
0.0014057799708098173,
0.03070370852947235,
0.056828573346138,
0.07736716419458389,
-0.08165981620550156,
-0.02103492245078087,
0.026116199791431427,
-0.030608948... | 0.075319 |
workloads and applications include Wordpress and Drupal, developer tools like JIRA and Git, and shared notebook system such as Jupyter as well as home directories. One of main benefits of Amazon EFS is that it can be mounted by multiple containers spread across multiple nodes and multiple availability zones. Another be... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_storage.adoc | mainline | aws-eks-best-practices | [
0.034322723746299744,
0.03401857614517212,
0.018085697665810585,
0.018826870247721672,
0.06824841350317001,
0.03370290249586105,
-0.019239824265241623,
0.021853845566511154,
0.07411257922649384,
0.07610050588846207,
-0.033614885061979294,
-0.00431292038410902,
0.047509368509054184,
0.01122... | 0.108365 |
Lustre provides different deployment options. The first option is called \_scratch\_ and it doesn't replicate data, while the second option is called \_persistent\_ which, as the name implies, persists data. The first option (\_scratch\_) can be used \_to reduce the cost of temporary shorter-term data processing.\_ The... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_storage.adoc | mainline | aws-eks-best-practices | [
-0.08192826807498932,
-0.01490284875035286,
-0.0038311886601150036,
0.029285473749041557,
-0.012352879159152508,
-0.03027554415166378,
-0.029084235429763794,
0.015808967873454094,
0.024929875507950783,
0.05112994462251663,
-0.0069761197082698345,
0.02111814357340336,
0.0698356032371521,
-0... | 0.102741 |
way to create minimal images. Multiple layers of packages, tools, application dependencies, libraries can easily bloat the container image size. By using multi-stage builds, you can selectively copy artifacts from one stage to another, excluding everything that isn't necessary from the final image. You can check more i... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_storage.adoc | mainline | aws-eks-best-practices | [
0.053891513496637344,
0.1330176442861557,
0.09739909321069717,
-0.02472505159676075,
-0.01875554770231247,
-0.08136497437953949,
-0.03650371730327606,
0.02856205590069294,
0.03891565278172493,
0.03822030872106552,
-0.0428868904709816,
-0.05488753318786621,
0.05627541244029999,
-0.025155583... | 0.006843 |
//!!NODE\_ROOT [."topic"] [[cost-opt-compute,cost-opt-compute.title]] = Cost Optimization - Compute and Autoscaling :info\_doctype: section :imagesdir: images/ :info\_title: Compute and Autoscaling :info\_abstract: Compute and Autoscaling :info\_titleabbrev: Compute :authors: ["Justin Garrison", "Rajdeep Saha"] :date: ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_compute.adoc | mainline | aws-eks-best-practices | [
-0.013910719193518162,
0.06527987122535706,
-0.029268190264701843,
0.06146293133497238,
0.02094998024404049,
-0.07696213573217392,
0.01825537718832493,
0.0765061154961586,
-0.06999371945858002,
0.03476833179593086,
-0.06947249919176102,
-0.03521081432700157,
0.05068465694785118,
0.01984212... | 0.119407 |
This will require getting metrics from your applications and setting configurations such as https://kubernetes.io/docs/tasks/run-application/configure-pdb/[`PodDisruptionBudgets`] and https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.5/deploy/pod\_readiness\_gate/[Pod Readiness Gates] to make sure your ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_compute.adoc | mainline | aws-eks-best-practices | [
0.04501407593488693,
-0.0013599477242678404,
0.00994630716741085,
0.018539728596806526,
-0.07161451876163483,
-0.027725163847208023,
-0.05678804963827133,
0.028606269508600235,
0.016333691775798798,
0.043852582573890686,
-0.054314762353897095,
-0.055827394127845764,
-0.021129393950104713,
... | 0.081582 |
number of nodes you need during normal business hours and "minimum" as the number of nodes you need during off-business hours. Please refer to https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md#auto-discovery-setup[Cluster Autoscaler FAQ] doc. === Cluster Autoscaler Prio... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_compute.adoc | mainline | aws-eks-best-practices | [
0.03131488710641861,
0.0403003953397274,
0.010249665006995201,
0.06462433189153671,
-0.021445151418447495,
0.018658289685845375,
0.002675604075193405,
0.044256340712308884,
-0.007969142869114876,
0.04434371739625931,
-0.0853952020406723,
-0.05046869441866875,
0.013746237382292747,
-0.01165... | 0.086062 |
and node templates to define broadly what type of EC2 instances can be created and settings about the instances as they are created. Bin packing is the practice of utilizing more of the instance's resources by packing more workloads onto fewer, optimally sized, instances. While this helps to reduce your compute costs b... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_compute.adoc | mainline | aws-eks-best-practices | [
0.035021692514419556,
0.023573510348796844,
0.004861404653638601,
0.03579636290669441,
0.044694747775793076,
-0.02508644387125969,
-0.06033923104405403,
-0.0002900658582802862,
0.05719200521707535,
0.06093578785657883,
-0.02331802248954773,
-0.034030649811029434,
0.006258869078010321,
-0.0... | 0.138295 |
to start with Kubernetes resource labeling and utilize tools like https://aws.amazon.com/blogs/containers/aws-and-kubecost-collaborate-to-deliver-cost-monitoring-for-eks-customers/[Kubecost] to get infrastructure cost reporting based on Kubernetes labels on pods, namespaces etc. Worker nodes need to have tags to show b... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_compute.adoc | mainline | aws-eks-best-practices | [
0.060990214347839355,
0.0344030000269413,
-0.03201703727245331,
0.09054645150899887,
0.015101666562259197,
0.011099530383944511,
0.016525546088814735,
-0.004707406274974346,
0.04976557195186615,
0.04394124075770378,
-0.0458904504776001,
-0.15461544692516327,
0.011434807442128658,
-0.007838... | 0.162703 |
run types in a single cluster to optimize specific workload requirements and cost. === Spot The https://aws.amazon.com/ec2/spot/[spot] capacity type provisions EC2 instances from spare capacity in an Availability Zone. Spot offers the largest discounts--up to 90% -- but those instances can be interrupted when they are ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_compute.adoc | mainline | aws-eks-best-practices | [
0.025258103385567665,
-0.0451018400490284,
-0.01019861176609993,
0.05294770747423172,
0.010431284084916115,
0.003325885161757469,
-0.016445327550172806,
0.02764204703271389,
0.05738174542784691,
0.0445546880364418,
-0.08258075267076492,
-0.013938182964920998,
0.019881809130311012,
-0.02440... | 0.092976 |
enroll in an Enterprise Agreement with AWS. Enterprise Agreements give customers the option to tailor agreements that best suit their needs. Customers can enjoy discounts on the pricing based on AWS EDP (Enterprise Discount Program). For additional information on Enterprise Agreements please contact your AWS sales repr... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_compute.adoc | mainline | aws-eks-best-practices | [
0.01653505675494671,
0.07683011144399643,
0.004497996065765619,
0.05823853239417076,
0.025082862004637718,
0.02371310070157051,
-0.020229551941156387,
0.06708800047636032,
0.005113836843520403,
0.05607641860842705,
-0.07170278578996658,
-0.0380408875644207,
0.03433751314878464,
-0.03208765... | 0.081289 |
the workload is a node which is not burstable or shareable between workloads. Fargate will save you EC2 instance management time which itself has a cost, but CPU and memory costs may be more expensive than other EC2 capacity types. Fargate pods can take advantage of compute savings plan to reduce the on-demand cost. ==... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/cost_opt_compute.adoc | mainline | aws-eks-best-practices | [
0.020288342610001564,
0.01377095840871334,
-0.012316721491515636,
0.021669801324605942,
0.025646992027759552,
-0.03887808695435524,
-0.10588058829307556,
0.06361236423254013,
0.09014204144477844,
-0.022116579115390778,
-0.10275391489267349,
0.0033151363022625446,
-0.052504364401102066,
-0.... | 0.110035 |
//!!NODE\_ROOT [."topic"] [[cost-opt-awareness,cost-opt-awareness.title]] = Expenditure awareness :info\_doctype: section :imagesdir: images/ :info\_title: Expenditure awareness :info\_abstract: Expenditure awareness :info\_titleabbrev: Awareness Expenditure awareness is understanding who, where and what is causing exp... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/awareness.adoc | mainline | aws-eks-best-practices | [
0.05410285294055939,
0.04692856967449188,
-0.02808917500078678,
0.08161910623311996,
0.10855088382959366,
-0.0038460437208414078,
0.04965827986598015,
0.0066094365902245045,
0.07429814338684082,
0.08440004289150238,
-0.011350154876708984,
-0.0908968523144722,
0.05082549899816513,
-0.032156... | 0.159143 |
Use the Kubernetes dashboard \*\_Kubernetes dashboard\_\* Kubernetes Dashboard is a general purpose, web-based UI for Kubernetes clusters, which provides information about the Kubernetes cluster including the resource usage at a cluster, node and pod level. The deployment of the Kubernetes dashboard on an Amazon EKS cl... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/awareness.adoc | mainline | aws-eks-best-practices | [
0.06275007873773575,
0.014714418910443783,
-0.041405897587537766,
0.04929110035300255,
0.0563114732503891,
-0.007396566681563854,
0.026181159541010857,
-0.01831928826868534,
0.08500370383262634,
0.08926856517791748,
-0.052993860095739365,
-0.10437867045402527,
0.0056846896186470985,
-0.030... | 0.190638 |
deployed REVISION: 1 TEST SUITE: None NOTES: --------------------------------------------------Kubecost has been successfully installed. When pods are Ready, you can enable port-forwarding with the following command: kubectl port-forward --namespace kubecost deployment/kubecost-cost-analyzer 9090 Next, navigate to http... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/cost/awareness.adoc | mainline | aws-eks-best-practices | [
0.02903580479323864,
0.025324534624814987,
0.02506251260638237,
-0.023809567093849182,
-0.03040217235684395,
-0.029783938080072403,
-0.11182205379009247,
-0.05756039544939995,
0.050744086503982544,
0.07126184552907944,
0.028346575796604156,
-0.11408735066652298,
-0.03660740703344345,
0.000... | 0.053456 |
[."topic"] [#scale-cluster-services] = Cluster Services :info\_doctype: section :imagesdir: images/scalability/ Cluster services run inside an EKS cluster, but they are not user workloads. If you have a Linux server you often need to run services like NTP, syslog, and a container runtime to support your workloads. Clus... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/cluster-services.adoc | mainline | aws-eks-best-practices | [
-0.00014230023953132331,
0.008365137502551079,
0.0374777689576149,
0.032340168952941895,
0.03651246055960655,
-0.003961704205721617,
-0.021153556182980537,
0.011506403796374798,
0.08662883937358856,
0.026237567886710167,
-0.007779982872307301,
-0.013452354818582535,
-0.005763942841440439,
... | 0.27297 |
256 cores or 16 nodes in the cluster--whichever happens first. If using the https://docs.aws.amazon.com/eks/latest/userguide/managing-coredns.html[CoreDNS EKS add-on], consider enabling the https://docs.aws.amazon.com/eks/latest/userguide/coredns-autoscaling.html[autoscaling] option. The CoreDNS autoscaler dynamically ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/cluster-services.adoc | mainline | aws-eks-best-practices | [
0.021113933995366096,
-0.04125810042023659,
0.007975384593009949,
0.01027608010917902,
-0.04617966338992119,
0.020881295204162598,
-0.07696337252855301,
0.004755636677145958,
0.06668708473443985,
0.05222746729850769,
-0.028102388605475426,
-0.04709351807832718,
0.0024759273510426283,
-0.02... | 0.106768 |
scaling. Because there are so many different options for logging and monitoring we cannot show examples for every provider. With https://docs.fluentbit.io/manual/pipeline/filters/kubernetes[fluentbit] we recommend enabling Use\_Kubelet to fetch metadata from the local kubelet instead of the Kubernetes API Server and se... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/cluster-services.adoc | mainline | aws-eks-best-practices | [
0.04246089980006218,
0.028809936717152596,
0.052930861711502075,
-0.026529913768172264,
0.00522141857072711,
-0.05761750414967537,
0.002431885339319706,
0.039546459913253784,
0.060367975383996964,
0.04754622280597687,
-0.04554680362343788,
-0.09338206797838211,
-0.04176430404186249,
0.0145... | 0.157566 |
[."topic"] [#scale-control-plane] = Kubernetes Control Plane :info\_doctype: section :info\_titleabbrev: Control Plane :imagesdir: images/scalability/ TIP: https://aws-experience.com/emea/smb/events/series/get-hands-on-with-amazon-eks?trk=4a9b4147-2490-4c63-bc9f-f8a84b122c8c≻\_channel=el[Explore] best practices through... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/control-plane.adoc | mainline | aws-eks-best-practices | [
0.02713560312986374,
-0.01041728537529707,
-0.021104400977492332,
0.06903145462274551,
-0.0016285846941173077,
0.060166459530591965,
-0.03997805342078209,
-0.00789699424058199,
0.07384204864501953,
0.08104898780584335,
-0.03090357594192028,
-0.040874987840652466,
-0.006646253168582916,
-0.... | 0.109208 |
good process and practices for node upgrades and security patching. If every node in your cluster is replaced regularly then there is less toil required to maintain separate processes for ongoing maintenance. Use Karpenter's https://docs.aws.amazon.com/eks/latest/best-practices/karpenter.html#\_creating\_nodepools[time... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/control-plane.adoc | mainline | aws-eks-best-practices | [
0.028115766122937202,
0.0455373078584671,
0.07475164532661438,
0.06312484294176102,
0.05722515657544136,
-0.053616657853126526,
-0.0441027469933033,
-0.08842980116605759,
-0.004612368531525135,
0.08330489695072174,
-0.04941023513674736,
-0.0050765410996973515,
0.027429107576608658,
-0.0583... | 0.104056 |
requests, the API Server limits the number of inflight requests it can have outstanding at a given time. Once this limit is exceeded, the API Server will start rejecting requests and return a 429 HTTP response code for "Too Many Requests" back to clients. The server dropping requests and having clients try again later ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/control-plane.adoc | mainline | aws-eks-best-practices | [
0.0035463471431285143,
-0.005627564154565334,
0.03626192733645439,
0.013506872579455376,
-0.06548136472702026,
-0.03788919374346733,
-0.018359636887907982,
-0.019257912412285805,
0.11399471759796143,
0.09694702178239822,
-0.07344488799571991,
0.005435551982372999,
-0.03182029351592064,
-0.... | 0.154202 |
$ kubectl get flowschemas NAME PRIORITYLEVEL MATCHINGPRECEDENCE DISTINGUISHERMETHOD AGE MISSINGPL exempt exempt 1 7h19m False eks-exempt exempt 2 7h19m False probes exempt 2 7h19m False system-leader-election leader-election 100 ByUser 7h19m False endpoint-controller workload-high 150 ByUser 7h19m False workload-leader... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/control-plane.adoc | mainline | aws-eks-best-practices | [
-0.0052335383370518684,
0.007267188746482134,
0.015321843326091766,
-0.013456104323267937,
-0.023430055007338524,
0.00017253111582249403,
-0.028965042904019356,
-0.04803212359547615,
0.018756534904241562,
0.060780953615903854,
0.004954253323376179,
-0.08158861845731735,
0.03373941779136658,
... | 0.105873 |
affected FlowSchemas can decrease the number of requests executing at a given time. This can be accomplished by reducing the total number of requests made over the period where 429s are occurring. Note that long-running requests such as expensive list calls are especially problematic because they count as an inflight r... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/control-plane.adoc | mainline | aws-eks-best-practices | [
-0.010976887308061123,
0.029793616384267807,
0.04697491601109505,
-0.019256573170423508,
-0.041985608637332916,
-0.04747173935174942,
-0.009926055558025837,
-0.04632097855210304,
0.11178359389305115,
0.09733662009239197,
-0.05788053944706917,
0.0020024192053824663,
-0.05366818606853485,
-0... | 0.119364 |
rules: - resourceRules: - apiGroups: - '\*' namespaces: - default resources: - events verbs: - list subjects: - kind: ServiceAccount serviceAccount: name: default namespace: default ---- \* This FlowSchema captures all list event calls made by service accounts in the default namespace. \* The matching precedence 8000 i... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/control-plane.adoc | mainline | aws-eks-best-practices | [
-0.005985036492347717,
0.0041277469135820866,
0.05969887599349022,
-0.0035149576142430305,
0.02303602360188961,
-0.07953988015651703,
0.04544808343052864,
-0.03524211049079895,
0.10751374065876007,
0.09794124215841293,
-0.05880482867360115,
-0.06303848326206207,
-0.044213589280843735,
-0.0... | 0.122659 |
are as narrowly scoped as needed. For example, to list only running pods in the default namespace use the following API path and arguments. ---- /api/v1/namespaces/default/pods?fieldSelector=status.phase=Running&limit=500 ---- Or list all pods that are running with: ---- /api/v1/pods?fieldSelector=status.phase=Running&... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/control-plane.adoc | mainline | aws-eks-best-practices | [
0.03931480646133423,
0.016198335215449333,
0.020648514851927757,
0.021862007677555084,
0.0019187091384083033,
0.011507115326821804,
-0.023279448971152306,
-0.020357424393296242,
0.052027758210897446,
0.04698455333709717,
-0.05554664507508278,
-0.018347682431340218,
-0.04363393411040306,
-0... | 0.149025 |
`RollingUpdate` strategies. ==== Prevent thundering herds on DaemonSet creation By default, regardless of the `RollingUpdate` configuration, the daemonset-controller in the kube-controller-manager will create pods for all matching nodes simultaneously when you create a new DaemonSet. To force a gradual rollout of pods ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/control-plane.adoc | mainline | aws-eks-best-practices | [
0.016378678381443024,
-0.009379145689308643,
0.010287435725331306,
0.00549802603200078,
-0.026924343779683113,
-0.014921207912266254,
-0.054705020040273666,
-0.04970606416463852,
0.04850681498646736,
0.06624284386634827,
0.010321327485144138,
-0.011677475646138191,
0.004783118609338999,
-0... | 0.098483 |
only `NotReady` pods or a large percentage of `NotReady` pods and you update its template, the daemonset-controller will create new pods concurrently for any `NotReady` pods. This can result in thundering herd issues if there are a significant number of `NotReady` pods, for example if pods are continually crash looping... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/control-plane.adoc | mainline | aws-eks-best-practices | [
0.014547312632203102,
-0.04806952923536301,
0.027832714840769768,
-0.009579190984368324,
0.029306787997484207,
-0.046668216586112976,
-0.07401169091463089,
-0.01056746207177639,
0.036200035363435745,
0.05711603909730911,
0.07093130052089691,
0.031237903982400894,
-0.03249678015708923,
-0.0... | 0.107278 |
[."topic"] [#scale-data-plane] = Kubernetes Data Plane :info\_doctype: section :info\_titleabbrev: Data Plane :imagesdir: images/scalability/ // The Kubernetes Data Plane includes EC2 instances, load balancers, storage, and other APIs used by the Kubernetes Control Plane. For organization purposes we grouped xref:clust... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/data-plane.adoc | mainline | aws-eks-best-practices | [
0.036337438970804214,
0.02781115658581257,
0.026208246126770973,
0.028814129531383514,
-0.0015903692692518234,
0.01108333095908165,
-0.00038133739144541323,
0.035567302256822586,
0.028597919270396233,
0.03543099761009216,
-0.07325750589370728,
-0.08530917763710022,
-0.016753066331148148,
-... | 0.091468 |
outage could impact 1/3 of the cluster. You should specify node requirements and pod spread in your workloads so the Kubernetes scheduler can place workloads properly. Workloads should define the resources they need and the availability required via taints, tolerations, and https://kubernetes.io/blog/2020/05/introducin... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/data-plane.adoc | mainline | aws-eks-best-practices | [
0.012784762308001518,
-0.013371171429753304,
0.04320603981614113,
0.0630897805094719,
-0.004686288069933653,
-0.02873055450618267,
-0.044959910213947296,
-0.015705332159996033,
0.02131934091448784,
0.06064288318157196,
-0.06175775080919266,
-0.01732989028096199,
-0.027835747227072716,
-0.0... | 0.116216 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.