content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
# - 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 |
installed add-ons are up-to-date. See documentation. === How do I configure NodePools in EKS Auto Mode? A new cluster will come pre-configured with two NodePools ==== general-purpose image:gp\_nodepool.png[General Purpose NodePool] This NodePool instructs Karpenter to launch nodes with the following characteristics: 1.... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/autoscaling/auto-mode.adoc | mainline | aws-eks-best-practices | [
-0.022983014583587646,
0.014321966096758842,
0.04173464700579643,
0.07913774251937866,
0.051291532814502716,
-0.01730688102543354,
0.01987074501812458,
0.018940281122922897,
0.01831369288265705,
0.045470234006643295,
0.004798330832272768,
-0.04479312524199486,
0.021087653934955597,
0.00683... | 0.208 |
[."topic"] [[cas,cas.title]] = Kubernetes Cluster Autoscaler :info\_doctype: section :info\_title: Cluster Autoscaler :info\_abstract: Cluster Autoscaler :info\_titleabbrev: Cluster Autoscaler :imagesdir: images/autoscaling/ include::../attributes.txt[] TIP: https://aws-experience.com/emea/smb/events/series/get-hands-o... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/autoscaling/cluster-autoscaler.adoc | mainline | aws-eks-best-practices | [
-0.009719865396618843,
0.05289989709854126,
0.0176541768014431,
0.049447886645793915,
0.0069269281812012196,
-0.013625084422528744,
0.012926294468343258,
0.021750779822468758,
0.020748354494571686,
0.0185537151992321,
-0.0031519869808107615,
-0.06768528372049332,
-0.023937374353408813,
-0.... | 0.234563 |
but work is done by a single replica at a time. It is not horizontally scalable. For basic setups, the default it should work out of the box using the provided https://docs.aws.amazon.com/eks/latest/userguide/cluster-autoscaler.html[installation instructions], but there are a few things to keep in mind. Ensure that: \*... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/autoscaling/cluster-autoscaler.adoc | mainline | aws-eks-best-practices | [
-0.036797501146793365,
-0.014749204739928246,
-0.009420786052942276,
0.04134180024266243,
-0.015101307071745396,
0.007189970929175615,
-0.013974783942103386,
-0.010539015755057335,
-0.012707838788628578,
0.06939202547073364,
-0.014570700004696846,
-0.07250913977622986,
0.027059093117713928,
... | 0.120693 |
for your use case. === Vertically Autoscaling the Cluster Autoscaler The simplest way to scale the Cluster Autoscaler to larger clusters is to increase the resource requests for its deployment. Both memory and CPU should be increased for large clusters, though this varies significantly with cluster size. The autoscalin... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/autoscaling/cluster-autoscaler.adoc | mainline | aws-eks-best-practices | [
0.05769522860646248,
0.0374533049762249,
0.01772027090191841,
0.0603862963616848,
-0.03306243568658829,
-0.02419542521238327,
-0.04522040858864784,
0.03787171468138695,
-0.0014404094545170665,
0.040734730660915375,
-0.05800483003258705,
-0.021750979125499725,
-0.04655236378312111,
-0.03310... | 0.124435 |
... --nodes=1:10:k8s-worker-asg-1 --nodes=1:10:k8s-worker-asg-2 --- metadata: name: cluster-autoscaler namespace: cluster-autoscaler-2 ... --nodes=1:10:k8s-worker-asg-3 --nodes=1:10:k8s-worker-asg-4 .... Ensure that: \* Each shard is configured to point to a unique set of EC2 Auto Scaling Groups \* Each shard is deploy... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/autoscaling/cluster-autoscaler.adoc | mainline | aws-eks-best-practices | [
-0.0008965142187662423,
0.0020779140759259462,
-0.022539937868714333,
0.051691532135009766,
-0.012350313365459442,
-0.012630111537873745,
-0.0360710546374321,
0.011798865161836147,
-0.013912906870245934,
-0.00825620535761118,
-0.05714607238769531,
-0.09926050156354904,
0.07290255278348923,
... | 0.071146 |
within `--max-node-provision-time`, it will attempt to scale an EC2 Auto Scaling group matching the name \_p2-node-group\_. This value defaults to 15 minutes and can be reduced for more responsive node group selection, though if the value is too low, it can cause unnecessary scale outs. === Overprovisioning The Cluster... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/autoscaling/cluster-autoscaler.adoc | mainline | aws-eks-best-practices | [
0.02938109263777733,
0.02595514990389347,
0.07760146260261536,
0.08581585437059402,
0.07258784770965576,
-0.047078296542167664,
-0.05364404246211052,
0.01205827109515667,
0.02927413582801819,
0.05252964794635773,
-0.013446971774101257,
-0.04039962589740753,
-0.020337728783488274,
-0.041117... | 0.100905 |
`balance-similar-node-groups=true`. \* Node Groups are configured with identical settings except for different availability zones and EBS Volumes. === Co-Scheduling Machine learning distributed training jobs benefit significantly from the minimized latency of same-zone node configurations. These workloads deploy multip... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/autoscaling/cluster-autoscaler.adoc | mainline | aws-eks-best-practices | [
0.03778347000479698,
0.015633350238204002,
0.02106427773833275,
0.03365880250930786,
0.004650833085179329,
0.0014458586229011416,
-0.030080270022153854,
-0.008916463702917099,
-0.004114015493541956,
-0.0005963729345239699,
-0.09678931534290314,
-0.08018229156732559,
-0.026852808892726898,
... | 0.107298 |
|10 seconds |max-empty-bulk-delete |Maximum number of empty nodes that can be deleted at the same time. |10 |scale-down-delay-after-add |How long after scale up that scale down evaluation resumes |10 minutes |scale-down-delay-after-delete |How long after node deletion that scale down evaluation resumes, defaults to sca... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/autoscaling/cluster-autoscaler.adoc | mainline | aws-eks-best-practices | [
0.01881890743970871,
-0.0194514412432909,
-0.039578020572662354,
0.08125735819339752,
0.009539957158267498,
-0.022865863516926765,
-0.04828323796391487,
0.021469205617904663,
-0.035321611911058426,
-0.0058440822176635265,
0.02855188213288784,
-0.024839138612151146,
0.036252111196517944,
0.... | 0.10605 |
//!!NODE\_ROOT [[cluster-autoscaling,cluster-autoscaling.title]] = Cluster Autoscaling :doctype: book :sectnums: :toc: left :icons: font :experimental: :idprefix: :idseparator: - :sourcedir: . :info\_doctype: chapter :info\_title: Best Practices for Cluster Autoscaling :info\_abstract: Best Practices for Cluster Autosc... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/autoscaling/index.adoc | mainline | aws-eks-best-practices | [
0.008650826290249825,
0.03390447422862053,
0.013439260423183441,
0.045550763607025146,
0.026689890772104263,
-0.006188051775097847,
0.04213012754917145,
0.0327095128595829,
-0.04969850555062294,
0.0016926854150369763,
-0.0010324589675292373,
-0.040022291243076324,
-0.027572905644774437,
-0... | 0.145457 |
//!!NODE\_ROOT [[hybrid,hybrid.title]] = Best Practices for Hybrid Deployments :doctype: book :sectnums: :toc: left :icons: font :experimental: :idprefix: :idseparator: - :sourcedir: . :info\_doctype: chapter :info\_title: Best Practices for Hybrid Deployments :info\_abstract: Best Practices for Hybrid Deployments :inf... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/index.adoc | mainline | aws-eks-best-practices | [
-0.0276796817779541,
0.04712812229990959,
0.002120798919349909,
-0.02309330180287361,
0.046815477311611176,
-0.037751179188489914,
0.005961897317320108,
0.024974791333079338,
-0.04497189074754715,
0.02051784284412861,
0.07266251742839813,
0.012827062048017979,
0.0464445985853672,
-0.072659... | 0.140455 |
[.topic] [[hybrid-nodes-host-creds,hybrid-nodes-host-creds.title]] = Host credentials through network disconnections :info\_doctype: section :info\_title: Host credentials through network disconnections :info\_titleabbrev: Host credentials :info\_abstract: Host credentials through network disconnections EKS Hybrid Node... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/host-credentials.adoc | mainline | aws-eks-best-practices | [
-0.007538800127804279,
0.029143990948796272,
-0.015185799449682236,
0.03414005786180496,
-0.029221514239907265,
0.028504757210612297,
0.03427907079458237,
-0.028667369857430458,
0.05831781402230263,
0.047938570380210876,
-0.010589861311018467,
-0.055914752185344696,
0.13419340550899506,
-0... | 0.060543 |
network disconnections typically occurs within seconds of network restoration, because the kubelet calls `aws\_signing\_helper credential-process` to obtain credentials on demand. Although not directly related to hybrid nodes or network disconnections, you can configure notifications and alerts for certificate expiry w... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/host-credentials.adoc | mainline | aws-eks-best-practices | [
0.04533081129193306,
-0.010109289549291134,
0.06587868928909302,
0.04609745368361473,
-0.002153754932805896,
-0.029075147584080696,
0.02550239861011505,
-0.07753065228462219,
0.07946747541427612,
-0.01813541166484356,
-0.017161410301923752,
-0.047975968569517136,
0.08534006774425507,
0.015... | 0.020727 |
[.topic] [[hybrid-nodes-network-disconnection-best-practices,hybrid-nodes-network-disconnection-best-practices.title]] = Best practices for stability through network disconnections :info\_doctype: section :info\_title: Best practices for stability through network disconnections :info\_titleabbrev: Best practices :info\... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/best-practices.adoc | mainline | aws-eks-best-practices | [
0.004444214981049299,
0.007307440508157015,
0.020638972520828247,
0.016331950202584267,
-0.03356604278087616,
0.07174236327409744,
0.018878132104873657,
0.00138564791996032,
0.007283278275281191,
-0.005357649642974138,
-0.023918280377984047,
0.0401967316865921,
0.017264969646930695,
-0.096... | 0.022204 |
metrics to observe the network traffic into and out of your TGW or VGW. You can create alarms for these metrics to detect scenarios where network traffic dips below normal levels, indicating a potential network issue between hybrid nodes and the EKS control plane. The TGW and VGW metrics are described in the following ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/best-practices.adoc | mainline | aws-eks-best-practices | [
0.011559355072677135,
0.046836160123348236,
-0.018922220915555954,
0.04842172935605049,
0.004266371950507164,
0.047650355845689774,
0.04640703275799751,
0.0074373288080096245,
0.061135321855545044,
0.022827403619885445,
-0.029760651290416718,
-0.07942232489585876,
0.03409518301486969,
-0.0... | 0.076865 |
functionality is integrated with the Cilium agent, and the Cilium agent will continuously restart when disconnected from the Kubernetes control plane. The reason for the restart is due to Cilium's health check failing because its health is coupled with access to the Kubernetes control plane (see https://github.com/cili... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/best-practices.adoc | mainline | aws-eks-best-practices | [
0.029986219480633736,
-0.008020286448299885,
0.015283453278243542,
0.01952146366238594,
-0.02351207658648491,
-0.06704473495483398,
-0.00242803362198174,
0.02909160405397415,
0.09788911044597626,
0.009685391560196877,
-0.04532624036073685,
-0.01876399666070938,
0.005337059032171965,
-0.023... | 0.185093 |
with `tolerationSeconds` for the unreachable taint is shown below. In the example, `tolerationSeconds` is set to `1800` (30 minutes), which means pods running on unreachable nodes will only be evicted if the network disconnection lasts longer than 30 minutes. [source,yaml,subs="verbatim,attributes,quotes"] ---- apiVers... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/best-practices.adoc | mainline | aws-eks-best-practices | [
0.04579373449087143,
-0.03094177134335041,
0.063019759953022,
0.04033671319484711,
0.049341753125190735,
-0.021472766995429993,
-0.01612934283912182,
-0.06486116349697113,
0.07650291174650192,
0.03762321174144745,
-0.004834669176489115,
-0.034976791590452194,
-0.005182020831853151,
-0.0336... | 0.166977 |
//!!NODE\_ROOT [.topic] [[hybrid-nodes-kubernetes-pod-failover,hybrid-nodes-kubernetes-pod-failover.title]] = Kubernetes pod failover through network disconnections :doctype: section :info\_doctype: section :info\_title: Kubernetes pod failover through network disconnections :info\_titleabbrev: Kubernetes pod failover ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/kubernetes-pod-failover.adoc | mainline | aws-eks-best-practices | [
0.006787692196667194,
0.00902726873755455,
0.10683892667293549,
0.012697434052824974,
-0.002005874877795577,
0.019389862194657326,
0.002132357796654105,
-0.012698703445494175,
0.0417388454079628,
0.055043261498212814,
-0.017037276178598404,
0.006447602529078722,
0.02364468388259411,
-0.069... | 0.159271 |
number of retries allowed for the kubelet to post node status. |40 |40 |No |node-lifecycle-controller |large-cluster-size-threshold |The number of nodes at which the node-lifecycle-controller treats the cluster as large for eviction logic. `--secondary-node-eviction-rate` is overridden to 0 for clusters of this size or... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/kubernetes-pod-failover.adoc | mainline | aws-eks-best-practices | [
0.05459485203027725,
0.015083283185958862,
-0.035445645451545715,
0.031013818457722664,
-0.03264552727341652,
0.009823299944400787,
-0.05592716485261917,
-0.015734810382127762,
0.04893623664975166,
0.03282660245895386,
0.04454110935330391,
-0.0778203159570694,
0.03408874571323395,
-0.09591... | 0.116739 |
on any nodes during the disconnection and subsequent reconnection. === Scenario 3: Majority zone disruption \*Expected result\*: Pods on unreachable nodes are not evicted and continue running on those nodes. A majority zone disruption means that most nodes in a given zone are disconnected from the Kubernetes control pl... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/kubernetes-pod-failover.adoc | mainline | aws-eks-best-practices | [
0.10776999592781067,
-0.04735177382826805,
0.0732966884970665,
0.07127656787633896,
0.05956392362713814,
-0.04692896828055382,
0.00020342211064416915,
0.005034578964114189,
0.06812114268541336,
0.07362885773181915,
0.002294044243171811,
-0.01662716642022133,
0.011826577596366405,
-0.083180... | 0.12879 |
to a network disconnection, it cannot retrieve the information needed to start the pods. In this scenario, local troubleshooting tools such as the `crictl` CLI cannot be used to start pods manually as a “break-glass” measure. Kubernetes typically removes failed pods and creates new ones rather than restarting existing ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/kubernetes-pod-failover.adoc | mainline | aws-eks-best-practices | [
0.06471851468086243,
-0.007262947969138622,
0.0899038165807724,
0.01775660179555416,
-0.023664221167564392,
-0.015374617651104927,
-0.02943713217973709,
-0.02339201234281063,
0.009074791334569454,
0.030111756175756454,
-0.046995047479867935,
-0.043729834258556366,
-0.01843167655169964,
0.0... | 0.107869 |
[.topic] [[hybrid-nodes-app-network-traffic,hybrid-nodes-app-network-traffic.title]] = Application network traffic through network disconnections :info\_doctype: section :info\_title: Application network traffic through network disconnections :info\_titleabbrev: Application network traffic :info\_abstract: Application ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/app-network-traffic.adoc | mainline | aws-eks-best-practices | [
0.011585338972508907,
-0.023967336863279343,
-0.03388103097677231,
-0.0400611087679863,
-0.08189770579338074,
-0.03554625064134598,
0.02740364335477352,
0.032877326011657715,
0.018117638304829597,
-0.02443631738424301,
-0.011943202465772629,
-0.0599927119910717,
0.020956840366125107,
-0.07... | 0.269992 |
modes for load balancing: https://metallb.universe.tf/concepts/layer2/[L2 mode] and https://metallb.universe.tf/concepts/bgp/[BGP mode]. Reference the MetalLB documentation for details of how these load balancing modes work and their limitations. The validation for this guide used MetalLB in L2 mode, where one machine ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/app-network-traffic.adoc | mainline | aws-eks-best-practices | [
-0.06204477325081825,
-0.03774717450141907,
0.04261825606226921,
-0.0005942750140093267,
-0.04176708683371544,
0.003817240707576275,
0.034956417977809906,
-0.042006850242614746,
0.08565950393676758,
-0.012436464428901672,
-0.07644511759281158,
-0.03640289977192879,
0.002628169022500515,
-0... | 0.20303 |
:443: i/o timeout" logger="UnhandledError" "Unhandled Error" err="k8s.io/client-go/informers/factory.go:160: Failed to watch \*v1.EndpointSlice: failed to list \*v1.EndpointSlice: Get \"https:///apis/discovery.k8s.io/v1/endpointslices?labelSelector=%21service.kubernetes.io%2Fheadless%2C%21service.kubernetes.io%2Fservic... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/app-network-traffic.adoc | mainline | aws-eks-best-practices | [
-0.018329229205846786,
0.043608810752630234,
0.03201038017868996,
0.001134516322053969,
-0.024719424545764923,
-0.0021457297261804342,
-0.039565637707710266,
-0.03785879909992218,
0.12703780829906464,
0.07734553515911102,
-0.00894840620458126,
-0.0516393817961216,
-0.01476630661636591,
0.0... | 0.198064 |
//!!NODE\_ROOT [.topic] [[hybrid-nodes-network-disconnections,hybrid-nodes-network-disconnections.title]] = EKS Hybrid Nodes and network disconnections :doctype: section :sectnums: :toc: left :icons: font :experimental: :idprefix: :idseparator: - :sourcedir: . :info\_doctype: section :info\_title: EKS Hybrid Nodes and ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/hybrid/network-disconnections/index.adoc | mainline | aws-eks-best-practices | [
-0.01057872362434864,
0.03469059243798256,
0.031139280647039413,
0.05415508151054382,
0.09403985738754272,
-0.008426626212894917,
0.01871778815984726,
-0.06040945276618004,
0.06926481425762177,
0.022152915596961975,
0.04146179184317589,
0.016676809638738632,
0.040660567581653595,
-0.102653... | 0.153481 |
# Bee Health Detection Example This repository contains example code detect if a bee is healthy. Specifically, given a picture and structured attributes about a bee, it predicts if the bee is healthy. The code leverages pre-trained TF Hub image modules and uses Google Cloud Machine Learning Engine to train a TensorFlow... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/cloudml-bee-health-detection/README.md | main | gcp-professional-services | [
-0.03484155610203743,
-0.05560236796736717,
0.025231480598449707,
0.03030283935368061,
0.08998743444681168,
-0.01291478332132101,
0.01906486600637436,
-0.051404573023319244,
-0.04993145912885666,
-0.03236757218837738,
0.019762450829148293,
-0.10601471364498138,
0.013536444865167141,
-0.026... | 0.017029 |
After you’ve built a successful prototype of a machine learning model, there’s still plenty of things to do. To some extent, your journey as an ML engineer only begins here. You’d need to take care about plenty of things such as operationalization of your model: monitoring, CI/CD, reliability and reproducibility, and m... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/tensorflow-unit-testing/README.md | main | gcp-professional-services | [
0.0033267377875745296,
-0.11800829321146011,
0.06771623343229294,
0.03098594769835472,
0.022072898223996162,
-0.053500786423683167,
-0.09514951705932617,
-0.01358791347593069,
-0.12527044117450714,
-0.04051540419459343,
-0.025511905550956726,
-0.016820047050714493,
-0.005640571471303701,
-... | 0.009961 |
we don’t check whether the training itself makes sense - i.e., whether a loss decreases to any meaningful value. But more about it later. Let’s have a look at a simple example of how to test a model from this [tutorial](https://www.tensorflow.org/tutorials/keras/regression). ```python class ExampleModelTest(tf.test.Tes... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/tensorflow-unit-testing/README.md | main | gcp-professional-services | [
-0.025798147544264793,
0.007542775943875313,
0.007429901044815779,
0.06686504185199738,
0.04250425472855568,
-0.006840959656983614,
-0.018073905259370804,
0.028727015480399132,
-0.03622668236494064,
-0.019835133105516434,
-0.03281359747052193,
-0.0366453155875206,
-0.016515541821718216,
0.... | 0.059632 |
# JavaScript to QueryParam This example shows a basic proxy that converts a simple, single-level JSON document posted into the endpoint to a series of query parameters sent to the target. For example, if the following were posted: ```json { "foo": "bar", "baz": "quux" } ``` The resulting back end query would be: `GET h... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/apigee-json-to-queryparam/README.md | main | gcp-professional-services | [
-0.10143610835075378,
0.020879626274108887,
0.003688775934278965,
0.027607690542936325,
-0.10778070241212845,
-0.00837064441293478,
-0.0394757017493248,
-0.0173909030854702,
-0.004024705849587917,
-0.006284673698246479,
-0.030272018164396286,
-0.0054752035066485405,
0.08143302798271179,
-0... | -0.055778 |
# Dataflow Flex Template: De-identify CSVs in GCS (DLP) → BigQuery A runnable Flex Template that takes CSVs in Cloud Storage, calls DLP to de-identify sensitive fields, and writes sanitized rows to BigQuery. > \*\*Prerequisites\*\* > - Google Cloud project with billing enabled > - You can run commands either in \*\*Clo... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/dataflow-dlp-flex-deid/README.md | main | gcp-professional-services | [
-0.06650363653898239,
0.02735704928636551,
-0.02698392979800701,
-0.020732257515192032,
0.021079277619719505,
-0.016017213463783264,
0.0029966942965984344,
-0.007819403894245625,
0.02358176000416279,
0.0597512312233448,
-0.025674160569906235,
-0.06900390237569809,
0.04444307088851929,
-0.1... | -0.080218 |
mismatch\*\* → ensure headers match CSV columns and your DLP template. - \*\*Permission denied\*\* → verify runner service account roles listed in “One-time resources”. - \*\*Template not found\*\* → check `deidentify\_template\_name` and its location (`global` or regional). --- | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/dataflow-dlp-flex-deid/README.md | main | gcp-professional-services | [
-0.014597051776945591,
0.04307251423597336,
-0.0037517123855650425,
-0.042887814342975616,
0.02640688046813011,
0.041688427329063416,
-0.07253202050924301,
-0.008554479107260704,
-0.006737563759088516,
0.012624372728168964,
-0.035692956298589706,
-0.09408541768789291,
-0.031068187206983566,
... | -0.102528 |
# gRPC Example This example creates a gRCP server that connect to redis to find the name of a user for a given user id. ## Application Project Structure ``` . └── grpc\_example\_redis └── src └── main ├── java └── com.example.grpc ├── client └── ConnectClient # Example Client ├── server └── ConnectServer # Initializes ... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/grpc_redis_example/README.md | main | gcp-professional-services | [
-0.07478410005569458,
-0.05232486501336098,
-0.09318063408136368,
-0.08965666592121124,
-0.06137509644031525,
-0.09499496966600418,
0.08024115860462189,
0.05966609716415405,
0.0075571308843791485,
-0.0246383398771286,
0.013345243409276009,
0.009067082777619362,
0.018329022452235222,
0.0045... | 0.111554 |
# ABAP Utility for Bulk Creation of CDS Views ## Summary This ABAP utility program streamlines the creation of CDS views designed for capturing delta changes in SAP tables. These delta-enabled views are crucial for replicating data to BigQuery, enabling powerful data analytics on SAP data. By automating this process, t... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/sap-bigquery-cds-generator/README.md | main | gcp-professional-services | [
-0.056206461042165756,
-0.052070606499910355,
-0.04384583607316017,
-0.010128911584615707,
-0.020519481971859932,
-0.05982765555381775,
-0.0035539816599339247,
-0.013841657899320126,
0.006330575793981552,
0.07633263617753983,
0.02694905363023281,
-0.02714437246322632,
0.02912156842648983,
... | 0.078408 |
the output, the same logs are saved in the table ZCDS\_CR\_LOG | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/sap-bigquery-cds-generator/README.md | main | gcp-professional-services | [
0.02461792156100273,
0.04245007038116455,
-0.10015368461608887,
-0.01423534657806158,
0.08483845740556717,
-0.08605615049600601,
0.011889401823282242,
0.026098361238837242,
0.05071118846535683,
0.04685456305742264,
0.1026315838098526,
0.0253585297614336,
0.0815371572971344,
-0.024724444374... | -0.009623 |
# Distributed Load-Testing with Jmeter ## Build and Push jmeter-master docker File ```Dockerfile FROM justb4/jmeter:latest EXPOSE 60000 ``` ```bash docker build --tag="/jmeter-master:latest" -f Dockerfile-master . docker push /jmeter-master:latest ``` ## Build and Push jmeter-slave docker File ```Dockerfile FROM justb4... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/gke-distributed-load-test-jmeter/README.md | main | gcp-professional-services | [
-0.013722214847803116,
0.0311571191996336,
-0.013289532624185085,
0.0319606252014637,
-0.02094205841422081,
-0.07001452893018723,
-0.1047712042927742,
-0.017515065148472786,
0.01126736868172884,
0.008143272250890732,
-0.0519215352833271,
-0.05701248720288277,
0.035273149609565735,
0.027826... | -0.041648 |
# Overview The purpose of this walkthrough is to create a [Dataflow](https://cloud.google.com/dataflow) streaming pipeline to read XML encoded messages from [PubSub](https://cloud.google.com/pubsub):  ## Pipeline This pipeline is developed with the [Beam Pyth... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/dataflow-xml-pubsub-to-gcs/README.md | main | gcp-professional-services | [
-0.06055181846022606,
-0.021740838885307312,
-0.01438233908265829,
-0.001998343737795949,
-0.04548516124486923,
-0.07968027144670486,
-0.029771415516734123,
-0.019881734624505043,
-0.00945118349045515,
-0.07570473849773407,
-0.059161439538002014,
-0.03739572688937187,
0.014840008690953255,
... | 0.058573 |
# Dataflow PubSub XML to Google cloud storage sample pipeline ## License Copyright 2023 Google LLC Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0 Unless r... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/dataflow-xml-pubsub-to-gcs/python/README.md | main | gcp-professional-services | [
-0.04458138719201088,
-0.06659697741270065,
0.024635253474116325,
-0.07590179145336151,
-0.032141949981451035,
-0.019094226881861687,
-0.047666750848293304,
-0.04951499402523041,
0.03501571714878082,
0.03904290124773979,
-0.026520734652876854,
-0.0403512641787529,
0.07118324935436249,
-0.0... | -0.068578 |
Monitor the Dataflow Job Navigate to https://console.cloud.google.com/dataflow/jobs to locate the job you just created. Clicking on the job will let you navigate to the job monitoring screen. ## Debug the Pipeline \*\*Optionally\*\* This sample contains the necessary bindings to debug step by step and/or breakpoint thi... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/dataflow-xml-pubsub-to-gcs/python/README.md | main | gcp-professional-services | [
-0.03165878728032112,
-0.04805789887905121,
0.026361100375652313,
-0.0032388740219175816,
0.030605120584368706,
-0.07782081514596939,
-0.026963161304593086,
-0.0788726732134819,
0.04624437540769577,
0.04989350587129593,
-0.041777487844228745,
-0.06108885630965233,
-0.008246634155511856,
-0... | -0.076646 |
# CloudML Deep Collaborative Filtering A simple machine learning system capable of recommending songs given a user as a query using collaborative filtering and TensorFlow. Unlike classic matrix factorization approaches, using a neural network allows user and item features to be included during training. This example co... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/cloudml-collaborative-filtering/README.md | main | gcp-professional-services | [
-0.08275594562292099,
-0.12906160950660706,
0.00047016714233905077,
0.0030581627506762743,
0.032552797347307205,
0.09975925832986832,
0.035085808485746384,
-0.04967685043811798,
-0.08282039314508438,
-0.042180370539426804,
-0.018508199602365494,
0.039381466805934906,
0.03646448627114296,
-... | 0.009781 |
absolute value to get a value between 0 and 1. 7. Calculate error using log loss and train the model. 8. Evaluate the model performance by sampling 1000 random items and calculating the average recall@k when each positive sample's item is ranked against these random items for the sample's user. 9. Export a `SavedModel`... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/cloudml-collaborative-filtering/README.md | main | gcp-professional-services | [
-0.00951081607490778,
-0.00901597086340189,
-0.04107331112027168,
0.07038364559412003,
0.010718789882957935,
0.004138540476560593,
-0.015566691756248474,
0.05224328115582466,
-0.044651538133621216,
0.00461303535848856,
0.009322145022451878,
-0.09387358278036118,
0.07753350585699081,
-0.065... | -0.018908 |
# React single page app on Cloud Run + Cloud Storage ## Introduction This blueprint contains a simple React single page application created with [`create-react-app`](https://create-react-app.dev/) and necessary Terraform resources to deploy it in on Google Cloud. The blueprint also contains a very simple Python backend... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/react-spa-app/README.md | main | gcp-professional-services | [
-0.13579817116260529,
0.03632326424121857,
0.06292358785867691,
-0.04568798467516899,
-0.030968917533755302,
0.0074129183776676655,
-0.017835834994912148,
-0.019156910479068756,
-0.009560146369040012,
0.08381404727697372,
-0.04206039384007454,
-0.022291485220193863,
0.06345825642347336,
-0... | 0.012508 |
load balancers active in this configuration. ## Variables | name | description | type | required | default | | ---------------------------------- | ------------------------------------------------------------------------------------- | :-----------------------------------------------------------------------------------... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/react-spa-app/README.md | main | gcp-professional-services | [
-0.04578951746225357,
0.01746787503361702,
-0.08718867599964142,
0.01949450559914112,
-0.11628112941980362,
0.0011441067326813936,
-0.007049244828522205,
0.022598126903176308,
-0.006398044526576996,
-0.043465420603752136,
0.024671543389558792,
-0.04779881238937378,
0.033681754022836685,
-0... | 0.038155 |
# NetApp Cloud Volumes Service (CVS) Terraform Example This example shows how to deploy NetApp CVS volumes using terraform (i.e. without using any external modules). This code also enables replication between volumes if \*replication\* variable is set as \*true\*. ## Prerequisites 1. You must have a recent version of T... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/tf-netapp-cvs/README.md | main | gcp-professional-services | [
-0.06812149286270142,
-0.04394375905394554,
-0.004438037518411875,
-0.054850827902555466,
-0.062283385545015335,
-0.014280224218964577,
-0.0664612352848053,
0.006137122865766287,
0.050284210592508316,
0.1046651154756546,
-0.047513581812381744,
-0.10609181225299835,
0.07601120322942734,
0.0... | -0.022234 |
# Automated BigQuery Exports via Email This serverless solution enables users to regularly send BigQuery export results via email. The end users will get a scheduled email with a link to either a Google Cloud Storage [signed URL](https://cloud.google.com/storage/docs/access-control/signed-urls) or an [unsigned URL](htt... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/bq-email-exports/README.md | main | gcp-professional-services | [
-0.016516199335455894,
0.08951111137866974,
-0.020754842087626457,
0.01964443363249302,
0.01934652030467987,
-0.0275284331291914,
-0.019284408539533615,
0.007965214550495148,
0.006934169679880142,
0.06824091076850891,
-0.05091429129242897,
0.02257516048848629,
0.030647534877061844,
-0.0772... | -0.092893 |
## Providers | Name | Version | |------|---------| | archive | n/a | | google | ~> 3.48.0 | ## Inputs | Name | Description | Type | Default | Required | |------|-------------|------|---------|:-----:| | bq\\_dataset\\_expiration | The default lifetime of all tables in the dataset in milliseconds. The minimum value is 3... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/bq-email-exports/terraform/README.md | main | gcp-professional-services | [
-0.031158186495304108,
0.011762951500713825,
-0.05734715983271599,
0.10500472038984299,
-0.05858367681503296,
-0.0012703542597591877,
-0.02805241011083126,
0.03394193574786186,
-0.03631335124373436,
0.04956489056348801,
-0.0008639963925816119,
-0.05787884071469307,
0.06601038575172424,
-0.... | 0.009534 |
| | sender\\_email\\_address | Email address of sender. | `any` | n/a | yes | | sendgrid\\_api\\_key | API key for authenticating the sending of emails through SendGrid API | `any` | n/a | yes | | service\\_acct\\_name | The service account used by the three BQ email export Cloud Functions | `any` | n/a | yes | | servi... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/bq-email-exports/terraform/README.md | main | gcp-professional-services | [
-0.05621270090341568,
-0.013942630030214787,
-0.05937773734331131,
0.03324035182595253,
0.015974078327417374,
0.023198727518320084,
0.03726883977651596,
0.006408918648958206,
0.04500577971339226,
0.07964303344488144,
-0.014076320454478264,
-0.09183821827173233,
0.0711572915315628,
-0.07039... | -0.052358 |
\*\*Table of Contents\*\* - [Data Lake](#data-lake) - [Troubleshooting](#troubleshooting) - [Issues with destroying KMS Resources](#issues-with-destroying-kms-resources) - [Requirements](#requirements) - [Providers](#providers) - [Inputs](#inputs) - [Outputs](#outputs) # Data Lake This module is intended to spin up a b... | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/kerberized_data_lake/README.md | main | gcp-professional-services | [
-0.03752168267965317,
0.014168947003781796,
-0.04535793140530586,
-0.07770124077796936,
-0.008833592757582664,
-0.05483032017946243,
0.05263699218630791,
-0.027527237311005592,
-0.044186316430568695,
0.06785531342029572,
0.009432577528059483,
-0.027542421594262123,
0.06935962289571762,
-0.... | 0.116046 |
qualified domain name for cluster on which to run presto / spark jobs | | gcs\\_encrypted\\_keytab\\_path | GCS path to keep keytabs | | kms\\_key | kms key for decrypting keytabs | | https://github.com/GoogleCloudPlatform/professional-services/blob/main//examples/kerberized_data_lake/README.md | main | gcp-professional-services | [
-0.02319588139653206,
-0.06304475665092468,
-0.07806722819805145,
-0.056296493858098984,
-0.04207604005932808,
-0.05235232040286064,
0.03184090182185173,
-0.03718947991728783,
-0.01711955852806568,
-0.008037803694605827,
-0.012573466636240482,
-0.011517242528498173,
0.028106914833188057,
-... | 0.057661 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.