content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 50
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
its execution before the TERM signal can be sent. If a `PreStop` hook hangs during execution, the Pod's phase will be `Terminating` and remain there until the Pod is killed after its `terminationGracePeriodSeconds` expires. This grace period applies to the total time it takes for both the `PreStop` hook to execute and ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/containers/container-lifecycle-hooks.md | main | kubernetes | [
0.045880164951086044,
0.023790378123521805,
0.044890135526657104,
-0.02551720291376114,
0.00822508241981268,
-0.01174011081457138,
-0.016073832288384438,
-0.001971171936020255,
0.06011014059185982,
0.06415240466594696,
0.02107270620763302,
0.06075109541416168,
-0.0638078898191452,
-0.05754... | 0.148405 |
This page will discuss containers and container images, as well as their use in operations and solution development. The word \_container\_ is an overloaded term. Whenever you use the word, check whether your audience uses the same definition. Each container that you run is repeatable; the standardization from having d... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/containers/_index.md | main | kubernetes | [
0.017827754840254784,
0.01544957421720028,
0.0867137461900711,
-0.012614324688911438,
0.05918111279606819,
-0.04132761061191559,
0.01704447530210018,
-0.037671998143196106,
0.08201423287391663,
0.01690053381025791,
0.013652436435222626,
0.009253363125026226,
0.005324967205524445,
-0.024907... | 0.201077 |
The CRI is a plugin interface which enables the kubelet to use a wide variety of container runtimes, without having a need to recompile the cluster components. You need a working {{}} on each Node in your cluster, so that the {{< glossary\_tooltip text="kubelet" term\_id="kubelet" >}} can launch {{< glossary\_tooltip t... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/containers/cri.md | main | kubernetes | [
-0.027665462344884872,
0.01101607084274292,
0.05013224855065346,
-0.01753099262714386,
-0.06655406951904297,
0.011335322633385658,
0.032061267644166946,
-0.023227393627166748,
0.029571086168289185,
-0.038815345615148544,
-0.01678909920156002,
-0.1541776955127716,
0.009258171543478966,
-0.0... | 0.08718 |
Windows applications constitute a large portion of the services and applications that run in many organizations. [Windows containers](https://aka.ms/windowscontainers) provide a way to encapsulate processes and package dependencies, making it easier to use DevOps practices and follow cloud native patterns for Windows a... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/windows/intro.md | main | kubernetes | [
0.023499248549342155,
-0.03393232822418213,
0.03119782544672489,
-0.00953044556081295,
0.0017339411424472928,
-0.023815540596842766,
-0.013441639021039009,
-0.01837180368602276,
0.10871205478906631,
0.009726197458803654,
-0.06803338974714279,
-0.0401734858751297,
-0.03649115934967995,
-0.0... | 0.156244 |
a list. For example, `spec.containers[\*].securityContext` refers to the SecurityContext object for all containers. If any of these fields is specified, the Pod will not be admitted by the API server. \* [Workload resources](/docs/concepts/workloads/controllers/) including: \* ReplicaSet \* Deployment \* StatefulSet \*... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/windows/intro.md | main | kubernetes | [
-0.035015661269426346,
0.019951917231082916,
-0.027297809720039368,
0.0013992846943438053,
-0.014237016439437866,
-0.00573320547118783,
0.0634092316031456,
-0.04474978893995285,
0.034919798374176025,
0.03180187568068504,
-0.012471513822674751,
-0.058339923620224,
0.02431659772992134,
-0.01... | 0.200106 |
are not available. They require [asserting a user privilege](https://docs.microsoft.com/en-us/windows/desktop/Memory/large-page-support) that's not configurable for containers. \* `requests.cpu` and `requests.memory` - requests are subtracted from node available resources, so they can be used to avoid overprovisioning ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/windows/intro.md | main | kubernetes | [
0.014780476689338684,
0.07503341138362885,
-0.0867246687412262,
0.048152778297662735,
0.02694949321448803,
-0.02721097320318222,
0.051542799919843674,
0.02012048102915287,
-0.03625931218266487,
0.0738999992609024,
-0.03996802493929863,
-0.014842201955616474,
-0.0021409771870821714,
-0.0110... | 0.137341 |
or “pause” container is first created to host the container. In Linux, the cgroups and namespaces that make up a pod need a process to maintain their continued existence; the pause process provides this. Containers that belong to the same pod, including infrastructure and worker containers, share a common network endpo... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/windows/intro.md | main | kubernetes | [
-0.00844047125428915,
-0.006244560703635216,
-0.00840417668223381,
-0.023166626691818237,
0.01183257158845663,
0.06337416917085648,
-0.019704079255461693,
-0.07177196443080902,
0.08587605506181717,
0.04734797403216362,
-0.011451615951955318,
0.026427922770380974,
-0.10800022631883621,
-0.0... | 0.224902 |
[300MB to over 10GB](https://techcommunity.microsoft.com/t5/containers/nano-server-x-server-core-x-server-which-base-image-is-the-right/ba-p/2835785) for a single image. Additionally, take note that the `C:` drive in Windows containers represents a virtual free size of 20GB by default, which is not the actual consumed ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/windows/intro.md | main | kubernetes | [
0.07626327127218246,
0.01836216263473034,
0.04180001839995384,
-0.006450247950851917,
0.05365871638059616,
-0.0006808207253925502,
0.00527958944439888,
0.060495149344205856,
0.01557739358395338,
0.06870020180940628,
-0.047196365892887115,
-0.04767605662345886,
-0.015385743230581284,
0.0286... | 0.109843 |
This page provides a walkthrough for some steps you can follow to run Windows containers using Kubernetes. The page also highlights some Windows specific functionality within Kubernetes. It is important to note that creating and deploying services and workloads on Kubernetes behaves in much the same way for Linux and W... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/windows/user-guide.md | main | kubernetes | [
0.05379319190979004,
0.030761167407035828,
0.012990503571927547,
0.006811461411416531,
-0.055377986282110214,
0.07895390689373016,
0.0003090082318522036,
-0.021623704582452774,
-0.00974280759692192,
0.018944351002573967,
-0.11281348764896393,
-0.07797171920537949,
-0.017947962507605553,
0.... | 0.105559 |
to access the IP of services scheduled on them due to current platform limitations of the Windows networking stack. Only Windows pods are able to access service IPs. {{< /note >}} ## Observability ### Capturing logs from workloads Logs are an important element of observability; they enable users to gain insights into t... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/windows/user-guide.md | main | kubernetes | [
0.064938984811306,
0.04888772591948509,
0.023726772516965866,
0.014222655445337296,
0.033028967678546906,
-0.012408379465341568,
0.02215557172894478,
-0.02546125464141369,
0.06380841881036758,
0.06453891098499298,
-0.0900237187743187,
-0.0334327407181263,
-0.07482929527759552,
0.0266223549... | 0.143421 |
the following default labels: \* kubernetes.io/os = [windows|linux] \* kubernetes.io/arch = [amd64|arm64|...] If a Pod specification does not specify a `nodeSelector` such as `"kubernetes.io/os": windows`, it is possible the Pod can be scheduled on any host, Windows or Linux. This can be problematic since a Windows con... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/windows/user-guide.md | main | kubernetes | [
0.03800640255212784,
0.04511703923344612,
0.02050025388598442,
-0.021816415712237358,
0.014871137216687202,
0.03693888336420059,
-0.019022829830646515,
-0.013717458583414555,
0.05658867582678795,
0.005691351369023323,
-0.025953995063900948,
-0.0615161769092083,
-0.04708721488714218,
-0.026... | 0.128436 |
Kubernetes supports worker {{< glossary\_tooltip text="nodes" term\_id="node" >}} running either Linux or Microsoft Windows. {{% thirdparty-content single="true" %}} The CNCF and its parent the Linux Foundation take a vendor-neutral approach towards compatibility. It is possible to join your [Windows server](https://ww... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/windows/_index.md | main | kubernetes | [
-0.020541001111268997,
-0.04843507334589958,
-0.023945484310388565,
0.00924534909427166,
-0.028257425874471664,
0.053424131125211716,
-0.013431121595203876,
-0.038730211555957794,
0.03222177177667618,
0.03963088616728783,
-0.0985642820596695,
-0.07318853586912155,
-0.045227307826280594,
0.... | 0.145183 |
The core of Kubernetes' {{< glossary\_tooltip text="control plane" term\_id="control-plane" >}} is the {{< glossary\_tooltip text="API server" term\_id="kube-apiserver" >}}. The API server exposes an HTTP API that lets end users, different parts of your cluster, and external components communicate with one another. The... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/kubernetes-api.md | main | kubernetes | [
-0.03530379757285118,
-0.016536446288228035,
0.011706778779625893,
0.0011460734531283379,
-0.0815172791481018,
0.0006312491605058312,
0.004620034713298082,
-0.028458939865231514,
0.1198887750506401,
0.03963232785463333,
-0.04899889975786209,
-0.07068841904401779,
-0.008006551302969456,
-0.... | 0.19977 |
root endpoints publishing discovery information for downstream documents. A list of all group versions supported by a cluster is published at the `/api` and `/apis` endpoints. Example: ``` { "kind": "APIGroupList", "apiVersion": "v1", "groups": [ { "name": "apiregistration.k8s.io", "versions": [ { "groupVersion": "apir... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/kubernetes-api.md | main | kubernetes | [
0.0027850039768964052,
0.05194927006959915,
0.007834573276340961,
0.04322998598217964,
0.02508353255689144,
-0.0009138541063293815,
-0.09177453815937042,
-0.015590822324156761,
0.03462175652384758,
0.04305224493145943,
0.013206027448177338,
-0.05079696699976921,
-0.012508495710790157,
0.03... | 0.048056 |
v2.0 and v3.0; there are no plans to support 3.1 in the near future. ### Protobuf serialization Kubernetes implements an alternative Protobuf based serialization format that is primarily intended for intra-cluster communication. For more information about this format, see the [Kubernetes Protobuf serialization](https:/... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/kubernetes-api.md | main | kubernetes | [
-0.043604567646980286,
0.0014585445169359446,
0.02008734457194805,
-0.08469609916210175,
-0.018443936482071877,
0.020805751904845238,
-0.0860065370798111,
-0.04522594437003136,
0.06127007305622101,
0.013378000818192959,
-0.039289772510528564,
-0.022650910541415215,
-0.04002899304032326,
-0... | 0.134315 |
the API did change in incompatible ways that require deleting all existing alpha objects prior to upgrade. {{< /note >}} Refer to [API versions reference](/docs/reference/using-api/#api-versioning) for more details on the API version level definitions. ## API Extension The Kubernetes API can be extended in one of two w... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/kubernetes-api.md | main | kubernetes | [
0.008703071624040604,
-0.00862945057451725,
0.07361478358507156,
-0.01195652224123478,
0.0034346517641097307,
0.011463457718491554,
-0.03770989179611206,
-0.08532658964395523,
0.08516675978899002,
0.05285834148526192,
-0.03583671525120735,
0.0007801784086041152,
-0.050496671348810196,
0.01... | 0.07282 |
{{< glossary\_definition prepend="Kubernetes provides a" term\_id="kubectl" length="short" >}} The `kubectl` tool communicates with your cluster through the [Kubernetes API](/docs/concepts/overview/kubernetes-api/). For configuration, `kubectl` looks for a file named `config` in the `$HOME/.kube` directory. You can spe... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/kubectl.md | main | kubernetes | [
-0.015425113961100578,
-0.020609965547919273,
-0.01300596259534359,
0.016285041347146034,
-0.02052929811179638,
0.015428745187819004,
0.01317229401320219,
-0.06379692256450653,
0.06548380106687546,
0.04681333526968956,
-0.01152484305202961,
-0.0774272158741951,
-0.026500269770622253,
-0.05... | 0.139039 |
skew policy](/releases/version-skew-policy/) for details. ## {{% heading "whatsnext" %}} \* Read the [kubectl reference](/docs/reference/kubectl/) for syntax and command details. \* [Install kubectl](/docs/tasks/tools/#kubectl) on your machine. \* Learn about [The Kubernetes API](/docs/concepts/overview/kubernetes-api/... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/kubectl.md | main | kubernetes | [
0.042014896869659424,
-0.007433120161294937,
0.05359597131609917,
-0.04577931761741638,
0.027089163661003113,
0.009419837966561317,
-0.07488939166069031,
-0.0243514496833086,
-0.0059246220625936985,
0.04665258526802063,
0.01206094678491354,
-0.03742887079715729,
-0.04555528610944748,
-0.08... | 0.148691 |
This page provides a high-level overview of the essential components that make up a Kubernetes cluster. {{< figure src="/images/docs/components-of-kubernetes.svg" alt="Components of Kubernetes" caption="The components of a Kubernetes cluster" class="diagram-large" clicktozoom="true" >}} ## Core Components A Kubernetes ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/components.md | main | kubernetes | [
0.01107893604785204,
-0.037743885070085526,
0.03619406372308731,
0.03469504043459892,
0.012790522538125515,
0.04465353488922119,
-0.045959580689668655,
-0.0462907999753952,
0.06317298859357834,
0.06474944949150085,
-0.04733095318078995,
-0.02485506422817707,
-0.02990267425775528,
-0.032629... | 0.224322 |
This page is an overview of Kubernetes. The name Kubernetes originates from Greek, meaning helmsman or pilot. K8s as an abbreviation results from counting the eight letters between the "K" and the "s". Google open sourced the Kubernetes project in 2014. Kubernetes combines [over 15 years of Google's experience](/blog/2... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/_index.md | main | kubernetes | [
-0.02242208644747734,
0.01660950295627117,
0.061010345816612244,
-0.038244739174842834,
-0.022775044664740562,
0.011242110282182693,
0.00006140217010397464,
0.03255630284547806,
0.09234008938074112,
0.055268313735723495,
-0.08140413463115692,
0.033232539892196655,
0.03005945309996605,
-0.0... | 0.220481 |
solutions. However, Kubernetes is not monolithic, and these default solutions are optional and pluggable. Kubernetes provides the building blocks for building developer platforms, but preserves user choice and flexibility where it is important. Kubernetes: \* Does not limit the types of applications supported. Kubernet... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/_index.md | main | kubernetes | [
-0.02052967995405197,
-0.009954303503036499,
0.06209883466362953,
-0.07108397036790848,
-0.0617453008890152,
-0.01832273229956627,
0.0007926818798296154,
0.024824749678373337,
0.09328063577413559,
0.048169124871492386,
-0.0876961424946785,
-0.04833625629544258,
0.013708813115954399,
-0.026... | 0.238087 |
system, on top of the virtualized hardware. \*\*Container deployment era:\*\* Containers are similar to VMs, but they have relaxed isolation properties to share the Operating System (OS) among the applications. Therefore, containers are considered lightweight. Similar to a VM, a container has its own filesystem, share ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/_index.md | main | kubernetes | [
0.04158666729927063,
0.05734784156084061,
0.011928720399737358,
-0.010081984102725983,
0.09837168455123901,
-0.05567602440714836,
-0.009089192375540733,
0.056847188621759415,
0.0012731443857774138,
0.037411972880363464,
-0.023544710129499435,
-0.02297911047935486,
-0.005064134020358324,
-0... | 0.257143 |
Each {{< glossary\_tooltip text="object" term\_id="object" >}} in your cluster has a [\_Name\_](#names) that is unique for that type of resource. Every Kubernetes object also has a [\_UID\_](#uids) that is unique across your whole cluster. For example, you can only have one Pod named `myapp-1234` within the same [names... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/names.md | main | kubernetes | [
-0.03150332719087601,
-0.03617427498102188,
0.06277267634868622,
-0.01917562633752823,
-0.04303566366434097,
-0.022375399246811867,
0.07352079451084137,
-0.07255382835865021,
0.09341219067573547,
-0.01981332339346409,
-0.009747943840920925,
-0.11044199019670486,
0.032874852418899536,
-0.01... | 0.081278 |
is enabled for Service objects, which allows Service names to start with digits. {{< /note >}} ### Path Segment Names Some resource types require their names to be able to be safely encoded as a path segment. In other words, the name may not be "." or ".." and the name may not contain "/" or "%". Here's an example mani... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/names.md | main | kubernetes | [
-0.06726323813199997,
0.029867922887206078,
0.04916275665163994,
-0.0471300333738327,
-0.05211346969008446,
-0.03589235246181488,
0.033244263380765915,
-0.03841047361493111,
0.11199341714382172,
-0.014820517040789127,
-0.006677677389234304,
-0.033383969217538834,
-0.02166096493601799,
0.04... | 0.155407 |
\_Field selectors\_ let you select Kubernetes {{< glossary\_tooltip text="objects" term\_id="object" >}} based on the value of one or more resource fields. Here are some examples of field selector queries: \* `metadata.name=my-service` \* `metadata.namespace!=default` \* `status.phase=Pending` This `kubectl` command se... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/field-selectors.md | main | kubernetes | [
0.012600364163517952,
0.060779403895139694,
0.06789868324995041,
0.0522654727101326,
-0.017653629183769226,
-0.03022703528404236,
0.12950918078422546,
-0.08022766560316086,
0.08862277120351791,
0.028154492378234863,
-0.027792517095804214,
-0.12032144516706467,
-0.037477537989616394,
-0.073... | 0.113534 |
{{}} You can use finalizers to control {{}} of {{< glossary\_tooltip text="objects" term\_id="object" >}} by alerting {{}} to perform specific cleanup tasks before deleting the target resource. Finalizers don't usually specify the code to execute. Instead, they are typically lists of keys on a specific resource similar... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/finalizers.md | main | kubernetes | [
-0.04368874430656433,
0.0518210306763649,
0.06844385713338852,
0.0013149352744221687,
-0.013778424821794033,
-0.03122095763683319,
0.08203664422035217,
-0.12128337472677231,
0.15064020454883575,
0.04335946589708328,
-0.04124408960342407,
-0.0500885508954525,
-0.006713633891195059,
-0.02471... | 0.096675 |
when it identifies owner references on a resource targeted for deletion. In some situations, finalizers can block the deletion of dependent objects, which can cause the targeted owner object to remain for longer than expected without being fully deleted. In these situations, you should check finalizers and owner refere... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/finalizers.md | main | kubernetes | [
-0.011948526836931705,
0.04130585491657257,
0.09149009734392166,
0.013824257999658585,
0.03497910872101784,
-0.00045801527448929846,
0.011644621379673481,
-0.06138982996344566,
0.08306075632572174,
0.01713591441512108,
0.004910232499241829,
0.012870470993220806,
-0.02889183536171913,
0.007... | 0.121315 |
In Kubernetes, \_namespaces\_ provide a mechanism for isolating groups of resources within a single cluster. Names of resources need to be unique within a namespace, but not across namespaces. Namespace-based scoping is applicable only for namespaced {{< glossary\_tooltip text="objects" term\_id="object" >}} \_(e.g. De... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/namespaces.md | main | kubernetes | [
-0.050588447600603104,
-0.06351689994335175,
0.03506528213620186,
0.01858389936387539,
-0.02323165163397789,
-0.006937879603356123,
0.10231377929449081,
-0.09079672396183014,
0.10728927701711655,
0.00885270070284605,
0.00003209586066077463,
-0.10145233571529388,
0.038617003709077835,
0.002... | 0.093885 |
name (FQDN). As a result, all namespace names must be valid [RFC 1123 DNS labels](/docs/concepts/overview/working-with-objects/names/#dns-label-names). {{< warning >}} By creating namespaces with the same name as [public top-level domains](https://data.iana.org/TLD/tlds-alpha-by-domain.txt), Services in these namespace... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/namespaces.md | main | kubernetes | [
-0.13096629083156586,
-0.053384456783533096,
-0.06253660470247269,
-0.024352582171559334,
-0.10046607255935669,
-0.08514735847711563,
0.0195310041308403,
-0.05160899832844734,
0.05968974903225899,
-0.041092194616794586,
-0.009832015261054039,
-0.01887481100857258,
0.04924175888299942,
0.03... | 0.050086 |
You can visualize and manage Kubernetes objects with more tools than kubectl and the dashboard. A common set of labels allows tools to work interoperably, describing objects in a common manner that all tools can understand. In addition to supporting tooling, the recommended labels describe applications in a way that ca... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/common-labels.md | main | kubernetes | [
-0.01774323172867298,
0.014771001413464546,
-0.01570960134267807,
-0.05260171368718147,
-0.00017299700994044542,
0.02566167339682579,
0.030839119106531143,
0.013607899658381939,
0.1287108063697815,
0.027187084779143333,
-0.04782102629542351,
-0.07146182656288147,
0.018991852179169655,
-0.0... | 0.211962 |
(MySQL), installed using Helm. The following snippets illustrate the start of objects used to deploy this application. The start to the following `Deployment` is used for WordPress: ```yaml apiVersion: apps/v1 kind: Deployment metadata: labels: app.kubernetes.io/name: wordpress app.kubernetes.io/instance: wordpress-abc... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/common-labels.md | main | kubernetes | [
0.02119372971355915,
0.015002090483903885,
-0.016616718843579292,
-0.039246100932359695,
-0.009764525108039379,
-0.037651870399713516,
0.010795111767947674,
-0.0027614186983555555,
0.11411389708518982,
0.06240101531147957,
0.025308631360530853,
-0.011551628820598125,
0.06315194070339203,
-... | 0.135973 |
You can use Kubernetes annotations to attach arbitrary non-identifying metadata to {{< glossary\_tooltip text="objects" term\_id="object" >}}. Clients such as tools and libraries can retrieve this metadata. ## Attaching metadata to objects You can use either labels or annotations to attach metadata to Kubernetes object... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/annotations.md | main | kubernetes | [
-0.006756477989256382,
0.045857224613428116,
0.013848424889147282,
-0.022461572661995888,
-0.008189006708562374,
0.029751881957054138,
0.07730364799499512,
-0.0753697082400322,
0.13309602439403534,
-0.02053752914071083,
-0.0025814794935286045,
-0.11261309683322906,
0.004375010263174772,
0.... | 0.112435 |
Find [Well-known labels, Annotations and Taints](/docs/reference/labels-annotations-taints/) | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/annotations.md | main | kubernetes | [
-0.06401459872722626,
0.09448464959859848,
-0.04286994785070419,
-0.02517830953001976,
0.1039147600531578,
0.02687561884522438,
0.08653929829597473,
-0.0017374868039041758,
-0.02553298883140087,
-0.06376281380653381,
0.04242639243602753,
-0.06142240762710571,
-0.008445549756288528,
0.03185... | 0.20047 |
The Kubernetes API server stores objects, relying on an etcd-compatible backing store (often, the backing storage is etcd itself). Each object is serialized using a particular version of that API type; for example, the v1 representation of a ConfigMap. Kubernetes uses the term \_storage version\_ to describe how an obj... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/storage-version.md | main | kubernetes | [
-0.006431501358747482,
0.024308321997523308,
0.07792013138532639,
-0.0024186770897358656,
0.002846126677468419,
0.026236526668071747,
-0.11414798349142075,
-0.059154536575078964,
0.12773361802101135,
0.02271955832839012,
-0.05001455917954445,
0.011906955391168594,
-0.016305070370435715,
-0... | 0.158273 |
can be enabled/disabled by Served flag. served: true # One and only one version must be marked as the storage version. storage: true schema: openAPIV3Schema: type: object properties: host: type: string port: type: string - name: v1 served: true storage: false schema: openAPIV3Schema: type: object properties: host: type... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/storage-version.md | main | kubernetes | [
-0.03510341793298721,
0.027394646778702736,
-0.06726405024528503,
0.0031595511827617884,
-0.040879249572753906,
0.020345043390989304,
-0.042797017842531204,
0.0003838068514596671,
-0.041644852608442307,
-0.021850906312465668,
-0.005240259226411581,
-0.04711518436670303,
-0.014899416826665401... | 0.020963 |
cannot be fully removed from use until then. See [storage version migration](/docs/tasks/manage-kubernetes-objects/storage-version-migration) on examples of how to run a migration to ensure that all objects are using a newer storage version without manual intervention. | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/storage-version.md | main | kubernetes | [
0.05140936002135277,
0.03994149714708328,
0.06461203098297119,
0.0004476002650335431,
0.046328600496053696,
-0.015655992552638054,
-0.029659602791070938,
-0.10096679627895355,
0.08440268039703369,
0.05307416245341301,
0.03139335662126541,
0.03382684662938118,
-0.025423193350434303,
-0.0049... | 0.03098 |
In Kubernetes, some {{< glossary\_tooltip text="objects" term\_id="object" >}} are \*owners\* of other objects. For example, a {{}} is the owner of a set of Pods. These owned objects are \*dependents\* of their owner. Ownership is different from the [labels and selectors](/docs/concepts/overview/working-with-objects/la... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/owners-dependents.md | main | kubernetes | [
-0.0546484999358654,
0.004578219726681709,
0.03703732043504715,
-0.021746864542365074,
-0.03305232152342796,
-0.01921715773642063,
0.14452511072158813,
-0.05407773330807686,
0.114188052713871,
0.008189331740140915,
-0.009813888929784298,
-0.051969774067401886,
0.005175423342734575,
-0.0186... | 0.160527 |
owner resource when you use either [foreground or orphan cascading deletion](/docs/concepts/architecture/garbage-collection/#cascading-deletion). In foreground deletion, it adds the `foreground` finalizer so that the controller must delete dependent resources that also have `ownerReferences.blockOwnerDeletion=true` bef... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/owners-dependents.md | main | kubernetes | [
-0.006229155231267214,
0.03472292795777321,
0.06700710207223892,
-0.039151426404714584,
0.023539632558822632,
-0.01994284614920616,
0.04728114604949951,
-0.043260060250759125,
0.13979029655456543,
0.055495355278253555,
0.021589038893580437,
-0.01898442953824997,
-0.012893497943878174,
0.01... | 0.109722 |
\_Labels\_ are key/value pairs that are attached to {{< glossary\_tooltip text="objects" term\_id="object" >}} such as Pods. Labels are intended to be used to specify identifying attributes of objects that are meaningful and relevant to users, but do not directly imply semantics to the core system. Labels can be used t... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/labels.md | main | kubernetes | [
-0.06672941148281097,
0.022383248433470726,
-0.026091597974300385,
-0.015382708981633186,
-0.020019611343741417,
-0.010203051380813122,
0.1078929677605629,
-0.03400538116693497,
0.07521628588438034,
-0.04293834790587425,
0.028366971760988235,
-0.050479788333177567,
0.025701718404889107,
-0... | 0.175292 |
can be made of multiple \_requirements\_ which are comma-separated. In the case of multiple requirements, all must be satisfied so the comma separator acts as a logical \_AND\_ (`&&`) operator. The semantics of empty or non-specified selectors are dependent on the context, and API types that use selectors should docume... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/labels.md | main | kubernetes | [
-0.07026134431362152,
0.05942947044968605,
0.01054964866489172,
-0.03668795898556709,
0.06149661913514137,
0.03909987583756447,
0.04824821278452873,
-0.05142226815223694,
-0.004897462669759989,
-0.026692437008023262,
-0.0032153138890862465,
-0.15874901413917542,
0.07765915244817734,
0.0075... | 0.081878 |
query string): \* \_equality-based\_ requirements: `?labelSelector=environment%3Dproduction,tier%3Dfrontend` \* \_set-based\_ requirements: `?labelSelector=environment+in+%28production%2Cqa%29%2Ctier+in+%28frontend%29` Both label selector styles can be used to list or watch resources via a REST client. For example, tar... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/labels.md | main | kubernetes | [
0.01451246626675129,
0.07867942750453949,
0.00028033702983520925,
0.0013421919429674745,
-0.05168766900897026,
0.007948269136250019,
0.06614839285612106,
0.01819491945207119,
0.011459899134933949,
-0.03161140903830528,
-0.03491264209151268,
-0.18828438222408295,
0.043726131319999695,
-0.06... | 0.141031 |
resources along any dimension specified by a label: ```shell kubectl apply -f examples/guestbook/all-in-one/guestbook-all-in-one.yaml kubectl get pods -Lapp -Ltier -Lrole ``` ```none NAME READY STATUS RESTARTS AGE APP TIER ROLE guestbook-fe-4nlpb 1/1 Running 0 1m guestbook frontend guestbook-fe-ght6d 1/1 Running 0 1m g... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/labels.md | main | kubernetes | [
0.03387262672185898,
0.010870269499719143,
-0.05400801822543144,
-0.00266274088062346,
0.027738947421312332,
0.002980054123327136,
-0.04518583044409752,
-0.02538609318435192,
0.04517311975359917,
0.01070251315832138,
-0.012533240020275116,
-0.05352996289730072,
0.0181720107793808,
-0.07022... | 0.076588 |
The `kubectl` command-line tool supports several different ways to create and manage Kubernetes {{< glossary\_tooltip text="objects" term\_id="object" >}}. This document provides an overview of the different approaches. Read the [Kubectl book](https://kubectl.docs.kubernetes.io) for details of managing objects by Kubec... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/object-management.md | main | kubernetes | [
-0.02014421857893467,
0.025822283700108528,
0.052764810621738434,
0.04029753431677818,
-0.02549945004284382,
-0.06410716474056244,
0.05258798599243164,
-0.08363799750804901,
0.11063282191753387,
0.015132199041545391,
-0.005702432245016098,
-0.10185226052999496,
0.02288852632045746,
-0.0476... | 0.136915 |
and easier to understand. - As of Kubernetes version 1.5, imperative object configuration is more mature. Disadvantages compared to declarative object configuration: - Imperative object configuration works best on files, not directories. - Updates to live objects must be reflected in configuration files, or they will b... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/object-management.md | main | kubernetes | [
-0.024764442816376686,
0.04095687344670296,
0.09117840975522995,
-0.014157545752823353,
-0.026008667424321175,
-0.06900578737258911,
-0.0593658871948719,
-0.04584003984928131,
0.12087975442409515,
0.07366844266653061,
-0.003801712766289711,
0.017505189403891563,
-0.039769046008586884,
-0.0... | 0.140906 |
This page explains how Kubernetes objects are represented in the Kubernetes API, and how you can express them in `.yaml` format. ## Understanding Kubernetes objects {#kubernetes-objects} \*Kubernetes objects\* are persistent entities in the Kubernetes system. Kubernetes uses these entities to represent the state of you... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/_index.md | main | kubernetes | [
0.021639104932546616,
-0.009550448507070541,
0.007077059708535671,
0.018042005598545074,
-0.02592279389500618,
-0.0037315990775823593,
0.022523721680045128,
-0.058499936014413834,
0.13260477781295776,
0.04364435747265816,
-0.05150328576564789,
-0.0478462316095829,
-0.012479512952268124,
-0... | 0.216189 |
`kubectl` command-line interface, passing the `.yaml` file as an argument. Here's an example: ```shell kubectl apply -f https://k8s.io/examples/application/deployment.yaml ``` The output is similar to this: ``` deployment.apps/nginx-deployment created ``` ### Required fields In the manifest (YAML or JSON file) for the ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/overview/working-with-objects/_index.md | main | kubernetes | [
-0.00006633848533965647,
0.06307917833328247,
0.0018714682664722204,
-0.013208921067416668,
-0.06813463568687439,
0.006086279172450304,
0.027288757264614105,
0.03382699564099312,
0.05637533590197563,
0.0735839456319809,
-0.06460671126842499,
-0.12760326266288757,
-0.01748291216790676,
0.00... | 0.105896 |
By default, containers run with unbounded [compute resources](/docs/concepts/configuration/manage-resources-containers/) on a Kubernetes cluster. Using Kubernetes [resource quotas](/docs/concepts/policy/resource-quotas/), administrators (also termed \_cluster operators\_) can restrict consumption and creation of cluste... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/limit-range.md | main | kubernetes | [
-0.015053312294185162,
0.018303869292140007,
0.019961467012763023,
0.02851695567369461,
-0.041971102356910706,
-0.05060527101159096,
0.06992419064044952,
-0.06139726564288139,
0.08246311545372009,
0.04083144664764404,
-0.0457141175866127,
-0.07210236042737961,
-0.008288376964628696,
-0.038... | 0.123251 |
to the namespace level. This implies that any references or operations within these examples will interact with elements within the default namespace of your cluster. You can override the operating namespace by configuring namespace in the `metadata.namespace` field. {{< /note >}} {{% code\_sample file="concepts/policy... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/limit-range.md | main | kubernetes | [
0.008792955428361893,
-0.004425850696861744,
0.001750726136378944,
0.06202155351638794,
0.018364109098911285,
-0.05396845564246178,
-0.007342237047851086,
-0.0003381164569873363,
0.0004288960190024227,
-0.01062428392469883,
-0.034122761338949203,
-0.00903176050633192,
-0.023124905303120613,
... | 0.147008 |
When several users or teams share a cluster with a fixed number of nodes, there is a concern that one team could use more than its fair share of resources. \_Resource quotas\_ are a tool for administrators to address this concern. A resource quota, defined by a ResourceQuota object, provides constraints that limit aggr... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/resource-quotas.md | main | kubernetes | [
-0.0862310528755188,
0.0002969335182569921,
0.025423100218176842,
0.020004894584417343,
-0.019112693145871162,
-0.020881809294223785,
0.09266051650047302,
-0.07533957064151764,
0.0941251665353775,
0.03887531906366348,
-0.035010043531656265,
-0.08327412605285645,
0.05506554991006851,
0.0150... | 0.105629 |
storage of this namespace. You can use a [LimitRange](/docs/concepts/policy/limit-range/) to automatically set a default request for these resources. The name of a ResourceQuota object must be a valid [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names). Examples of policies that... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/resource-quotas.md | main | kubernetes | [
-0.03207702189683914,
-0.05443790182471275,
-0.033699389547109604,
0.01842918060719967,
-0.10407006740570068,
-0.04250152036547661,
0.021838871762156487,
-0.05323575437068939,
0.01982668600976467,
0.05583229660987854,
-0.07130272686481476,
-0.051591645926237106,
0.04197103902697563,
0.0186... | 0.137879 |
resource either explicitly when the device class's ExtendedResourceName field is given, say, `example.com/gpu`, then you can define a quota as follows: \* `requests.example.com/gpu: 4` or implicitly using the derived extended resource name from device class name `examplegpu`, you can define a quota as follows: \* `requ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/resource-quotas.md | main | kubernetes | [
-0.01070575974881649,
0.0062710498459637165,
-0.0010169177548959851,
0.0005702192429453135,
-0.023575855419039726,
-0.028577454388141632,
0.02658383548259735,
0.010494721122086048,
0.06295377016067505,
0.00669023348018527,
-0.056715648621320724,
-0.038086067885160446,
0.05232589319348335,
... | 0.088768 |
API group, use `count/widgets.example.com`. If you use [API aggregation](/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/) to add additional, custom APIs that are not defined as CustomResourceDefinitions, the core Kubernetes control plane does not enforce quota for the aggregated API. The extension... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/resource-quotas.md | main | kubernetes | [
-0.009531286545097828,
-0.022546052932739258,
0.0006613577716052532,
0.04423561319708824,
-0.08733142167329788,
0.04277648776769638,
-0.0015339857200160623,
0.040919508785009384,
0.13078370690345764,
0.06402280926704407,
-0.05995265021920204,
-0.10811411589384079,
0.054398007690906525,
0.0... | 0.0919 |
all standard namespaced resources using the syntax `count/.`: ```shell kubectl create namespace myspace ``` ```shell kubectl create quota test --hard=count/deployments.apps=2,count/replicasets.apps=4,count/pods=3,count/secrets=4 --namespace=myspace ``` ```shell kubectl create deployment nginx --image=nginx --namespace=... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/resource-quotas.md | main | kubernetes | [
-0.007771472912281752,
-0.03630514070391655,
0.0012532436521723866,
0.056559208780527115,
-0.006621169857680798,
-0.030700845643877983,
0.014903453178703785,
-0.06388315558433533,
0.084536112844944,
0.05299955606460571,
-0.03507975488901138,
-0.09423931688070297,
0.06229748576879501,
-0.00... | 0.126334 |
pods that have the [Guaranteed](/docs/concepts/workloads/pods/pod-qos/#guaranteed) or [Burstable](/docs/concepts/workloads/pods/pod-qos/#burstable) [QoS class](/docs/concepts/workloads/pods/pod-qos/). The `operator` for a `scopeSelector` must be `Exists`. ### Non-terminating Pods scope {#quota-scope-non-terminating} Th... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/resource-quotas.md | main | kubernetes | [
-0.019895242527127266,
0.02308979257941246,
-0.020326295867562294,
0.09049100428819656,
-0.03559878468513489,
-0.06949854642152786,
0.07824105769395828,
0.016057202592492104,
0.04688217490911484,
0.05157189071178436,
-0.026400357484817505,
-0.0414281003177166,
-0.03492174670100212,
0.01257... | 0.206413 |
If you want to try this out, use a testing cluster and set up those three PriorityClasses before you continue. - One quota object is created for each priority. Inspect this set of ResourceQuotas: {{% code\_sample file="policy/quota.yaml" %}} Apply the YAML using `kubectl create`. ```shell kubectl create -f https://k8s.... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/resource-quotas.md | main | kubernetes | [
0.016202682629227638,
0.0029246294870972633,
0.0052658505737781525,
-0.01564183458685875,
-0.05234067142009735,
-0.02010771818459034,
0.0026725339703261852,
0.015469524078071117,
0.03457145020365715,
0.0765378475189209,
0.008720357902348042,
-0.11447198688983917,
-0.0004167339648120105,
-0... | 0.110674 |
the `scopeSelector` field, the quota object is restricted to track only the following resources: \* `persistentvolumeclaims` \* `requests.storage` Read [Limit Storage Consumption](/docs/tasks/administer-cluster/limit-storage-consumption/) to learn more about this. ## {{% heading "whatsnext" %}} - See a [detailed exampl... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/resource-quotas.md | main | kubernetes | [
-0.039066560566425323,
0.05993635579943657,
0.006638507358729839,
0.007684759330004454,
-0.030896445736289024,
0.010623473674058914,
0.01995084062218666,
0.012897351756691933,
0.06925974786281586,
0.05081072822213173,
-0.07655409723520279,
-0.06360188871622086,
0.0002822635287884623,
-0.01... | 0.132481 |
{{< feature-state for\_k8s\_version="v1.20" state="stable" >}} Kubernetes allow you to limit the number of process IDs (PIDs) that a {{< glossary\_tooltip term\_id="Pod" text="Pod" >}} can use. You can also reserve a number of allocatable PIDs for each {{< glossary\_tooltip term\_id="node" text="node" >}} for use by th... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/pid-limiting.md | main | kubernetes | [
-0.009301048703491688,
-0.0057264817878603935,
0.07296407222747803,
-0.012997949495911598,
-0.01571107655763626,
-0.008625048212707043,
0.02188383787870407,
-0.010024544782936573,
0.06828711181879044,
0.06013146787881851,
-0.043221842497587204,
-0.00578570319339633,
0.030613258481025696,
-... | 0.169948 |
allows you to limit the number of processes running in a Pod. You specify this limit at the node level, rather than configuring it as a resource limit for a particular Pod. Each Node can have a different PID limit. To configure the limit, you can specify the command line parameter `--pod-max-pids` to the kubelet, or se... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/pid-limiting.md | main | kubernetes | [
0.016924763098359108,
0.01810476928949356,
0.03537241369485855,
0.006685664411634207,
-0.040871910750865936,
-0.032254479825496674,
-0.019273700192570686,
0.003968849778175354,
0.07988494634628296,
0.03440820053219795,
-0.033760856837034225,
0.018826277926564217,
-0.02426142431795597,
-0.0... | 0.210095 |
Kubernetes policies are configurations that manage other configurations or runtime behaviors. Kubernetes offers various forms of policies, described below: ## Apply policies using API objects Some API objects act as policies. Here are some examples: \* [NetworkPolicies](/docs/concepts/services-networking/network-polici... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/policy/_index.md | main | kubernetes | [
-0.06770580261945724,
0.030489787459373474,
0.047960128635168076,
-0.03395592421293259,
-0.014576009474694729,
0.010406194254755974,
0.10663102567195892,
-0.038195088505744934,
0.0716540589928627,
0.07189076393842697,
-0.03643622249364853,
-0.021916933357715607,
0.025453617796301842,
-0.00... | 0.174566 |
Kubernetes can be configured to use swap memory on a {{< glossary\_tooltip text="node" term\_id="node" >}}, allowing the kernel to free up physical memory by swapping out pages to backing storage. This is useful for multiple use-cases. For example, nodes running workloads that can benefit from using swap, such as those... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/swap-memory-management.md | main | kubernetes | [
0.034685730934143066,
0.017345227301120758,
0.01942899450659752,
0.051708199083805084,
-0.048483412712812424,
0.07997335493564606,
-0.02427089959383011,
0.0046858652494847775,
0.06780366599559784,
0.0707223191857338,
-0.0480562224984169,
0.030323991551995277,
-0.02630315162241459,
-0.08366... | 0.208453 |
and remaining swap memory when using `LimitedSwap`. Additionally, a `machine\_swap\_bytes` metric has been added to cadvisor to show the total physical swap capacity of the machine. See [this page](/docs/reference/instrumentation/node-metrics/) for more info. For example, these `/metrics/resource` are supported: - `nod... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/swap-memory-management.md | main | kubernetes | [
0.020905863493680954,
-0.0016431583790108562,
0.0037944912910461426,
-0.009279711171984673,
-0.015685303136706352,
-0.03637368604540825,
-0.006669217720627785,
0.0737331211566925,
0.027977081015706062,
0.03372364118695259,
-0.05154327303171158,
-0.025323595851659775,
0.01872759498655796,
-... | 0.21007 |
Pods that frequently use their RAM may cause other Pods to swap. In addition, since swap allows for greater memory usage for workloads in Kubernetes that cannot be predictably accounted for, and due to unexpected packing configurations, the scheduler currently does not account for swap memory usage. This heightens the ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/swap-memory-management.md | main | kubernetes | [
0.02441769652068615,
0.003459680126979947,
0.06881692260503769,
0.05839787423610687,
-0.017503999173641205,
0.004616369027644396,
-0.035075630992650986,
0.037351131439208984,
0.10730157792568207,
0.05065172538161278,
-0.0684586688876152,
0.07006996870040894,
-0.019439036026597023,
-0.08268... | 0.152245 |
never being able to swap out during node memory pressure. However, setting the eviction thresholds too high could result in the node running out of memory and invoking the OOM killer, which is not ideal either. To address this, it is recommended to set the kubelet's eviction thresholds to be slightly lower than the `vm... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/swap-memory-management.md | main | kubernetes | [
0.038915056735277176,
0.04484201967716217,
0.04213084653019905,
0.04745946452021599,
-0.035551153123378754,
-0.014641192741692066,
-0.0024779189843684435,
0.05124063417315483,
0.08794207870960236,
0.04205654188990593,
-0.017776042222976685,
0.008441650308668613,
-0.038315482437610626,
-0.1... | 0.129292 |
disk. When they share the same disk, processes can overwhelm swap, disrupting the I/O of kubelet, container runtime, and systemd, which would impact other workloads. Since swap space is located on a disk, it is crucial to ensure the disk is fast enough for the intended use cases. Alternatively, one can configure I/O pr... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/swap-memory-management.md | main | kubernetes | [
0.013123642653226852,
0.010053159669041634,
0.08981841802597046,
0.007475430145859718,
-0.02805415354669094,
-0.009891781955957413,
-0.03095032460987568,
0.001325300196185708,
0.1115773469209671,
0.04712212458252907,
-0.05712222307920456,
0.04905632883310318,
-0.009021119214594364,
-0.0522... | 0.158891 |
is proportionate to its memory request, the node's total physical memory and the total amount of swap memory on the node that is available for use by Pods. It is important to note that, for containers within Burstable QoS Pods, it is possible to opt-out of swap usage by specifying memory requests that are equal to memo... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/swap-memory-management.md | main | kubernetes | [
0.049990445375442505,
0.03672480583190918,
0.016571862623095512,
0.020202064886689186,
-0.044917840510606766,
0.04024611786007881,
0.0043982514180243015,
0.06049945577979088,
0.05331701412796974,
0.06369142979383469,
-0.04713506996631622,
0.04917412996292114,
-0.018930507823824883,
-0.0902... | 0.193092 |
This page describes good practices when configuring a Kubernetes cluster utilizing Dynamic Resource Allocation (DRA). These instructions are for cluster administrators. ## Separate permissions to DRA related APIs DRA is orchestrated through a number of different APIs. Use authorization tools (like RBAC, or another solu... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/dra.md | main | kubernetes | [
-0.02241925708949566,
0.0037694803904742002,
0.056574150919914246,
-0.01695762202143669,
-0.04808814823627472,
0.0027197927702218294,
0.014108498580753803,
0.025354182347655296,
0.026270266622304916,
0.03785832226276398,
-0.038845743983983994,
-0.052386220544576645,
-0.024409832432866096,
... | 0.191057 |
component {{< glossary\_tooltip text="kube-scheduler" term\_id="kube-scheduler" >}} and the internal ResourceClaim controller orchestrated by the component {{< glossary\_tooltip text="kube-controller-manager" term\_id="kube-controller-manager" >}} do the heavy lifting during scheduling of Pods with claims based on meta... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/dra.md | main | kubernetes | [
-0.019335299730300903,
0.008198167197406292,
0.08415765315294266,
0.06567347049713135,
0.027576223015785217,
-0.05484126880764961,
0.011971544474363327,
0.02504432015120983,
0.11922076344490051,
0.03985022008419037,
-0.05058472603559494,
-0.0103832446038723,
-0.0316895917057991,
-0.0307268... | 0.198705 |
more manageable. ### `kube-scheduler` metrics The following scheduler metrics are high level metrics aggregating performance across all Pods scheduled, not just those using DRA. It is important to note that the end-to-end metrics are ultimately influenced by the `kube-controller-manager`'s performance in creating Resou... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/dra.md | main | kubernetes | [
0.004915407858788967,
0.003653722582384944,
0.015985742211341858,
0.011947841383516788,
-0.0521022193133831,
-0.04938394948840141,
-0.034010156989097595,
-0.009084025397896767,
0.05055626109242439,
-0.0029396594036370516,
-0.08127225935459137,
-0.11181434988975525,
-0.05364592373371124,
-0... | 0.161147 |
This page explains proxies used with Kubernetes. ## Proxies There are several different proxies you may encounter when using Kubernetes: 1. The [kubectl proxy](/docs/tasks/access-application-cluster/access-cluster/#directly-accessing-the-rest-api): - runs on a user's desktop or in a pod - proxies from a localhost addre... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/proxies.md | main | kubernetes | [
-0.017489485442638397,
0.009273812174797058,
0.029390791431069374,
-0.0450470969080925,
-0.043861910700798035,
0.02589242346584797,
0.029926760122179985,
-0.03513989597558975,
0.1279086470603943,
0.06874285638332367,
-0.0764891728758812,
0.053575191646814346,
0.01994280517101288,
-0.046597... | 0.162585 |
This page provides good practices and considerations when designing \_admission webhooks\_ in Kubernetes. This information is intended for cluster operators who run admission webhook servers or third-party applications that modify or validate your API requests. Before reading this page, ensure that you're familiar with... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/admission-webhooks-good-practices.md | main | kubernetes | [
-0.030502261593937874,
0.07309260219335556,
0.0034550654236227274,
-0.042899202555418015,
-0.00829374697059393,
-0.04554934427142143,
0.03364776447415352,
-0.040151745080947876,
0.039118796586990356,
0.031210239976644516,
-0.02314860373735428,
-0.0731825977563858,
0.02682727389037609,
-0.0... | 0.184315 |
Intercept API requests before admission and validate against complex policy declarations. | * Validate critical configurations before resource admission. * Enforce complex policy logic before admission. | | [Validating admission policy](/docs/reference/access-authn-authz/validating-admission-policy/) | Intercept API re... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/admission-webhooks-good-practices.md | main | kubernetes | [
-0.047720108181238174,
0.11234614253044128,
0.01478908583521843,
-0.03896143287420273,
-0.011690781451761723,
-0.04119063913822174,
0.01941114291548729,
-0.013768376782536507,
0.04315286502242088,
0.025615062564611435,
-0.02235531434416771,
-0.12760166823863983,
0.043281570076942444,
-0.00... | 0.083833 |
ensure webhook availability {#load-balancer-webhook} Admission webhooks should leverage some form of load-balancing to provide high availability and performance benefits. If a webhook is running within the cluster, you can run multiple webhook backends behind a Service of type `ClusterIP`. ### Use a high-availability d... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/admission-webhooks-good-practices.md | main | kubernetes | [
0.004616522695869207,
0.04048219323158264,
0.0558365099132061,
0.009860585443675518,
-0.01857439987361431,
-0.06749074906110764,
-0.04087206721305847,
-0.04586804285645485,
0.01944071799516678,
0.06294310837984085,
-0.03239431604743004,
-0.06190933287143707,
-0.021790659055113792,
-0.09120... | 0.156369 |
in mutations when possible. \* Avoid self-mutations. \* Fail open and validate the final state. \* Plan for future field updates in later versions. \* Prevent webhooks from self-triggering. \* Don't change immutable objects. ### Patch only required fields {#patch-required-fields} Admission webhook servers send HTTP res... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/admission-webhooks-good-practices.md | main | kubernetes | [
-0.05902335047721863,
0.07928898185491562,
0.05426893010735512,
-0.03870752081274986,
-0.00088381243404001,
-0.07824189960956573,
-0.011519302614033222,
-0.0573844276368618,
0.05124896764755249,
0.06105086952447891,
-0.0059877075254917145,
-0.07642016559839249,
0.01194149348884821,
-0.0735... | 0.167056 |
cluster add-on components, such as networking plugins or storage plugins, that your webhook depends on. If both the webhook and the dependent add-on become unavailable, neither component can function. To avoid these dependency loops, try the following: \* Use [ValidatingAdmissionPolicies](/docs/reference/access-authn-a... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/admission-webhooks-good-practices.md | main | kubernetes | [
-0.07927469164133072,
0.06094605475664139,
-0.046111948788166046,
0.014835321344435215,
0.04611983150243759,
-0.049594249576330185,
0.01584779843688011,
-0.06639308482408524,
-0.03152007237076759,
-0.017264965921640396,
0.03809110447764397,
-0.09156633168458939,
0.016244443133473396,
-0.01... | 0.024749 |
running at a specific point in the admission process. Other webhooks could still mutate your modified object. The following recommendations might help to minimize the risk of unintended changes: \* [Validate mutations before admission](#validate-mutations) \* Use a reinvocation policy to observe changes to an object by... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/admission-webhooks-good-practices.md | main | kubernetes | [
-0.04863327741622925,
0.0316513329744339,
-0.04739411175251007,
0.009925647638738155,
0.034351278096437454,
-0.06831827759742737,
0.014075621031224728,
-0.0485764741897583,
-0.049276821315288544,
0.03663310036063194,
0.04237506911158562,
-0.07215048372745514,
0.029497921466827393,
-0.06984... | 0.127903 |
mutations don't violate validations {#ensure-mutations-dont-violate-validations} Your mutating webhooks shouldn't break any of the validations that apply to an object before admission. For example, consider a mutating webhook that sets the default CPU request of a Pod to a specific value. If the CPU limit of that Pod i... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/admission-webhooks-good-practices.md | main | kubernetes | [
-0.008461683988571167,
0.023727742955088615,
0.06662195175886154,
-0.03627195209264755,
0.069978266954422,
-0.11776565760374069,
-0.07190228253602982,
-0.043291784822940826,
-0.022909538820385933,
0.025482309982180595,
0.022596869617700577,
-0.0745776817202568,
0.0012187284883111715,
-0.05... | 0.101613 |
examples as-is; use them as a starting point and design your webhooks to run well in your specific environment. \* [`cert-manager`](https://github.com/cert-manager/cert-manager/tree/master/internal/webhook) \* [Gatekeeper Open Policy Agent (OPA)](https://open-policy-agent.github.io/gatekeeper/website/docs/mutation) ## ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/admission-webhooks-good-practices.md | main | kubernetes | [
-0.07690557837486267,
0.10119587928056717,
-0.12037079781293869,
-0.01925257034599781,
0.026770394295454025,
-0.09698954224586487,
0.012833506800234318,
0.016229581087827682,
-0.055487118661403656,
-0.04072932153940201,
0.024134019389748573,
-0.08502373099327087,
0.10772093385457993,
-0.02... | 0.102166 |
{{< feature-state feature\_gate\_name="CoordinatedLeaderElection" >}} Kubernetes {{< skew currentVersion >}} includes a beta feature that allows {{< glossary\_tooltip text="control plane" term\_id="control-plane" >}} components to deterministically select a leader via \_coordinated leader election\_. This is useful to ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/coordinated-leader-election.md | main | kubernetes | [
-0.029698463156819344,
-0.0021321591921150684,
0.07408022880554199,
-0.004319776780903339,
0.005855660419911146,
0.027944888919591904,
-0.020325917750597,
-0.08119751513004303,
0.037399813532829285,
0.0793895348906517,
-0.010193348862230778,
-0.04275905713438988,
-0.0012783611891791224,
-0... | 0.056454 |
that Lease expires. Other healthy instances detect the expired Lease and attempt a new election. This mechanism ensures that even though multiple replicas of a component may be running for stability and recovery, \_only one instance actively performs control tasks at a time\_, while the others remain on standby, watchi... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/coordinated-leader-election.md | main | kubernetes | [
-0.029528217390179634,
-0.06802913546562195,
0.01109384000301361,
0.023657722398638725,
0.07969683408737183,
0.03875663876533508,
-0.0174306221306324,
-0.06331750005483627,
0.12103620916604996,
0.025417178869247437,
0.09532441198825836,
0.08599784225225449,
0.027244199067354202,
0.00019386... | 0.125005 |
Networking is a central part of Kubernetes, but it can be challenging to understand exactly how it is expected to work. There are 4 distinct networking problems to address: 1. Highly-coupled container-to-container communications: this is solved by {{< glossary\_tooltip text="Pods" term\_id="pod" >}} and `localhost` com... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/networking.md | main | kubernetes | [
0.04870927333831787,
-0.027689870446920395,
0.08473275601863861,
-0.02438941039144993,
-0.029267357662320137,
-0.00644676573574543,
-0.02390258014202118,
0.011462667025625706,
0.0817096009850502,
0.028553036972880363,
-0.08220052719116211,
0.001254731323570013,
-0.009980384260416031,
-0.03... | 0.23634 |
plans and some on-going efforts that aim to improve Kubernetes networking, please refer to the SIG-Network [KEPs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network). | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/networking.md | main | kubernetes | [
-0.00479326443746686,
-0.0038077165372669697,
0.12143784761428833,
0.0004809279053006321,
-0.05150308459997177,
0.028214020654559135,
-0.034598514437675476,
-0.009161442518234253,
0.0038288806099444628,
0.014040032401680946,
-0.052210986614227295,
0.01819254644215107,
-0.05812447518110275,
... | 0.180221 |
The state of Kubernetes objects in the Kubernetes API can be exposed as metrics. An add-on agent called [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics) can connect to the Kubernetes API server and expose a HTTP endpoint with metrics generated from the state of individual objects in the cluster. I... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/kube-state-metrics.md | main | kubernetes | [
-0.019185353070497513,
0.0025742328725755215,
-0.02674582600593567,
0.03853646665811539,
-0.025020204484462738,
0.012674003839492798,
-0.007019327022135258,
-0.028578653931617737,
0.08478619903326035,
0.041277363896369934,
-0.05363946408033371,
-0.11527872830629349,
-0.011663305573165417,
... | 0.238711 |
System component metrics can give a better look into what is happening inside them. Metrics are particularly useful for building dashboards and alerts. Kubernetes components emit metrics in [Prometheus format](https://prometheus.io/docs/instrumenting/exposition\_formats/). This format is structured plain text, designed... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/system-metrics.md | main | kubernetes | [
-0.022747712209820747,
-0.00475835707038641,
0.015881409868597984,
-0.006384439766407013,
-0.03200007602572441,
-0.06886128336191177,
0.028202136978507042,
-0.030685730278491974,
0.16706663370132446,
0.022806957364082336,
-0.03380497917532921,
-0.0620136559009552,
-0.019403677433729172,
-0... | 0.172299 |
that release. The version is expressed as x.y, where x is the major version, y is the minor version. The patch version is not needed even though a metrics can be deprecated in a patch release, the reason for that is the metrics deprecation policy runs against the minor release. The flag can only take the previous minor... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/system-metrics.md | main | kubernetes | [
0.0033301941584795713,
-0.0005714569706469774,
0.024032341316342354,
-0.03263326361775398,
0.04343370348215103,
0.04194813594222069,
-0.0006802196148782969,
-0.036717429757118225,
0.015089327469468117,
0.010027818381786346,
0.049746204167604446,
0.00910651683807373,
-0.059247687458992004,
... | 0.007389 |
a ClusterRole with the `get` verb for the `/metrics/resources` non-resource URL. On Kubernetes 1.21 you must use the `--show-hidden-metrics-for-version=1.20` flag to expose these alpha stability metrics. ### kubelet Pressure Stall Information (PSI) metrics {{< feature-state feature\_gate\_name="KubeletPSI" >}} When the... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/system-metrics.md | main | kubernetes | [
-0.004127238877117634,
0.019910437986254692,
-0.02213178761303425,
0.05042077228426933,
-0.024277303367853165,
-0.03076491877436638,
0.013246017508208752,
-0.015224539674818516,
0.08830883353948593,
-0.01930168829858303,
-0.05504828691482544,
-0.08853545784950256,
-0.0486159473657608,
-0.0... | 0.208829 |
consumption can be investigated. PSI metrics unlock a more robust way to monitor realitime resource contention at all levels for every cgroup, opening up the opportunity to dynamically handle workloads across the system. You can read more about the PSI metrics in [Understand PSI Metrics](/docs/reference/instrumentation... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/system-metrics.md | main | kubernetes | [
-0.03028671070933342,
0.0045584822073578835,
-0.09392687678337097,
0.061202868819236755,
-0.033130962401628494,
-0.024837827309966087,
-0.006095943972468376,
0.0010743126040324569,
0.0048908633179962635,
-0.0323006696999073,
-0.05943335220217705,
-0.030967004597187042,
-0.07439786195755005,
... | 0.135374 |
In order to run workloads in your cluster, you need {{< glossary\_tooltip text="Nodes" term\_id="node" >}}. Nodes in your cluster can be \_autoscaled\_ - dynamically [\_provisioned\_](#provisioning), or [\_consolidated\_](#consolidation) to provide needed capacity while optimizing cost. Autoscaling is performed by Node... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/node-autoscaling.md | main | kubernetes | [
-0.004501106217503548,
-0.036114830523729324,
0.023538930341601372,
0.08067838102579117,
-0.004300824366509914,
0.010965080931782722,
-0.004799526184797287,
-0.03754241019487381,
-0.014169741421937943,
0.04802984371781349,
-0.013468308374285698,
-0.06494645774364471,
0.021495064720511436,
... | 0.121571 |
cost-effective the cluster is. {{< note >}} Correctly setting the resource requests of your Pods is as important to the overall cost-effectiveness of a cluster as optimizing Node utilization. Combining Node autoscaling with [vertical workload autoscaling](#vertical-workload-autoscaling) can help you achieve this. {{< /... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/node-autoscaling.md | main | kubernetes | [
0.03887953236699104,
0.012217674404382706,
0.035519350320100784,
0.09353583306074142,
0.0038700737059116364,
-0.04221871867775917,
-0.01691466197371483,
0.024825135245919228,
-0.0006258703651838005,
0.05504588037729263,
-0.012520493939518929,
-0.008794039487838745,
-0.001419347943738103,
-... | 0.185159 |
Node groups generally map to some sort of cloud provider resource group (most commonly a Virtual Machine group). A single instance of Cluster Autoscaler can simultaneously manage multiple Node groups. When provisioning, Cluster Autoscaler will add Nodes to the group that best fits the requests of pending Pods. When con... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/node-autoscaling.md | main | kubernetes | [
-0.003697272390127182,
-0.01786939799785614,
0.023130498826503754,
0.07122375071048737,
0.04105496406555176,
-0.0233956016600132,
0.03542397916316986,
-0.01697872206568718,
0.008246629498898983,
0.041971005499362946,
-0.0016551167936995625,
-0.03199441358447075,
-0.022125178948044777,
-0.0... | 0.177465 |
Node for it might not help the Pod actually run. If the requests of a given Pod are too high, it might incorrectly prevent consolidating its Node. [Vertical workload autoscaling](/docs/concepts/workloads/autoscaling#scaling-workloads-vertically) automatically adjusts the resource requests of your Pods based on their hi... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/node-autoscaling.md | main | kubernetes | [
0.01084120199084282,
0.045253630727529526,
0.04450245946645737,
0.046727024018764496,
-0.03917819261550903,
-0.029187260195612907,
-0.04474545270204544,
0.0464504100382328,
-0.0041420492343604565,
0.033660680055618286,
-0.06760218739509583,
0.013363830745220184,
-0.0356002114713192,
-0.029... | 0.134616 |
Application logs can help you understand what is happening inside your application. The logs are particularly useful for debugging problems and monitoring cluster activity. Most modern applications have some kind of logging mechanism. Likewise, container engines are designed to support logging. The easiest and most ado... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/logging.md | main | kubernetes | [
0.07313041388988495,
0.0030048845801502466,
0.062097594141960144,
0.012566030025482178,
0.05260855332016945,
-0.047234270721673965,
-0.00023561896523460746,
0.029974497854709625,
0.060063283890485764,
0.07127180695533752,
-0.06639368832111359,
-0.039375919848680496,
-0.02510121650993824,
0... | 0.179116 |
logs. If a pod is evicted from the node, all corresponding containers are also evicted, along with their logs. The kubelet makes logs available to clients via a special feature of the Kubernetes API. The usual way to access this is by running `kubectl logs`. ### Log rotation {{< feature-state for\_k8s\_version="v1.21" ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/logging.md | main | kubernetes | [
0.10599253326654434,
0.047901589423418045,
0.07745518535375595,
0.022281380370259285,
-0.012802890501916409,
-0.05061422288417816,
-0.03922467678785324,
-0.020438143983483315,
0.09933969378471375,
0.028316274285316467,
-0.020651768893003464,
-0.03295983374118805,
-0.01153744850307703,
-0.0... | 0.108019 |
these logs, several cluster deployment tools set up Windows nodes to log to `C:\var\log\kubelet` instead. If you want to have logs written elsewhere, you can indirectly run the kubelet via a helper tool, `kube-log-runner`, and use that tool to redirect kubelet logs to a directory that you choose. However, by default, k... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/logging.md | main | kubernetes | [
0.09136029332876205,
-0.000925819156691432,
0.034332457929849625,
0.0539548322558403,
-0.005439057480543852,
0.004450446926057339,
-0.011030266992747784,
0.033887796103954315,
0.08878877758979797,
0.06581039726734161,
-0.03428943455219269,
-0.05869723856449127,
-0.021747859194874763,
0.009... | 0.132086 |
to stdout and stderr, but with no agreed format. A node-level agent collects these logs and forwards them for aggregation. ### Using a sidecar container with the logging agent {#sidecar-container-with-logging-agent} You can use a sidecar container in one of the following ways: \* The sidecar container streams applicati... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/logging.md | main | kubernetes | [
0.0349295474588871,
0.038673482835292816,
0.018082736060023308,
0.04742436483502388,
0.010390745475888252,
-0.0005325479432940483,
-0.05090419575572014,
0.010012172162532806,
0.020739376544952393,
-0.026954563334584236,
-0.02140381745994091,
-0.04542052000761032,
-0.005210301373153925,
-0.... | 0.096295 |
policies to the kubelet. #### Sidecar container with a logging agent  If the node-level logging agent is not flexible enough for your situation, you can create a sidecar container with a separate logging agent that ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/logging.md | main | kubernetes | [
0.06469742953777313,
0.0888444185256958,
0.06228388473391533,
0.021324114874005318,
-0.0021400321274995804,
-0.04105761647224426,
-0.0021980449091643095,
-0.008375891484320164,
0.014091506600379944,
0.0339767262339592,
0.007726238574832678,
-0.07771427929401398,
-0.03372824192047119,
0.006... | 0.121635 |
In a Kubernetes cluster, a {{< glossary\_tooltip text="node" term\_id="node" >}} can be shut down in a planned graceful way or unexpectedly because of reasons such as a power outage or something else external. A node shutdown could lead to workload failure if the node is not drained before the shutdown. A node shutdown... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/node-shutdown.md | main | kubernetes | [
0.016632309183478355,
0.06424159556627274,
0.12593434751033783,
0.01941716857254505,
-0.006995938718318939,
-0.030148949474096298,
-0.005437273997813463,
-0.019598834216594696,
0.09870573878288269,
0.07173946499824524,
-0.01346447691321373,
-0.021208506077528,
-0.02298273704946041,
-0.0680... | 0.089728 |
that node and therefore none will start. The kubelet \*\*also\*\* rejects Pods during the `PodAdmission` phase if an ongoing node shutdown has been detected, so that even Pods with a {{< glossary\_tooltip text="toleration" term\_id="toleration" >}} for `node.kubernetes.io/not-ready:NoSchedule` do not start there. When ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/node-shutdown.md | main | kubernetes | [
0.04120177775621414,
0.045588668435811996,
0.07658407092094421,
0.03640443831682205,
0.01107912976294756,
-0.0025667890440672636,
-0.0493447370827198,
-0.06692847609519958,
0.07573001086711884,
0.02367502823472023,
-0.053424984216690063,
-0.0386262945830822,
-0.01488401833921671,
-0.037263... | 0.135936 |
1000 | 120 seconds | | 0 | 60 seconds | The corresponding kubelet config YAML configuration would be: ```yaml shutdownGracePeriodByPodPriority: - priority: 100000 shutdownGracePeriodSeconds: 10 - priority: 10000 shutdownGracePeriodSeconds: 180 - priority: 1000 shutdownGracePeriodSeconds: 120 - priority: 0 shutdownGrace... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/node-shutdown.md | main | kubernetes | [
0.032895252108573914,
0.03345121443271637,
0.007083809468895197,
-0.0074552251026034355,
-0.07891501486301422,
0.028266144916415215,
-0.036612238734960556,
0.014590625651180744,
0.05134062469005585,
0.01565692201256752,
0.017513101920485497,
-0.05108613148331642,
-0.028952645137906075,
-0.... | 0.145898 |
`node.kubernetes.io/out-of-service` with either `NoExecute` or `NoSchedule` effect to a Node marking it out-of-service. If a Node is marked out-of-service with this taint, the pods on the node will be forcefully deleted if there are no matching tolerations on it and volume detach operations for the pods terminating on ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/node-shutdown.md | main | kubernetes | [
0.033640965819358826,
0.05486121028661728,
0.098892442882061,
0.0179919321089983,
0.06415645778179169,
-0.03201574459671974,
0.0004114836046937853,
-0.06410668790340424,
0.09198679029941559,
0.05653984099626541,
-0.012024528346955776,
0.04506893455982208,
-0.01800573244690895,
-0.031200973... | 0.156191 |
In Kubernetes, observability is the process of collecting and analyzing metrics, logs, and traces—often referred to as the three pillars of observability—in order to obtain a better understanding of the internal state, performance, and health of the cluster. Kubernetes control plane components, as well as many add-ons,... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/observability.md | main | kubernetes | [
0.007982481271028519,
-0.04428042471408844,
0.01217363215982914,
0.005678415298461914,
0.020589198917150497,
-0.002341496990993619,
-0.009273560717701912,
-0.04515764117240906,
0.07822932302951813,
0.022383086383342743,
-0.022729787975549698,
-0.07990945875644684,
-0.02270881086587906,
-0.... | 0.229865 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.