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 |
|---|---|---|---|---|---|
they are available for patch releases. AMI minor versions (e.g. 1.23.5 to 1.24.3) will be available in the EKS console and API as https://docs.aws.amazon.com/eks/latest/userguide/update-managed-node-group.html[upgrades for the node group]. Patch release versions (e.g. 1.23.5 to 1.23.6) will not be presented as upgrades... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/data-plane.adoc | mainline | aws-eks-best-practices | [
-0.049699947237968445,
-0.0016761920414865017,
0.05054325982928276,
0.04923447594046593,
0.0795697346329689,
0.034824926406145096,
-0.06981394439935684,
-0.044880785048007965,
-0.01291465014219284,
0.08749336004257202,
0.06378083676099777,
0.006177872885018587,
0.0356488935649395,
-0.07677... | 0.088572 |
you need and avoids needing complicated log rotation rules. To disable syslog you can add the following snippet to your cloud-init configuration: ---- runcmd: - [ systemctl, disable, --now, syslog.service ] ---- == Patch instances in place when OS update speed is a necessity [IMPORTANT] ==== Patching instances in place... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/data-plane.adoc | mainline | aws-eks-best-practices | [
0.0542992539703846,
-0.00860582198947668,
0.0577021948993206,
-0.05857444927096367,
0.11099490523338318,
-0.07634633034467697,
-0.007992506958544254,
-0.046082086861133575,
0.03265409171581268,
0.10470235347747803,
0.059837017208337784,
-0.015088939107954502,
0.046647652983665466,
-0.02610... | -0.008871 |
[."topic"] = Known Limits and Service Quotas :info\_doctype: section :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 Amazon EKS workshops. Amazon EKS can be used for ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/quotas.adoc | mainline | aws-eks-best-practices | [
-0.021517030894756317,
-0.014945472590625286,
-0.03240659087896347,
-0.03033916838467121,
0.025574544444680214,
0.012657687067985535,
0.014262651093304157,
0.03637903556227684,
0.0992773175239563,
0.054294854402542114,
-0.06168031319975853,
-0.03126652166247368,
0.08506317436695099,
0.0163... | 0.094553 |
the networking for your cluster | L-A4707A72 | 5 | VPC | Network interfaces per Region | Can limit the number of EKS Worker nodes, or Impact EKS control plane scaling/update activities. | L-DF5E4CA3 | 5,000 | VPC | Network Address Usage | Can limit the number of Clusters per account or the control or connectivity of th... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/quotas.adoc | mainline | aws-eks-best-practices | [
0.015771258622407913,
-0.05483054742217064,
-0.05623096972703934,
0.01702568307518959,
-0.012369103729724884,
0.08072133362293243,
0.00005547935506911017,
0.00852152518928051,
-0.024441774934530258,
0.04278985783457756,
-0.03966383635997772,
-0.05524362623691559,
0.052015937864780426,
-0.1... | 0.125525 |
request throttling to ensure that they remain performant and available for all customers. Similar to Service Quotas, each AWS service maintains their own request throttling thresholds. Consider reviewing the respective AWS Service documentation if your workloads will need to quickly issue a large number of API calls or... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/quotas.adoc | mainline | aws-eks-best-practices | [
-0.019967224448919296,
0.004250660073012114,
0.02243945375084877,
0.004087013192474842,
0.012308686040341854,
-0.02238173969089985,
-0.0596928633749485,
0.025664858520030975,
0.094418004155159,
0.07491836696863174,
-0.02422669529914856,
-0.008451963774859905,
0.013139506801962852,
-0.02693... | 0.059373 |
[."topic"] = Kubernetes Upstream SLOs :info\_doctype: section :info\_titleabbrev: Kubernetes SLOs :imagesdir: images/scalability/ Amazon EKS runs the same code as the upstream Kubernetes releases and ensures that EKS clusters operate within the SLOs defined by the Kubernetes community. The Kubernetes https://github.com... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/kubernetes_slos.adoc | mainline | aws-eks-best-practices | [
0.01804559864103794,
-0.01810442842543125,
0.009537633508443832,
0.02517111971974373,
0.06089521199464798,
-0.0424681082367897,
0.004772723652422428,
-0.01805473491549492,
0.13375674188137054,
0.023631954565644264,
-0.0035008061677217484,
0.008757758885622025,
-0.005796934012323618,
-0.052... | 0.255772 |
means a request can run for up to one minute (60 seconds) before being timed out and cancelled. The SLOs defined for Latency are broken out by the type of request that is being made, which can be mutating or read-only: ==== Mutating Mutating requests in Kubernetes make changes to a resource, such as creations, deletion... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/kubernetes_slos.adoc | mainline | aws-eks-best-practices | [
-0.04190952703356743,
0.014673377387225628,
0.05970486253499985,
0.016247767955064774,
0.01767008565366268,
-0.038404375314712524,
-0.0321817509829998,
-0.05012197047472,
0.11014697700738907,
0.02326696738600731,
0.024259183555841446,
0.04744669795036316,
-0.038932133466005325,
-0.08821426... | 0.187764 |
dashboards, below are some examples for the SLOs above. === API Server Request Latency |=== | Metric | Definition | apiserver\_request\_sli\_duration\_seconds | Response latency distribution (not counting webhook duration and priority & fairness queue wait times) in seconds for each verb, group, version, resource, subr... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/kubernetes_slos.adoc | mainline | aws-eks-best-practices | [
-0.0024104330223053694,
-0.008502908051013947,
-0.03474290668964386,
0.024006271734833717,
-0.0024180912878364325,
-0.09779711067676544,
-0.05188519507646561,
-0.011342087760567665,
0.07736355811357498,
0.022083992138504982,
-0.012787475250661373,
-0.0958702564239502,
-0.01842869445681572,
... | 0.176959 |
| Definition | kubelet\_pod\_start\_sli\_duration\_seconds | Duration in seconds to start a pod, excluding time to pull images and run init containers, measured from pod creation timestamp to when all its containers are reported as started and observed via watch | kubelet\_pod\_start\_duration\_seconds | Duration in se... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/kubernetes_slos.adoc | mainline | aws-eks-best-practices | [
0.03967434540390968,
0.003947748802602291,
0.046709779649972916,
0.03422405570745468,
0.010573336854577065,
-0.024312486872076988,
-0.044418442994356155,
0.00341401738114655,
0.08052170276641846,
-0.01740861125290394,
-0.0016052636783570051,
-0.07622908055782318,
-0.025309989228844643,
-0.... | 0.203309 |
[."topic"] = Control Plane Monitoring :info\_doctype: section :authors: ["Shane Corbett"] :date: 2023-09-22 :imagesdir: images/scalability/ == API Server When looking at our API server it's important to remember that one of its functions is to throttle inbound requests to prevent overloading the control plane. What can... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/kcp_monitoring.adoc | mainline | aws-eks-best-practices | [
-0.05175729840993881,
0.012178914621472359,
0.012984818778932095,
0.000652273534797132,
0.006782324519008398,
-0.06705600768327713,
-0.022341003641486168,
-0.019302846863865852,
0.048761989921331406,
0.06917238980531693,
-0.061717115342617035,
0.02114005573093891,
0.00251292553730309,
0.01... | 0.088514 |
see the following https://docs.aws.amazon.com/eks/latest/best-practices/scale-control-plane.html#\_api\_priority\_and\_fairness[best practices guide] ==== Here we see the seven different priority groups that come by default on the cluster image::shared-concurrency.png[Shared concurrency] Next we want to see what percen... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/kcp_monitoring.adoc | mainline | aws-eks-best-practices | [
-0.005471536424010992,
-0.014304406009614468,
-0.0002448295708745718,
0.01947927102446556,
0.0033681083004921675,
0.014135180041193962,
-0.057318445295095444,
-0.028172258287668228,
0.0733075737953186,
0.08669974654912949,
-0.028907926753163338,
-0.01142052561044693,
0.04400504380464554,
-... | 0.023754 |
this data we can use an Ad-Hoc PromQL or a CloudWatch Insights query to pull LIST requests from the audit log during that time frame to see which application this might be. === Finding the Source with CloudWatch Metrics are best used to find the problem area we want to look at and narrow both the timeframe and the sear... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/kcp_monitoring.adoc | mainline | aws-eks-best-practices | [
0.028735622763633728,
-0.000895302218850702,
-0.017333567142486572,
0.03006281517446041,
0.06515920162200928,
-0.0588824637234211,
0.04482138156890869,
-0.06665253639221191,
0.07405570149421692,
0.04218855872750282,
-0.06678412854671478,
-0.10563909262418747,
0.017018290236592293,
0.003107... | 0.048343 |
plane to enable this function. It is also a best practice to limit the log retention as to not drive up cost over time unnecessarily. An example for turning on all logging functions using the EKSCTL tool below. ==== [,yaml] ---- cloudWatch: clusterLogging: enableTypes: ["\*"] logRetentionInDays: 10 ---- == Kube Control... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/kcp_monitoring.adoc | mainline | aws-eks-best-practices | [
0.006592306774109602,
-0.02545349672436714,
-0.017238417640328407,
-0.0059531875886023045,
-0.014900646172463894,
-0.019523343071341515,
0.029200546443462372,
-0.06452000886201859,
0.05773734301328659,
0.09728885442018509,
0.01349305547773838,
-0.025208324193954468,
-0.03093058243393898,
-... | 0.124068 |
troubleshooting phase. Often in production you will find that it takes adjustments to more than one part of Kubernetes to allow the system to work at its most performant. It's easy to inadvertently troubleshoot what is just a symptom (such as a node timeout) of a much larger bottle neck. == ETCD etcd uses a memory mapp... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/kcp_monitoring.adoc | mainline | aws-eks-best-practices | [
0.004008463118225336,
0.0665108859539032,
0.12977838516235352,
-0.008032749406993389,
0.06465829163789749,
-0.0242479145526886,
-0.10381685197353363,
-0.03208405151963234,
0.09182509779930115,
0.0663573145866394,
-0.03159405291080475,
0.03650159388780594,
-0.05862373113632202,
-0.051221504... | 0.067223 |
[."topic"] [#scalability] = EKS Scalability best practices :info\_titleabbrev: Scalability :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 Amazon EKS workshops. This ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/index.adoc | mainline | aws-eks-best-practices | [
0.046459395438432693,
-0.008762320503592491,
0.01979074254631996,
0.03883080556988716,
-0.010904703289270401,
0.001133653917349875,
-0.029844341799616814,
-0.003228189190849662,
0.03629734367132187,
0.03606243431568146,
-0.05737965181469917,
-0.058202799409627914,
0.024245375767350197,
-0.... | 0.162883 |
you plan and scale beyond the information provided in this guide. Amazon EKS can support up to 100,000 nodes in a single cluster if you are selected for onboarding. include::control-plane.adoc[leveloffset=+1] include::data-plane.adoc[leveloffset=+1] include::cluster-services.adoc[leveloffset=+1] include::workloads.adoc... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/index.adoc | mainline | aws-eks-best-practices | [
0.05942371115088463,
-0.027091408148407936,
-0.03774932026863098,
0.06391168385744095,
-0.002456364454701543,
-0.0173479150980711,
-0.041347797960042953,
-0.017380807548761368,
0.00021574634592980146,
0.08582930266857147,
-0.05239594727754593,
-0.08052029460668564,
0.009503847919404507,
-0... | 0.128671 |
[."topic"] [#scale-workloads] = Workloads :info\_doctype: section :imagesdir: images/scalability/ Workloads have an impact on how large your cluster can scale. Workloads that use the Kubernetes APIs heavily will limit the total amount of workloads you can have in a single cluster, but there are some defaults you can ch... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/workloads.adoc | mainline | aws-eks-best-practices | [
0.022192809730768204,
0.04676564782857895,
0.026617618277668953,
0.035644929856061935,
0.04048250615596771,
0.05997234582901001,
-0.012971683405339718,
-0.011232408694922924,
0.08131299912929535,
0.03180300071835518,
-0.028806263580918312,
0.015803953632712364,
0.02431556023657322,
0.00098... | 0.147674 |
split the service across multiple ALBs or use Kubernetes Ingress. The default NLB targets is 3000, but is limited to 500 targets per AZ. If your cluster runs more than 500 pods for an NLB service you will need to use multiple AZs or request a quota limit increase. An alternative to using a load balancer coupled to a se... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/workloads.adoc | mainline | aws-eks-best-practices | [
-0.020165864378213882,
-0.02308494970202446,
-0.03094669058918953,
0.003357505891472101,
-0.0739898681640625,
-0.0009574289433658123,
0.003052828600630164,
0.012988911010324955,
0.05758582055568695,
0.08910062909126282,
-0.09826275706291199,
-0.05989053100347519,
0.04673636332154274,
-0.04... | 0.171888 |
Kubernetes resources, you can disable auto-mounting service account secrets by setting automountServiceAccountToken: false \* If your application's secrets are static and will not be modified in the future, mark the https://kubernetes.io/docs/concepts/configuration/secret/#secret-immutable[secret as immutable]. The kub... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/workloads.adoc | mainline | aws-eks-best-practices | [
-0.0047254059463739395,
0.02111084759235382,
0.049115315079689026,
0.004030735697597265,
-0.05549159646034241,
0.007319396827369928,
0.009672200307250023,
-0.02158559486269951,
0.11103342473506927,
0.037099506705999374,
-0.05029672384262085,
-0.04455173760652542,
0.011808950453996658,
0.00... | 0.127257 |
resource version removed from etcd and depending on the size of the resources may use considerable space on the etcd host until defragmentation runs every 15 minutes. This defragmentation may cause pauses in etcd which could have other affects on the Kubernetes API and controllers. You should avoid frequent modificatio... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/workloads.adoc | mainline | aws-eks-best-practices | [
0.008660845458507538,
0.0033872572239488363,
0.07945001125335693,
-0.016643857583403587,
0.07306787371635437,
-0.04144382104277611,
-0.024190839380025864,
-0.08937965333461761,
0.11944203078746796,
0.057015519589185715,
-0.034622278064489365,
-0.003993107005953789,
-0.02202269434928894,
-0... | 0.047572 |
[."topic"] = Kubernetes Scaling Theory :info\_doctype: section :authors: ["Shane Corbett"] :date: 2023-09-22 :info\_titleabbrev: The theory behind scaling :imagesdir: images/scalability/ == Nodes vs. Churn Rate Often when we discuss the scalability of Kubernetes, we do so in terms of how many nodes there are in a singl... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/scaling_theory.adoc | mainline | aws-eks-best-practices | [
0.030712872743606567,
-0.04225711524486542,
0.018087957054376602,
0.05053452029824257,
0.021503936499357224,
-0.03608866408467293,
-0.027950387448072433,
0.04311639443039894,
0.0667969286441803,
0.028358303010463715,
-0.020720940083265305,
0.004901912994682789,
0.03283960744738579,
-0.0126... | 0.147937 |
to do this by using Kubelet as an example. Kubelet talks both to the API server and the container runtime; \*how\* and \*what\* do we need to monitor to detect whether either component is experiencing an issue? === How many Pods per Node When we look at scaling numbers, such as how many pods can run on a node, we could... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/scaling_theory.adoc | mainline | aws-eks-best-practices | [
0.010890690609812737,
0.025076040998101234,
0.032370831817388535,
0.0646776407957077,
-0.03049050271511078,
-0.058131132274866104,
-0.07428949326276779,
-0.005638835020363331,
-0.0006867742049507797,
0.032806579023599625,
-0.08006076514720917,
-0.05662235617637634,
-0.030171887949109077,
-... | 0.092365 |
right node size for our workloads these are easy-to-overlook signals that might be putting unnecessary pressure on the system thus limiting both our scale and performance. === The Cost of Unnecessary Errors Kubernetes controllers excel at retrying when error conditions arise, however this comes at a cost. These retries... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/scaling_theory.adoc | mainline | aws-eks-best-practices | [
0.05536368116736412,
-0.011456655338406563,
0.03687455877661705,
0.0810166448354721,
0.013601000420749187,
-0.04252541810274124,
-0.002567498479038477,
-0.01857026480138302,
0.06653347611427307,
0.07846278697252274,
-0.06835641711950302,
-0.0817326009273529,
0.01035637129098177,
-0.0705755... | 0.104727 |
[."topic"] = Node and Workload Efficiency :info\_doctype: section :authors: ["Shane Corbett"] :date: 2023-09-22 :info\_titleabbrev: Node efficiency and scaling :imagesdir: images/scalability/ Being efficient with our workloads and nodes reduces complexity/cost while increasing performance and scale. There are many fact... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/node_efficiency.adoc | mainline | aws-eks-best-practices | [
0.05605083703994751,
0.03968247026205063,
0.050388917326927185,
0.0595223493874073,
0.07423534244298935,
-0.013115257024765015,
-0.045529648661613464,
0.07278857380151749,
0.07775776833295822,
0.03931187093257904,
-0.05796530470252037,
0.018838558346033096,
0.010861847549676895,
-0.0193951... | 0.111936 |
CFS system is: busy containers (CGROUPS) are the only containers that count toward the share system. In this case, only the first container is busy so it is allowed to use all 4 cores on the node. image::cores-2.png[] Why does this matter? Let's say we ran our performance testing in a development cluster where an NGINX... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/node_efficiency.adoc | mainline | aws-eks-best-practices | [
0.016718285158276558,
-0.008633640594780445,
0.0028169932775199413,
0.05596546828746796,
0.06682635843753815,
-0.07052992284297943,
-0.03188960626721382,
0.044238463044166565,
0.03597251698374748,
0.014417702332139015,
-0.03516305983066559,
0.002619229955598712,
-0.01294846273958683,
-0.03... | 0.109986 |
where our node is completely full, yet our CPU utilization is zero. image::hpa-utilization.png[] === Setting Requests It would tempting to set the request at the "`sweet spot`" value for that application, however this would cause inefficiencies as pictured in the diagram below. Here we have set the request value to 2 v... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/node_efficiency.adoc | mainline | aws-eks-best-practices | [
0.03745495155453682,
0.03565121814608574,
0.03340902552008629,
0.0534113273024559,
-0.03437964245676994,
-0.07542679458856583,
0.00047243383596651256,
0.00898625236004591,
0.05255899205803871,
0.024869713932275772,
-0.0597379244863987,
-0.05517159029841423,
-0.04106973111629486,
-0.0688168... | 0.098097 |
- how much buffer do you want in your applications vertical scale before scaling a new pod? \* What metrics truly reflect the saturation of your application - The saturation metric for a Kafka Producer would be quite different than a complex web application. \* How do all the other applications on the node effect each ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/node_efficiency.adoc | mainline | aws-eks-best-practices | [
0.02352437935769558,
-0.030620822682976723,
-0.02474457025527954,
0.002608214970678091,
-0.03192368894815445,
-0.0732397586107254,
-0.06450897455215454,
0.07397246360778809,
0.009507733397185802,
0.03884332627058029,
-0.10853266716003418,
-0.022393593564629555,
-0.045901909470558167,
-0.08... | 0.138221 |
and allows us a great deal of flexibility when using custom and external metrics (non K8s metrics). As an example, we can scaling on the highest of three values (see below). We scale if the average utilization of all the pods are over 50%, if custom metrics the packets per second of the ingress exceed an average of 1,0... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/node_efficiency.adoc | mainline | aws-eks-best-practices | [
-0.008721095509827137,
0.0027273099403828382,
0.015074231661856174,
0.024520915001630783,
-0.017180930823087692,
-0.051672451198101044,
0.0077043320052325726,
0.048810333013534546,
0.06010909751057625,
0.07037065178155899,
-0.01745554246008396,
-0.06670666486024857,
-0.033848099410533905,
... | 0.233638 |
Real world data shows that this is the number one factor in scalability of Kubernetes clusters. image::smooth-scaling.png[] The key takeaway is CPU utilization is only one dimension of both application and node performance. Using CPU utilization as a sole health indicator for our nodes and applications creates problems... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/node_efficiency.adoc | mainline | aws-eks-best-practices | [
0.059288594871759415,
0.04256165400147438,
0.012662325985729694,
0.015180995687842369,
0.0028706826269626617,
-0.027490757405757904,
-0.013927871361374855,
0.05907974764704704,
0.02805767022073269,
0.013434200547635555,
-0.07884186506271362,
-0.03146281838417053,
-0.01186444703489542,
-0.0... | 0.110099 |
designed to act as a fail safe for memory leaks by terminating the pod completely. This is an all or nothing style proposition, however we have now been given new ways to address this problem. First, it is important to understand that setting the right amount of memory for containers is not a straightforward as it appe... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/scalability/node_efficiency.adoc | mainline | aws-eks-best-practices | [
0.03160429000854492,
0.08534009754657745,
0.01653173379600048,
0.028767485171556473,
-0.015603027306497097,
-0.00012473658716771752,
-0.023514287546277046,
0.0699763223528862,
0.06792213767766953,
0.055018823593854904,
-0.023788737133145332,
0.019228141754865646,
-0.050271932035684586,
-0.... | 0.164766 |
[."topic"] [[data-plane,data-plane.title]] = EKS Data Plane :info\_doctype: section :info\_title: EKS Data Plane :info\_abstract: EKS Data Plane :info\_titleabbrev: Data Plane :imagesdir: images/reliability/ To operate high-available and resilient applications, you need a highly-available and resilient data plane. An e... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/dataplane.adoc | mainline | aws-eks-best-practices | [
-0.014578362926840782,
0.03419204428792,
0.045462556183338165,
0.04480407387018204,
0.021825036033988,
-0.0171353742480278,
0.0056726462207734585,
-0.013007068075239658,
0.03036506660282612,
0.0939861387014389,
-0.05175993591547012,
0.0008346457616426051,
0.019693974405527115,
-0.033031061... | 0.220717 |
the topology spread constraint can't be fulfilled. It should only be set if its preferable for pods to not run instead of violating the topology spread constraint. ==== On older versions of Kubernetes, you can use pod anti-affinity rules to schedule pods across multiple AZs. The manifest below informs Kubernetes schedu... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/dataplane.adoc | mainline | aws-eks-best-practices | [
0.03651556372642517,
0.006192802917212248,
0.018943781033158302,
0.023817161098122597,
-0.027496306225657463,
-0.007444863207638264,
0.002363762818276882,
-0.06265004724264145,
0.04084213078022003,
0.056992001831531525,
-0.06134548410773277,
-0.06277448683977127,
0.04110005497932434,
0.021... | 0.128024 |
to sizing resource requests and limits for workloads: \* Do not specify resource limits on CPU. In the absence of limits, the request acts as a weight on https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#how-pods-with-resource-limits-are-run[how much relative CPU time containers get]. This ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/dataplane.adoc | mainline | aws-eks-best-practices | [
0.020785128697752953,
0.055233173072338104,
0.04094851762056351,
0.01927555724978447,
-0.03535928949713707,
-0.06789785623550415,
-0.021754061803221703,
0.0030608156230300665,
0.06331310421228409,
0.029769636690616608,
-0.06380114704370499,
-0.029948364943265915,
-0.053076986223459244,
-0.... | 0.14337 |
nodes as a DaemonSet. All the pods use the DNS caching agent running on the node for name resolution instead of using `kube-dns` Service. This feature is automatically included in EKS Auto Mode. === Configure auto-scaling CoreDNS Another method of improving Cluster DNS performance is by enabling the built-in https://do... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/dataplane.adoc | mainline | aws-eks-best-practices | [
-0.02451976016163826,
-0.011657295748591423,
0.03707897290587425,
0.0372944250702858,
-0.06795764714479446,
0.003796967677772045,
-0.06094936653971672,
-0.028626084327697754,
0.11877413839101791,
0.06429877877235413,
-0.056966252624988556,
-0.018193121999502182,
0.0068041677586734295,
-0.0... | 0.202538 |
//!!NODE\_ROOT [[reliability,reliability.title]] = Amazon EKS Best Practices Guide for Reliability :doctype: book :sectnums: :toc: left :icons: font :experimental: :idprefix: :idseparator: - :sourcedir: . :info\_doctype: chapter :info\_title: Best Practices for Reliability :info\_abstract: Best Practices for Reliabilit... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/index.adoc | mainline | aws-eks-best-practices | [
-0.05970451608300209,
0.006637895945459604,
0.0030330466106534004,
0.067043736577034,
0.02951422892510891,
-0.04048825055360794,
0.004631727002561092,
0.04339421167969704,
-0.0023221569135785103,
0.037324629724025726,
-0.02888176590204239,
-0.008030137047171593,
0.09743883460760117,
-0.066... | 0.223854 |
on managed node groups. Because managed nodes run the Amazon EKS-optimized AMIs, Amazon EKS is responsible for building patched versions of these AMIs when bug fixes. However, you are responsible for deploying these patched AMI versions to your managed node groups. EKS also https://docs.aws.amazon.com/eks/latest/usergu... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/index.adoc | mainline | aws-eks-best-practices | [
-0.023791564628481865,
-0.005516210570931435,
0.04202010855078697,
0.06072348728775978,
0.07394140958786011,
-0.07972226291894913,
-0.04401259124279022,
-0.07833360880613327,
0.037276990711688995,
0.15507245063781738,
0.04508386552333832,
-0.016451386734843254,
0.03762442618608475,
-0.0846... | 0.169484 |
[."topic"] [[application,application.title]] = Running highly-available applications :info\_doctype: section :info\_title: Running highly-available applications :info\_abstract: Running highly-available applications :info\_titleabbrev: Applications :imagesdir: images/reliability/ Your customers expect your application ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/application.adoc | mainline | aws-eks-best-practices | [
-0.0050989557057619095,
0.009169832803308964,
0.08107419312000275,
-0.03185757249593735,
0.032130226492881775,
-0.010730687528848648,
0.030443483963608742,
0.0595332533121109,
0.05048424378037453,
-0.00930383987724781,
-0.06455472856760025,
0.01573890820145607,
0.051231496036052704,
-0.027... | 0.229841 |
pod topology spread constraints allow you to make your application available across different failure (or topology) domains like hosts or AZs. This approach works very well when you're trying to ensure fault tolerance as well as availability by having multiple replicas in each of the different topology domains. Pod ant... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/application.adoc | mainline | aws-eks-best-practices | [
-0.002382720820605755,
-0.045466646552085876,
0.039903998374938965,
-0.005773947574198246,
0.02874133549630642,
-0.04472876340150833,
-0.05231456086039543,
0.036151766777038574,
0.011453939601778984,
0.012948275543749332,
-0.08343540132045746,
-0.0032283752225339413,
0.058267198503017426,
... | 0.157805 |
demand and help you avoid impacting your customers during peak traffic. It is implemented as a control loop in Kubernetes that periodically queries metrics from APIs that provide resource metrics. HPA can retrieve metrics from the following APIs: 1. `metrics.k8s.io` also known as Resource Metrics API — Provides CPU and... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/application.adoc | mainline | aws-eks-best-practices | [
-0.030039725825190544,
0.005462174769490957,
-0.007293618284165859,
0.015215044841170311,
-0.09831921756267548,
-0.022739160805940628,
0.012709119357168674,
0.05145842209458351,
0.07228847593069077,
0.016704929992556572,
-0.07628302276134491,
-0.07033737748861313,
-0.04784054309129715,
-0.... | 0.21586 |
the container image. You can use `kubectl` to update a Deployment like this: [source,bash] ---- kubectl --record deployment.apps/nginx-deployment set image nginx-deployment nginx=nginx:1.16.1 ---- The `--record` argument record the changes to the Deployment and helps you if you need to perform a rollback. `kubectl roll... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/application.adoc | mainline | aws-eks-best-practices | [
0.004137999843806028,
0.028658533468842506,
0.05483369529247284,
-0.011773625388741493,
-0.01653578318655491,
-0.036892205476760864,
-0.041393645107746124,
-0.06709542125463486,
0.01602102443575859,
0.07695863395929337,
-0.005012128967791796,
0.00859766360372305,
0.01278309803456068,
-0.02... | 0.08695 |
all traffic to the old Deployment and stop sending traffic to the new Deployment. Although Kubernetes offers no native way to perform canary deployments, you can use tools such as https://github.com/weaveworks/flagger[Flagger] with https://docs.flagger.app/tutorials/istio-progressive-delivery[Istio]. == Health checks a... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/application.adoc | mainline | aws-eks-best-practices | [
0.08345317840576172,
-0.02908189408481121,
0.10241172462701797,
-0.026867330074310303,
0.018724996596574783,
-0.05095934867858887,
-0.006484304089099169,
0.01778756082057953,
-0.019648587331175804,
0.06038666516542435,
-0.024964742362499237,
-0.009837949648499489,
-0.024970225989818573,
-0... | 0.294215 |
the maximum configured time, the Pod still fails Startup Probes, it will be terminated, and a new Pod will be created. The Startup Probe is similar to the Liveness Probe – if they fail, the Pod is recreated. As Ricardo A. explains in his post https://medium.com/swlh/fantastic-probes-and-how-to-configure-them-fef7e030bd... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/application.adoc | mainline | aws-eks-best-practices | [
0.03867638111114502,
-0.07442272454500198,
0.007076670415699482,
0.03730214014649391,
0.06562820822000504,
-0.07890880852937698,
-0.062262147665023804,
0.048909079283475876,
-0.017806120216846466,
0.04359244182705879,
-0.02141730673611164,
0.009905162267386913,
-0.04111533984541893,
0.0459... | 0.131407 |
signal is sent. This grace period is 30 seconds by default; you can override the default by using `grace-period` flag in kubectl or declare `terminationGracePeriodSeconds` in your Podspec. `kubectl delete pod —grace-period=` It is common to have containers in which the main process doesn't have PID 1. Consider this Pyt... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/application.adoc | mainline | aws-eks-best-practices | [
0.006758176255971193,
0.006165831349790096,
0.03033613972365856,
-0.03512359410524368,
-0.012241392396390438,
-0.05208013579249382,
-0.007440392859280109,
0.008357471786439419,
0.13516153395175934,
0.045357320457696915,
-0.04449334368109703,
-0.01070624403655529,
-0.013702824711799622,
-0.... | 0.142614 |
system deviates, Kubernetes will take action to restore the state. For example, if a worker node becomes unavailable, Kubernetes will reschedule the Pods onto another worker node. Similarly, if a `replica` crashes, the https://kubernetes.io/docs/concepts/architecture/controller/#design[Deployment Contoller] will create... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/application.adoc | mainline | aws-eks-best-practices | [
-0.013985874131321907,
-0.01921851933002472,
0.07278425246477127,
0.0041723353788256645,
0.014103704132139683,
-0.02427225187420845,
-0.03523216024041176,
-0.018252605572342873,
0.028003117069602013,
0.044995225965976715,
-0.06950703263282776,
0.02659173496067524,
0.030993899330496788,
-0.... | 0.197701 |
application metrics In addition to monitoring the state of the application and aggregating standard metrics, you can also use the https://prometheus.io/docs/instrumenting/clientlibs/[Prometheus client library] to expose application-specific custom metrics to improve the application's observability. === Use centralized ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/application.adoc | mainline | aws-eks-best-practices | [
0.008276043459773064,
-0.003899203147739172,
-0.004748648032546043,
0.05084332451224327,
0.02056923322379589,
-0.06206647306680679,
0.020632976666092873,
0.002900207880884409,
0.09530895948410034,
0.10024265199899673,
-0.05716550350189209,
-0.06962354481220245,
0.003392904531210661,
-0.003... | 0.191365 |
[."topic"] [[control-plane,control-plane.title]] = EKS Control Plane :info\_doctype: section :info\_title: EKS Control Plane :info\_abstract: EKS Control Plane :info\_titleabbrev: Control Plane :imagesdir: images/reliability/ :idprefix: reliability-cp TIP: https://aws-experience.com/emea/smb/events/series/get-hands-on-... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/controlplane.adoc | mainline | aws-eks-best-practices | [
-0.03808348625898361,
-0.00517427921295166,
-0.02831522561609745,
0.01888120546936989,
0.026466386392712593,
0.03292129188776016,
0.02660788968205452,
-0.024456128478050232,
0.07467375695705414,
0.07825262099504471,
-0.01523932721465826,
-0.008934516459703445,
0.021574631333351135,
-0.0524... | 0.172456 |
example, `apiserver\_request\_duration\_seconds` can indicate how long API requests are taking to run. Consider monitoring these control plane metrics: === API Server [width="100%",cols="<50%,<50%",options="header",] |=== |Metric |Description |`apiserver\_request\_total` |Counter of apiserver requests broken out for ea... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/controlplane.adoc | mainline | aws-eks-best-practices | [
0.03882039710879326,
-0.010840414091944695,
-0.09387782216072083,
0.05836792290210724,
0.024785036221146584,
-0.050179723650217056,
-0.010020219720900059,
0.00580171775072813,
0.027089593932032585,
0.05784312263131142,
-0.016511498019099236,
-0.09915225207805634,
0.028223322704434395,
-0.0... | 0.11434 |
# - get-token # - --cluster-name # - <> # command: aws # env: null - name: super-admin user: token: <> .... == Admission Webhooks Kubernetes has two types of admission webhooks: https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers[validating admission webhooks and mutating admission ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/controlplane.adoc | mainline | aws-eks-best-practices | [
-0.008948703296482563,
0.06840240210294724,
0.017487209290266037,
0.010181260295212269,
0.016353193670511246,
-0.038409944623708725,
0.015531268902122974,
-0.046866122633218765,
0.05915503948926926,
0.09626089781522751,
-0.011565612629055977,
-0.09082548320293427,
0.04144221916794777,
-0.0... | 0.171014 |
continue to use outdated IP addresses for a short period of time. To mitigate these issues, Kubernetes API consumers (such as kubectl, CI/CD pipelines, and custom applications) should implement the following best practices: \* Implement DNS re-resolution \* Implement Retries with Backoff and Jitter. For example, see ht... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/reliability/controlplane.adoc | mainline | aws-eks-best-practices | [
-0.015479360707104206,
0.05386081337928772,
0.09435604512691498,
-0.0007047256221994758,
-0.10398316383361816,
-0.02494555525481701,
-0.11199414730072021,
-0.06072764843702316,
0.08273942768573761,
0.02660856954753399,
-0.06022495776414871,
-0.010515104047954082,
-0.03610827028751373,
-0.1... | 0.072492 |
//!!NODE\_ROOT [."topic"] [[cluster-upgrades,cluster-upgrades.title]] = Best Practices for Cluster Upgrades :doctype: book :sectnums: :toc: left :icons: font :experimental: :idprefix: :idseparator: - :sourcedir: . :info\_doctype: chapter :info\_title: Best Practices for Cluster Upgrades :info\_abstract: Best Practices ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/upgrades/index.adoc | mainline | aws-eks-best-practices | [
-0.011223817244172096,
0.04473095387220383,
0.01273400243371725,
0.05967579782009125,
0.028914691880345345,
-0.015910588204860687,
-0.037452515214681625,
-0.062315210700035095,
-0.0421215184032917,
0.08311077207326889,
0.02228422835469246,
-0.01309883315116167,
0.053794678300619125,
-0.104... | 0.166798 |
API versions. This can help ensure that your configurations remain compatible with the new Kubernetes version. == Keep your cluster up-to-date Staying current with Kubernetes updates is paramount for a secure and efficient EKS environment, reflecting the shared responsibility model in Amazon EKS. By integrating these s... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/upgrades/index.adoc | mainline | aws-eks-best-practices | [
-0.0029731467366218567,
0.019603334367275238,
0.0871729627251625,
0.02049327827990055,
0.05561559647321701,
0.006212493870407343,
-0.09145783632993698,
-0.04301201179623604,
0.08210303634405136,
0.07010220736265182,
-0.014244095422327518,
0.007583382073789835,
-0.008415419608354568,
-0.039... | 0.162054 |
is more complicated, and has a higher risk of downtime. In this situation, see <>. == Upgrade your control plane and data plane in sequence To upgrade a cluster you will need to take the following actions: [arabic] . xref:usedocs[Review the Kubernetes and EKS release notes.] . xref:backup-the-cluster-before-upgrading[T... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/upgrades/index.adoc | mainline | aws-eks-best-practices | [
0.004683570470660925,
-0.03529716655611992,
0.003460156498476863,
-0.0039482275024056435,
0.07426756620407104,
0.00021920276049058884,
-0.03888365998864174,
-0.030362950637936592,
0.037698183208703995,
0.07510270923376083,
0.020813457667827606,
-0.034560125321149826,
0.014635281637310982,
... | 0.090873 |
their relevant upgrade documentation: \* \*Amazon VPC CNI:\* For the recommended version of the Amazon VPC CNI add-on for each cluster version, see https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html[Updating the Amazon VPC CNI plugin for Kubernetes self-managed add-on]. \*When installed as an Amazon... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/upgrades/index.adoc | mainline | aws-eks-best-practices | [
-0.036304060369729996,
-0.04946964979171753,
0.008812671527266502,
-0.035429421812295914,
0.016447629779577255,
0.03664429858326912,
-0.08705941587686539,
-0.08759429305791855,
0.04188881441950798,
0.09383043646812439,
-0.013361020013689995,
-0.03314193710684776,
0.0018530270317569375,
-0.... | 0.104134 |
the new subnets you will be provided: \* belong to same set of AZs that are selected during cluster creation. \* belong to the same VPC provided during cluster creation Please consider associating additional CIDR blocks if the IP addresses in the existing VPC CIDR block run out. AWS enables the association of additiona... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/upgrades/index.adoc | mainline | aws-eks-best-practices | [
-0.05243228003382683,
-0.06970671564340591,
-0.022280091419816017,
0.06296006590127945,
0.03563568741083145,
0.027736788615584373,
0.008723923936486244,
-0.10286660492420197,
0.03838114067912102,
0.056170057505369186,
0.01420770026743412,
-0.07059622555971146,
0.07684341073036194,
0.007837... | 0.06284 |
[ { "category": "UPGRADE\_READINESS", "name": "Deprecated APIs removed in Kubernetes v1.29", "insightStatus": { "status": "PASSING", "reason": "No deprecated API usage detected within the last 30 days." }, "kubernetesVersion": "1.29", "lastTransitionTime": 1698774710.0, "lastRefreshTime": 1700157422.0, "id": "123e4567-... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/upgrades/index.adoc | mainline | aws-eks-best-practices | [
-0.007638311944901943,
-0.004447191022336483,
0.035473037511110306,
0.051616642624139786,
0.07413499802350998,
-0.017835378646850586,
-0.012006036937236786,
-0.0345393531024456,
0.08929625153541565,
0.07443342357873917,
-0.014584077522158623,
-0.05807720869779587,
-0.0312834270298481,
-0.0... | 0.173508 |
logs start-query \ --log-group-name /aws/eks/${CLUSTER}/cluster \ --start-time $(date -u --date="-30 minutes" "+%s") # or date -v-30M "+%s" on MacOS \ --end-time $(date "+%s") \ --query-string 'fields @message | filter `annotations.k8s.io/deprecated`="true"' \ --query queryId --output text) echo "Query started (query i... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/upgrades/index.adoc | mainline | aws-eks-best-practices | [
0.06076647713780403,
0.0805201381444931,
0.024112381041049957,
0.10327392816543579,
0.09046343713998795,
0.004634144250303507,
-0.01967056840658188,
-0.057469289749860764,
0.0964236930012703,
0.0457472950220108,
0.025691989809274673,
-0.07706569135189056,
-0.012766215018928051,
0.001584613... | 0.080307 |
control plane Before proceeding with a Kubernetes upgrade in Amazon EKS, it's vital to ensure compatibility between your managed node groups, self-managed nodes, and the control plane. Compatibility is determined by the Kubernetes version you are using, and it varies based on different scenarios. Tactics: \* \*Kubernet... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/upgrades/index.adoc | mainline | aws-eks-best-practices | [
-0.002443456556648016,
-0.022088423371315002,
0.04734403267502785,
-0.0020322275813668966,
0.02120719477534294,
0.03156979754567146,
-0.0838417112827301,
-0.07112369686365128,
0.09560026228427887,
0.05230821669101715,
-0.011786387301981449,
0.007068351376801729,
-0.023048531264066696,
-0.0... | 0.062925 |
self-managed nodes.] Some common tools include: \* https://eksctl.io/usage/nodegroup-upgrade/[eksctl] \* https://kops.sigs.k8s.io/operations/updates\_and\_upgrades/[kOps] \* https://aws-ia.github.io/terraform-aws-eks-blueprints/node-groups/#self-managed-node-groups[EKS Blueprints] == Backup the cluster before upgrading... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/upgrades/index.adoc | mainline | aws-eks-best-practices | [
-0.012256811372935772,
0.02996712736785412,
0.06829607486724854,
0.03623923286795616,
0.0469222292304039,
-0.020148444920778275,
-0.05942339077591896,
-0.06342948973178864,
0.02607482671737671,
0.10713335126638412,
-0.010114637203514576,
-0.01699008047580719,
0.028806472197175026,
-0.05466... | 0.126766 |
Optimized AMI for 1.25 no longer includes support for Dockershim. If you have a dependency on Dockershim, e.g. you are mounting the Docker socket, you will need to remove those dependencies before upgrading your worker nodes to 1.25. Find instances where you have a dependency on the Docker socket before upgrading to 1.... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/upgrades/index.adoc | mainline | aws-eks-best-practices | [
-0.0035707755014300346,
0.039796069264411926,
0.08017899841070175,
-0.0032906567212194204,
0.09646017104387283,
-0.041738975793123245,
0.021300530061125755,
-0.055808112025260925,
0.0044579231180250645,
0.09905117750167847,
0.021451976150274277,
-0.06622922420501709,
0.05236830189824104,
0... | 0.105808 |
[."topic"] [#windows-patching] = Patching Windows Servers and Containers :info\_doctype: section :info\_titleabbrev: Infrastructure Management :imagesdir: images/windows/ Patching Windows Server is a standard management task for Windows Administrators. This can be accomplished using different tools like Amazon System M... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/patching.adoc | mainline | aws-eks-best-practices | [
-0.0014932405902072787,
0.03620194271206856,
0.05838257819414139,
0.016472453251481056,
0.019270790740847588,
-0.0050439354963600636,
-0.01593780517578125,
-0.049765992909669876,
-0.017297180369496346,
0.08758410066366196,
-0.004903310909867287,
-0.07159116864204407,
0.07770922034978867,
-... | 0.077916 |
= 6.96GB \* Difference on disk = 1.2GB \* Fluentd https://docs.aws.amazon.com/AmazonECR/latest/userguide/repository-info.html[compressed final image ECR] = 533.05MB The base image already exists on the local disk, resulting in the total amount on disk being 1.2GB additional. The next time you see the amount of GBs in t... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/patching.adoc | mainline | aws-eks-best-practices | [
0.04450324550271034,
0.08113350719213486,
0.024893175810575485,
0.02119279094040394,
0.09012336283922195,
-0.09057744592428207,
-0.03856330364942551,
0.012425780296325684,
0.06049397215247154,
0.045537319034338,
-0.006953496020287275,
-0.0375029630959034,
0.007695187348872423,
-0.029384108... | -0.033649 |
[."topic"] [#windows-ami] = Amazon EKS optimized Windows AMI management :info\_doctype: section :info\_titleabbrev: AMI Management :imagesdir: images/windows/ Windows Amazon EKS optimized AMIs are built on top of Windows Server 2019 and Windows Server 2022. They are configured to serve as the base image for Amazon EKS ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/ami.adoc | mainline | aws-eks-best-practices | [
-0.004536493215709925,
0.058376237750053406,
0.0026132098864763975,
-0.011183802038431168,
0.008204848505556583,
0.03716589882969856,
0.005965480115264654,
-0.01886572316288948,
0.060177870094776154,
0.05688243731856346,
0.03118482232093811,
-0.0940425768494606,
0.04931344464421272,
0.0072... | 0.1523 |
parallel process, meaning the container runtime pulls the container image layers in parallel. In contrast, the extraction operation occurs in a sequential process, and it is I/O intensive. Due to that, the container image can take more than 8 minutes to be fully extracted and ready to be used by the container runtime (... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/ami.adoc | mainline | aws-eks-best-practices | [
0.01760079525411129,
0.08176563680171967,
0.07420849800109863,
0.026616306975483894,
0.06207917258143425,
-0.061518069356679916,
-0.057422179728746414,
-0.009507306851446629,
0.05141659453511238,
0.0580187551677227,
0.03457197919487953,
-0.03761778771877289,
-0.010618548840284348,
-0.04096... | 0.089856 |
[."topic"] [#windows-logging] = Logging :info\_doctype: section :imagesdir: images/windows/ Containerized applications typically direct application logs to STDOUT. The container runtime traps these logs and does something with them - typically writes to a file. Where these files are stored depends on the container runt... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/logging.adoc | mainline | aws-eks-best-practices | [
0.09004806727170944,
0.024617431685328484,
0.03605400025844574,
0.04647192358970642,
0.11141972243785858,
-0.009946790523827076,
0.028233610093593597,
-0.004431870300322771,
0.06429256498813629,
0.06675306707620621,
-0.03507237508893013,
-0.07003432512283325,
-0.036883436143398285,
0.03829... | 0.154836 |
[."topic"] [#windows-networking] = Windows Networking :info\_doctype: section :imagesdir: images/windows/ == Windows Container Networking Overview Windows containers are fundamentally different than Linux containers. Linux containers use Linux constructs like namespaces, the union file system, and cgroups. On Windows, ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/networking.adoc | mainline | aws-eks-best-practices | [
-0.0056125083938241005,
0.06791536509990692,
-0.06832248717546463,
-0.010060220025479794,
0.021143632009625435,
0.009321952238678932,
0.03758964315056801,
-0.029934272170066833,
0.014245516620576382,
0.01051624771207571,
-0.06708426773548126,
-0.026679372414946556,
0.0494728684425354,
-0.0... | 0.217681 |
therefore recommend enabling DSR on Windows nodes. DSR is enabled by default in Windows Server SAC EKS Optimized AMIs. For Windows Server 2019 LTSC EKS Optimized AMIs, you will need to enable it during instance provisioning using the script below and by using Windows Server 2019 Full or Core as the amiFamily in the `ek... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/networking.adoc | mainline | aws-eks-best-practices | [
-0.04521213844418526,
0.02840781770646572,
-0.003971207421272993,
0.015639813616871834,
-0.031996019184589386,
0.011943673714995384,
-0.06269664317369461,
-0.0048899040557444096,
0.03647322952747345,
0.02735367976129055,
-0.018619272857904434,
-0.05902975797653198,
-0.029382118955254555,
0... | 0.054534 |
CNI that works with EKS. Instructions for installing Calico CNI in EKS can be found on the https://docs.projectcalico.org/getting-started/kubernetes/managed-public-cloud/eks[Project Calico EKS installation] page. == Network Polices It is considered a best practice to change from the default mode of open communication b... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/networking.adoc | mainline | aws-eks-best-practices | [
0.012754962779581547,
0.011141890659928322,
0.002244826639071107,
-0.03355547785758972,
0.008067882619798183,
0.02348145842552185,
-0.005259750410914421,
-0.051437247544527054,
0.06445042788982391,
0.07161556929349899,
-0.002299947664141655,
-0.08254174888134003,
-0.000948857341427356,
-0.... | 0.233713 |
[."topic"] [#windows-images] = Container image scanning :info\_doctype: section :info\_titleabbrev: Scanning Windows Images :imagesdir: images/windows/ Image Scanning is an automated vulnerability assessment feature that helps improve the security of your application's container images by scanning them for a broad rang... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/images.adoc | mainline | aws-eks-best-practices | [
0.029136745259165764,
0.10630624741315842,
-0.03691575676202774,
-0.008824137970805168,
0.11070422828197479,
-0.01860332302749157,
0.03664848580956459,
0.00853710062801838,
-0.048488929867744446,
0.01769278757274151,
0.02133924514055252,
-0.021723894402384758,
0.07863927632570267,
0.039181... | 0.15154 |
[."topic"] [#windows-security] = Pod Security Contexts :info\_doctype: section :info\_titleabbrev: Pod Security for Windows Containers :imagesdir: images/windows/ \*Pod Security Policies (PSP)\* and \*Pod Security Standards (PSS)\* are two main ways of enforcing security in Kubernetes. Note that PodSecurityPolicy is de... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/security.adoc | mainline | aws-eks-best-practices | [
0.001660554320551455,
0.06655708700418472,
0.03279419243335724,
-0.021741630509495735,
0.08703801035881042,
0.0392373763024807,
0.08396568149328232,
0.0035610890481621027,
0.03349721431732178,
0.06333978474140167,
0.00999708753079176,
-0.025357801467180252,
0.04585641250014305,
0.027932696... | 0.212581 |
kind: Pod metadata: name: run-as-username-pod-demo spec: securityContext: windowsOptions: runAsUserName: "ContainerUser" containers: - name: run-as-username-demo nodeSelector: kubernetes.io/os: windows ---- Whereas in the following, the container level security context overrides the pod level security context. [source,... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/security.adoc | mainline | aws-eks-best-practices | [
0.06319909542798996,
0.03637067973613739,
-0.0032234108075499535,
-0.012151120230555534,
0.024727143347263336,
-0.021627157926559448,
0.07217276841402054,
-0.02046140655875206,
0.028301861137151718,
0.031320102512836456,
-0.010121019557118416,
-0.08870092034339905,
-0.012190638110041618,
0... | 0.127409 |
[."topic"] [#windows-hardening-containers-images] = Hardening Windows container images :info\_doctype: section :info\_titleabbrev: Hardening Windows containers images :imagesdir: images/windows/ Are you hardening your Windows container images? Over the years, I've worked with customers globally to help them migrate leg... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/hardening_container_image.adoc | mainline | aws-eks-best-practices | [
-0.006453962065279484,
0.07792963087558746,
0.04910603165626526,
0.021220827475190163,
0.09890814870595932,
-0.050660260021686554,
0.048986319452524185,
-0.017887167632579803,
-0.025624705478549004,
0.008083194494247437,
-0.020822957158088684,
0.03903485834598541,
0.026216911152005196,
0.0... | 0.090955 |
that your Windows container is hardened against unauthorized access or password-based attacks, aligning the security posture of your container with the broader system security policies. === Protection Against Brute Force Attacks \* Account Lockout: These settings help defend against brute force login attempts by lockin... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/hardening_container_image.adoc | mainline | aws-eks-best-practices | [
0.014682333916425705,
0.06733638048171997,
-0.00040531656122766435,
-0.029770396649837494,
0.0437149740755558,
0.028057701885700226,
0.029577624052762985,
-0.01477420050650835,
0.02020144648849964,
0.009236505255103111,
-0.01165100373327732,
0.0010511849541217089,
0.02537768892943859,
0.00... | 0.138133 |
containerized application or service is compromised, audit logs can provide valuable insights for post-incident analysis. They help security teams trace the actions taken by attackers or identify how a breach occurred. \* Real-time Detection: Audit logs allow administrators to set up real-time alerts for critical event... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/hardening_container_image.adoc | mainline | aws-eks-best-practices | [
0.018411055207252502,
0.06958995014429092,
0.017997877672314644,
-0.006538363639265299,
0.1161995604634285,
-0.0059229410253465176,
0.08825216442346573,
-0.029574669897556305,
0.019657982513308525,
0.0449308417737484,
-0.018078504130244255,
-0.026763953268527985,
-0.014963479712605476,
0.0... | 0.226988 |
best practices for Windows containers Implementing IIS best practices in Windows Containers is important for several reasons, ensuring that your applications are secure, high performance, and scalable. Although containers provide isolation and a lightweight environment, they still require proper configuration to avoid ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/hardening_container_image.adoc | mainline | aws-eks-best-practices | [
-0.002185901626944542,
0.12324000149965286,
0.021444138139486313,
0.036454156041145325,
0.038299884647130966,
0.003850445384159684,
0.04214511066675186,
0.02872682549059391,
0.021436337381601334,
0.0010305549949407578,
-0.04846906661987305,
0.0027156847063452005,
0.016326554119586945,
0.04... | 0.114814 |
or updates is minimized. Dockerfile: ---- # Enforce HTTPS (disable HTTP) -- Only if container is target for SSL termination RUN powershell -Command \ "$httpBinding = Get-WebBinding -Name 'Default Web Site' -Protocol http | Where-Object { $\_.bindingInformation -eq '\*:80:' }; \ if ($httpBinding) { Remove-WebBinding -Na... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/hardening_container_image.adoc | mainline | aws-eks-best-practices | [
0.051075272262096405,
0.08892843127250671,
-0.031197229400277138,
0.019889457151293755,
-0.005420682020485401,
-0.06468053162097931,
0.002106612781062722,
-0.09723307192325592,
-0.02308383770287037,
0.09912194311618805,
0.013029586523771286,
-0.04622511565685272,
-0.008895902894437313,
0.0... | -0.061849 |
targeting vulnerabilities specific to the IIS version. . \*Enable HTTPS-only connections\* This (commented-out) section enforces HTTPS connections and disables HTTP. If uncommented, the Dockerfile will configure IIS to listen only on port 443 (HTTPS) and remove the default HTTP binding on port 80. This is useful when t... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/hardening_container_image.adoc | mainline | aws-eks-best-practices | [
-0.026744117960333824,
0.13282039761543274,
-0.015348806045949459,
0.013882240280508995,
0.027278203517198563,
-0.02452833764255047,
-0.03147309646010399,
0.04047137871384621,
0.030061161145567894,
0.013416348956525326,
0.014261109754443169,
0.0056331888772547245,
0.0074799880385398865,
0.... | 0.18325 |
and Auditing\* \* Many regulatory standards and security frameworks (e.g., PCI DSS, HIPAA, GDPR) require systems to adhere to PoLP to limit access to sensitive data. Running Windows containers with restricted privileges helps organizations comply with these regulations and ensures that applications are only granted acc... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/hardening_container_image.adoc | mainline | aws-eks-best-practices | [
-0.03712004795670509,
0.1353025585412979,
0.023315545171499252,
-0.037602003663778305,
0.05924893170595169,
0.03676166757941246,
0.06296920031309128,
0.02196727879345417,
-0.0066583906300365925,
0.008939717896282673,
-0.03546424210071564,
0.038229603320360184,
-0.0008685454376973212,
0.029... | 0.150939 |
securing your Windows containers is not just a recommendation, it's an absolute necessity. Containers provide a lightweight, flexible way to package and deploy applications, but they are not immune to security vulnerabilities. As more businesses adopt containers to streamline their infrastructure, they also become a po... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/hardening_container_image.adoc | mainline | aws-eks-best-practices | [
0.023344088345766068,
0.09987617284059525,
0.04818475991487503,
0.021448642015457153,
0.054552339017391205,
0.07247225940227509,
0.05711425468325615,
-0.008244778029620647,
0.004737732466310263,
0.03592521324753761,
-0.07899057120084763,
-0.03487363085150719,
-0.0024861698038876057,
0.0656... | 0.081354 |
[."topic"] [#windows-scheduling] = Running Heterogeneous workloads :info\_doctype: section :doctype: book :info\_titleabbrev: Scheduling :imagesdir: images/windows/ Kubernetes has support for heterogeneous clusters where you can have a mixture of Linux and Windows nodes in the same cluster. Within that cluster, you can... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/scheduling.adoc | mainline | aws-eks-best-practices | [
0.04226132854819298,
0.01475053932517767,
0.044619329273700714,
0.03672504052519798,
0.02593143843114376,
-0.00887945294380188,
-0.0134181072935462,
-0.017999913543462753,
0.015931688249111176,
-0.016162125393748283,
-0.0954182893037796,
-0.0634743943810463,
-0.029332533478736877,
0.025054... | 0.157758 |
build version. [,bash] ---- NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME ip-10-10-2-235.ec2.internal Ready 23m v1.24.7-eks-fb459a0 10.10.2.235 3.236.30.157 Windows Server 2022 Datacenter 10.0.20348.1607 containerd://1.6.6 ip-10-10-31-27.ec2.internal Ready 23m v1.24.7-e... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/scheduling.adoc | mainline | aws-eks-best-practices | [
0.03088461607694626,
0.05218246206641197,
-0.029661251232028008,
-0.059030529111623764,
0.12551961839199066,
-0.029112109914422035,
-0.05973130092024803,
-0.01058849599212408,
0.023878276348114014,
0.06118842959403992,
0.05214923247694969,
-0.08425069600343704,
0.0020747443195432425,
-0.03... | 0.093211 |
[."topic"] [#windows-hardening] = Windows worker nodes hardening :info\_doctype: section :info\_titleabbrev: Windows Server Hardening :imagesdir: images/windows/ OS Hardening is a combination of OS configuration, patching, and removing unnecessary software packages, which aim to lock down a system and reduce the attack... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/hardening.adoc | mainline | aws-eks-best-practices | [
-0.037162430584430695,
0.07599833607673645,
0.026250194758176804,
0.053540509194135666,
0.08977074921131134,
-0.00799690093845129,
0.07230225950479507,
-0.015649324283003807,
-0.050937384366989136,
0.023989109322428703,
0.027676166966557503,
0.005698945838958025,
0.06380575895309448,
0.023... | 0.11937 |
improve the security and compliance of applications deployed on AWS. Amazon Inspector automatically assesses applications for exposure, vulnerabilities, and deviations from best practices. After performing an assessment, Amazon Inspector produces a detailed list of security findings prioritized by level of severity. Th... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/hardening.adoc | mainline | aws-eks-best-practices | [
0.018048280850052834,
0.04457306116819382,
-0.06173675134778023,
0.044961173087358475,
0.08519425243139267,
0.029924901202321053,
-0.0073766247369349,
-0.022896353155374527,
0.009849450550973415,
0.07342388480901718,
-0.04510363191366196,
-0.06349154561758041,
0.047833241522312164,
-0.0269... | 0.054383 |
[."topic"] [#windows-gmsa] = Configure gMSA for Windows Pods and containers :info\_doctype: section :info\_titleabbrev: gMSA for Windows Containers :imagesdir: images/windows/ == What is a gMSA account Windows-based applications such as .NET applications often use Active Directory as an identity provider, providing aut... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/gmsa.adoc | mainline | aws-eks-best-practices | [
-0.002471678424626589,
0.04369022324681282,
0.03101389668881893,
-0.03812563419342041,
0.050240274518728256,
-0.011039656586945057,
0.1060929149389267,
-0.00831733550876379,
0.0012641518842428923,
0.049084488302469254,
-0.08054380863904953,
0.007804153487086296,
0.015491516329348087,
0.018... | 0.15016 |
'IIS:\' -Location 'SiteName' ---- | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/gmsa.adoc | mainline | aws-eks-best-practices | [
0.031372327357530594,
0.008019881322979927,
-0.07650621235370636,
-0.008224517107009888,
-0.026644902303814888,
-0.07292617857456207,
0.06912465393543243,
0.008034692145884037,
0.004410404711961746,
0.06906770914793015,
0.00471061235293746,
-0.05017460882663727,
0.04561935365200043,
0.0583... | 0.080963 |
[."topic"] [#windows-oom] = Avoiding OOM errors :info\_doctype: section :info\_titleabbrev: Memory and Systems Management :imagesdir: images/windows/ Windows does not have an out-of-memory process killer as Linux does. Windows always treats all user-mode memory allocations as virtual, and pagefiles are mandatory. The n... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/oom.adoc | mainline | aws-eks-best-practices | [
0.04232817143201828,
0.03088071197271347,
-0.031845346093177795,
-0.007174511440098286,
-0.00014165528409648687,
-0.016988854855298996,
0.024524983018636703,
0.01969187520444393,
0.07253702729940414,
0.03368276730179787,
0.00844366755336523,
0.06986985355615616,
0.0038282866589725018,
-0.0... | 0.148045 |
//!!NODE\_ROOT [[windows,windows.title]] = Amazon EKS Best Practices Guide for Windows :doctype: book :sectnums: :toc: left :icons: font :experimental: :idprefix: :idseparator: - :sourcedir: . :info\_doctype: chapter :info\_title: Best Practices for Windows :info\_abstract: Best Practices for Windows :info\_titleabbrev... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/index.adoc | mainline | aws-eks-best-practices | [
0.006979573052376509,
0.0897405669093132,
-0.008013654500246048,
0.03670172765851021,
0.13944198191165924,
-0.03403366729617119,
0.03375525400042534,
-0.023619430139660835,
0.009066006168723106,
0.05796193704009056,
-0.00033541928860358894,
-0.026752419769763947,
0.02081378363072872,
-0.03... | 0.113892 |
[."topic"] [#windows-licensing] = Windows Server version and License :info\_doctype: section :info\_titleabbrev: Windows Versions and Licensing :imagesdir: images/windows/ == Windows Server version An Amazon EKS Optimized Windows AMI is based on Windows Server 2019 and 2022 Datacenter edition on the Long-Term Servicing... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/licensing.adoc | mainline | aws-eks-best-practices | [
0.04682457447052002,
0.030227823182940483,
0.025772811844944954,
-0.036718640476465225,
0.07514458149671555,
0.04152987152338028,
-0.0227135568857193,
-0.027900388464331627,
0.017728829756379128,
0.026232494041323662,
-0.048103418201208115,
0.000876882579177618,
0.03901595622301102,
-0.007... | 0.103394 |
[."topic"] [#windows-monitoring] = Monitoring :info\_doctype: section :info\_titleabbrev: Monitoring Windows Containers :imagesdir: images/windows/ Prometheus, a https://www.cncf.io/projects/[graduated CNCF project] is by far the most popular monitoring system with native integration into Kubernetes. Prometheus collect... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/monitoring.adoc | mainline | aws-eks-best-practices | [
-0.03764662146568298,
0.014648379758000374,
-0.024601178243756294,
0.04053632542490959,
0.040702104568481445,
-0.07954051345586777,
0.06460334360599518,
-0.033338338136672974,
0.05536174029111862,
-0.0006671407609246671,
-0.05077018216252327,
-0.112035371363163,
0.025187453255057335,
0.034... | 0.256056 |
the collectors you want to filter. [,powershell] ---- > Powershell Invoke-WebRequest https://github.com/prometheus-community/windows\_exporter/releases/download/v0.13.0/windows\_exporter-0.13.0-amd64.msi -OutFile > msiexec /i ENABLED\_COLLECTORS="cpu,cs,logical\_disk,net,os,system,container,memory" ---- By default, the... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/monitoring.adoc | mainline | aws-eks-best-practices | [
-0.045814067125320435,
0.026362309232354164,
-0.06588951498270035,
0.04688933491706848,
-0.017481772229075432,
-0.10657422244548798,
0.030199358239769936,
-0.015146678313612938,
-0.0076368278823792934,
-0.029562028124928474,
-0.021468594670295715,
-0.14032386243343353,
-0.008091181516647339,... | 0.122275 |
[."topic"] [#windows-storage] = Persistent storage options :info\_doctype: section :info\_titleabbrev: Storage Options :imagesdir: images/windows/ == What is an in-tree vs. out-of-tree volume plugin? Before the introduction of the Container Storage Interface (CSI), all volume plugins were in-tree meaning they were buil... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/storage.adoc | mainline | aws-eks-best-practices | [
-0.013232577592134476,
0.02423277497291565,
0.02666989155113697,
0.04077475145459175,
0.051100827753543854,
-0.020116280764341354,
-0.032241176813840866,
0.032426510006189346,
0.08531904220581055,
0.050585757941007614,
-0.005457089748233557,
0.013277379795908928,
0.014104199595749378,
-0.0... | 0.155097 |
access modes, without exposing users to the details of how those volumes are implemented. For these needs, there is the StorageClass resource. In the example below, the PVC has been created within the namespace windows. [,yaml] ---- apiVersion: v1 kind: PersistentVolumeClaim metadata: name: ebs-windows-pv-claim namespa... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/storage.adoc | mainline | aws-eks-best-practices | [
-0.03281848877668381,
0.01601714827120304,
-0.026538925245404243,
0.04466775432229042,
-0.04142443835735321,
0.009738296270370483,
0.03035837784409523,
0.01481438335031271,
0.07504060864448547,
0.014461410231888294,
-0.03698877990245819,
-0.07128283381462097,
0.02099422551691532,
-0.007872... | 0.05591 |
as if it had local storage. \_\_\_\_ The SMB Global Mapping is transparent to the orchestrator, and it is mounted through HostPath which can \*imply in secure concerns\*. \_\_\_\_ In the example below, the path `G:\Directory\app-state` is an SMB share on the Windows Node. [,yaml] ---- apiVersion: v1 kind: Pod metadata:... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/windows/storage.adoc | mainline | aws-eks-best-practices | [
-0.008310377597808838,
0.037302326411008835,
-0.04195978119969368,
0.02802027389407158,
0.028361620381474495,
0.02953510731458664,
-0.019144974648952484,
-0.0006004337919875979,
0.0217034462839365,
0.06602202355861664,
-0.015461515635251999,
-0.06357772648334503,
0.06558939069509506,
0.026... | 0.077473 |
[."topic"] [[karpenter,karpenter.title]] = Karpenter :info\_doctype: section :info\_title: Karpenter :info\_abstract: Karpenter :info\_titleabbrev: Karpenter :imagesdir: images/ TIP: https://aws-experience.com/emea/smb/events/series/get-hands-on-with-amazon-eks?trk=4a9b4147-2490-4c63-bc9f-f8a84b122c8c≻\_channel=el[Expl... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/autoscaling/karpenter.adoc | mainline | aws-eks-best-practices | [
-0.023015474900603294,
0.04337874799966812,
0.02744627371430397,
0.04529404267668724,
0.021516844630241394,
-0.015627527609467506,
-0.012494640424847603,
-0.06314611434936523,
0.035565074533224106,
0.08660116791725159,
-0.04974405840039253,
-0.07002194225788116,
0.008004670031368732,
-0.04... | 0.210729 |
AWS abstractions, but loses some flexibility because of that, such as scheduling for a specific availability zone. Karpenter removes a layer of AWS abstraction to bring some of the flexibility directly into Kubernetes. Karpenter is best used for clusters with workloads that encounter periods of high, spiky demand or ha... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/autoscaling/karpenter.adoc | mainline | aws-eks-best-practices | [
-0.025388432666659355,
0.018203129991889,
0.02898271195590496,
0.08045471459627151,
0.0007123456452973187,
-0.007327983155846596,
-0.017428727820515633,
-0.009328911080956459,
0.03391352668404579,
0.03427189588546753,
-0.04307503253221512,
-0.09539022296667099,
-0.01849319413304329,
-0.022... | 0.190697 |
in your VPC. If not, you will see errors similar to those that appear below. [source,console] ---- {"level":"FATAL","time":"2024-02-29T14:28:34.392Z","logger":"controller","message":"Checking EC2 API connectivity, WebIdentityErr: failed to retrieve credentials\ncaused by: RequestError: send request failed\ncaused by: P... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/autoscaling/karpenter.adoc | mainline | aws-eks-best-practices | [
-0.011367815546691418,
-0.000995422713458538,
-0.05121200531721115,
0.0099566001445055,
-0.006710108835250139,
0.01465157326310873,
-0.046621173620224,
0.0033516159746795893,
0.08951840549707413,
0.09253945201635361,
0.009141798131167889,
-0.09995816648006439,
-0.03220079839229584,
-0.0358... | 0.087818 |
defined apiVersion: apps/v1 kind: Deployment metadata: name: inflate-gpu spec: spec: tolerations: - key: "nvidia.com/gpu" operator: "Exists" effect: "NoSchedule" ---- For a general deployment for another team, the NodePool spec could include nodeAffinity. A Deployment could then use nodeSelectorTerms to match `billing-... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/autoscaling/karpenter.adoc | mainline | aws-eks-best-practices | [
0.013298246078193188,
0.009371614083647728,
0.01255336869508028,
-0.006237034685909748,
0.05711710453033447,
0.0043260022066533566,
-0.08618466556072235,
-0.05647604912519455,
0.04866956174373627,
0.01956775411963463,
-0.024427762255072594,
-0.10611417889595032,
0.011790790595114231,
-0.04... | 0.118437 |
said, the general best practice is to allow Karpenter to use a diverse set of instance types when using Spot. == Scheduling Pods The following best practices relate to deploying pods In a cluster using Karpenter for node provisioning. === Follow EKS best practices for high availability If you need to run highly availab... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/autoscaling/karpenter.adoc | mainline | aws-eks-best-practices | [
0.03754834085702896,
-0.02611275389790535,
0.05492530018091202,
0.03218927979469299,
-0.007272362243384123,
-0.0025919638574123383,
-0.02463524602353573,
-0.0337040051817894,
0.009048832580447197,
0.06477545201778412,
-0.04233430698513985,
-0.07287956774234772,
0.020424963906407356,
-0.035... | 0.110759 |
allow you to be alerted and proactively notified when the calculated estimated charges in your account(s) exceed a defined threshold. See https://aws.amazon.com/blogs/mt/setting-up-an-amazon-cloudwatch-billing-alarm-to-proactively-monitor-estimated-charges/[Setting up an Amazon CloudWatch Billing Alarm to Proactively M... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/autoscaling/karpenter.adoc | mainline | aws-eks-best-practices | [
0.009256193414330482,
0.01225222647190094,
-0.055513497442007065,
0.06534536182880402,
0.09042564034461975,
0.004107598215341568,
0.07666029781103134,
0.00616613682359457,
0.0777161493897438,
0.09794431924819946,
-0.06394454836845398,
-0.10754909366369247,
0.04707816243171692,
-0.018147923... | 0.022879 |
Karpenter, given Karpenter's dynamic nature in rapidly terminating/creating new nodes to align with demand, it is advisable to adhere to the following best practices: https://docs.aws.amazon.com/eks/latest/best-practices/scale-cluster-services.html#\_coredns\_lameduck\_duration[CoreDNS lameduck duration] https://docs.a... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/autoscaling/karpenter.adoc | mainline | aws-eks-best-practices | [
-0.039888013154268265,
-0.015098613686859608,
0.04344481602311134,
0.034280676394701004,
-0.09489759057760239,
-0.030407723039388657,
-0.07035785913467407,
-0.04832155257463455,
0.05361180379986763,
0.09837891161441803,
-0.03877590596675873,
-0.06045256927609444,
-0.034009478986263275,
-0.... | 0.171544 |
[."topic"] [[automode,automode.title]] = EKS Auto Mode :info\_doctype: section :info\_title: EKS Auto Mode :info\_abstract: EKS Auto Mode :info\_titleabbrev: EKS Auto Mode :imagesdir: images/autoscaling TIP: https://aws-experience.com/emea/smb/events/series/get-hands-on-with-amazon-eks?trk=4a9b4147-2490-4c63-bc9f-f8a84... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/autoscaling/auto-mode.adoc | mainline | aws-eks-best-practices | [
-0.03912733867764473,
0.04774966090917587,
0.021533625200390816,
0.02464725822210312,
0.023986734449863434,
-0.008999631740152836,
0.01842387020587921,
0.0042568095959723,
0.076179638504982,
0.04198094829916954,
0.0036928995978087187,
-0.05052760988473892,
0.012111910618841648,
-0.03002559... | 0.254371 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.