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 |
|---|---|---|---|---|---|
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 |
In order to support latency-critical and high-throughput workloads, Kubernetes offers a suite of Resource Managers. The managers aim to co-ordinate and optimise the alignment of node's resources for pods configured with a specific requirement for CPUs, devices, and memory (hugepages) resources. ## Hardware topology ali... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/policy/node-resource-managers.md | main | kubernetes | [
0.05404923856258392,
-0.024555742740631104,
0.006559279747307301,
0.011089924722909927,
-0.04201142117381096,
-0.02643747813999653,
-0.025925887748599052,
-0.0412735715508461,
0.09194868057966232,
0.0279656033962965,
-0.0489441379904747,
-0.032549191266298294,
-0.02473045140504837,
-0.0863... | 0.226856 |
and placed in the cpuset for the container. CFS quota is not used to bound the CPU usage of these containers as their usage is bound by the scheduling domain itself. In others words, the number of CPUs in the container cpuset is equal to the integer CPU `limit` specified in the pod spec. This static assignment increase... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/policy/node-resource-managers.md | main | kubernetes | [
-0.005953097715973854,
0.04624499753117561,
-0.027967995032668114,
0.01850525476038456,
0.04207473248243332,
-0.04637285694479942,
0.03283026069402695,
0.01534847542643547,
0.07416132092475891,
-0.015656176954507828,
-0.026440121233463287,
0.008043563924729824,
-0.024305203929543495,
0.003... | 0.196665 |
maturity level using the following feature gates: \* `CPUManagerPolicyBetaOptions` (default enabled). Disable to hide beta-level options. \* `CPUManagerPolicyAlphaOptions` (default disabled). Enable to show alpha-level options. You will still have to enable each option using the `cpuManagerPolicyOptions` field in the k... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/policy/node-resource-managers.md | main | kubernetes | [
0.03002764843404293,
0.007986941374838352,
0.02439105696976185,
0.011996014043688774,
-0.006720082368701696,
-0.028872353956103325,
-0.0431889146566391,
-0.03821057453751564,
-0.004737297538667917,
0.02214605174958706,
0.00727153429761529,
-0.047916751354932785,
-0.051538240164518356,
-0.0... | 0.104561 |
to note that this strategy might be less effective when the system is heavily loaded. Under such conditions, the benefit of reducing contention diminishes. Conversely, default behavior can help in reducing inter-core communication overhead, potentially providing better performance under high load conditions. ##### `str... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/policy/node-resource-managers.md | main | kubernetes | [
0.023785315454006195,
0.04634498432278633,
0.027660774067044258,
0.03776039183139801,
-0.0329337976872921,
0.01142036635428667,
-0.01928284950554371,
0.011458457447588444,
0.1166425570845604,
0.010078282095491886,
-0.03445259854197502,
-0.04445631057024002,
-0.0266256146132946,
-0.09279359... | 0.191586 |
{{< 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 for\_k8s\_version="v1.34" state="beta" >}} As... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/system-metrics.md | main | kubernetes | [
0.0191586185246706,
0.013065081089735031,
-0.013477301225066185,
0.05365779623389244,
-0.019561437889933586,
-0.011368341743946075,
0.009014077484607697,
-0.012263360433280468,
0.07831578701734543,
-0.030720287933945656,
-0.049739062786102295,
-0.09426254779100418,
-0.04604566842317581,
-0... | 0.182175 |
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.03780701011419296,
0.05554505065083504,
0.10802757740020752,
0.04688433185219765,
-0.01686350628733635,
-0.02371012419462204,
-0.02259250544011593,
-0.04084815829992294,
0.09499695897102356,
0.02411526069045067,
-0.04814794659614563,
0.014450010843575,
-0.029809532687067986,
-0.039369735... | 0.189703 |
the node. The graceful node shutdown feature is configured with two [`KubeletConfiguration`](/docs/tasks/administer-cluster/kubelet-config-file/) options: - `shutdownGracePeriod`: Specifies the total duration that the node should delay the shutdown by. This is the total grace period for pod termination for both regular... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/node-shutdown.md | main | kubernetes | [
0.032259903848171234,
0.047922391444444656,
0.08609181642532349,
0.055072393268346786,
0.023943452164530754,
-0.0013762576272711158,
-0.07145556062459946,
-0.00219089281745255,
0.06998952478170395,
0.07413895428180695,
-0.0320216566324234,
0.012091174721717834,
-0.038819488137960434,
-0.03... | 0.184795 |
get 120 seconds to shut down. Finally, all other pods will get 60 seconds to shut down. One doesn't have to specify values corresponding to all of the classes. For example, you could instead use these settings: | Pod priority class value | Shutdown period | | ------------------------ | --------------- | | 100000 | 300 ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/node-shutdown.md | main | kubernetes | [
0.024070682004094124,
0.04631830006837845,
0.05518294870853424,
-0.008361442014575005,
-0.07611869275569916,
0.05190674960613251,
-0.04489189386367798,
-0.016011841595172882,
0.08708833903074265,
0.04922070354223251,
-0.020242657512426376,
-0.03181929513812065,
-0.058777738362550735,
-0.04... | 0.083613 |
matching `out-of-service` tolerations. 1. Immediately perform detach volume operation for such pods. {{< note >}} - Before adding the taint `node.kubernetes.io/out-of-service`, it should be verified that the node is already in shutdown or power off state (not in the middle of restarting). - The user is required to manu... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/node-shutdown.md | main | kubernetes | [
0.0005279184551909566,
0.0549805611371994,
0.08725173026323318,
0.029335992410779,
0.04723621532320976,
-0.0187209602445364,
0.01792796701192856,
-0.02751694805920124,
0.0780952200293541,
0.07595718652009964,
0.011347910389304161,
0.047226157039403915,
0.007185736671090126,
0.0195399355143... | 0.156185 |
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 |
central log store. The [logging architecture guidance](/docs/concepts/cluster-administration/logging/) explains how to design such pipelines, apply retention, and log flows to backends. Figure 3 outlines a common log aggregation pipeline. {{< mermaid >}} flowchart LR subgraph Sources A[Application stdout / stderr] B[Co... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/observability.md | main | kubernetes | [
0.036999866366386414,
-0.006375713273882866,
0.011724348179996014,
0.014822346158325672,
0.03348616510629654,
-0.02885151095688343,
-0.0033713786397129297,
-0.0077064428478479385,
0.07161088287830353,
0.04314691945910454,
-0.027332769706845284,
-0.04162205010652542,
-0.005606313701719046,
... | 0.190229 |
{{< feature-state for\_k8s\_version="v1.27" state="beta" >}} System component traces record the latency of and relationships between operations in the cluster. Kubernetes components emit traces using the [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otlp/) with the gRPC exporter and can be collected and ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/system-traces.md | main | kubernetes | [
0.04239460453391075,
-0.03875475004315376,
-0.00995351281017065,
0.05478626862168312,
-0.006598426960408688,
-0.04981396719813347,
0.009589994326233864,
-0.03429456800222397,
0.06568654626607895,
-0.002838902175426483,
-0.015978172421455383,
-0.09527306258678436,
-0.08133389800786972,
-0.0... | 0.193806 |
requests so that container runtimes with trace instrumentation, such as CRI-O and containerd, can associate their exported spans with the trace context from the kubelet. The resulting traces will have parent-child links between kubelet and container runtime spans, providing helpful context when debugging node issues. P... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/system-traces.md | main | kubernetes | [
-0.008195462636649609,
0.039890676736831665,
0.04866749048233032,
0.034045349806547165,
0.024954630061984062,
-0.08496595919132233,
-0.047306422144174576,
-0.01988108642399311,
0.009048903360962868,
-0.056295279413461685,
-0.02667861245572567,
-0.10401687771081924,
-0.05360892042517662,
-0... | 0.112277 |
{{< feature-state state="stable" for\_k8s\_version="v1.29" >}} Controlling the behavior of the Kubernetes API server in an overload situation is a key task for cluster administrators. The {{< glossary\_tooltip term\_id="kube-apiserver" text="kube-apiserver" >}} has some controls available (i.e. the `--max-requests-infl... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/flow-control.md | main | kubernetes | [
-0.020449478179216385,
0.019976023584604263,
0.07385524362325668,
-0.01483129058033228,
-0.0368318073451519,
-0.02060418762266636,
0.016818402335047722,
-0.041406597942113876,
0.060196150094270706,
0.11206693202257156,
-0.0570090152323246,
-0.0012412626529112458,
-0.023580852895975113,
-0.... | 0.175453 |
level, and the subsidiary controlled requests are classified to higher priority levels, this is one possible solution. When the original requests can belong to any priority level, the subsidiary controlled requests have to be exempt from Priority and Fairness limitation. One way to do that is with the objects that conf... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/flow-control.md | main | kubernetes | [
-0.04837249591946602,
-0.01608189195394516,
0.04732135683298111,
-0.07516082376241684,
-0.07478426396846771,
-0.046656299382448196,
-0.016628604382276535,
-0.07403810322284698,
0.05476624146103859,
0.06255412846803665,
-0.08244900405406952,
-0.045994535088539124,
0.01468967366963625,
-0.02... | 0.089763 |
its seat. Depending on request parameters, the response to a \*\*watch\*\* request may or may not begin with \*\*create\*\* notifications for all the relevant pre-existing objects. API Priority and Fairness considers a \*\*watch\*\* request to be done with its seat once that initial burst of notifications, if any, is o... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/flow-control.md | main | kubernetes | [
-0.07041960209608078,
-0.01855553686618805,
0.08065502345561981,
0.011678666807711124,
-0.009685165248811245,
-0.05445697903633118,
0.07063756138086319,
-0.016690293326973915,
0.15425245463848114,
0.09969537705183029,
-0.07544080168008804,
-0.004746738355606794,
0.024209890514612198,
-0.04... | 0.233661 |
cluster administrator to scale up or down the total amount of traffic to a server by restarting `kube-apiserver` with a different value for `--max-requests-inflight` (or `--max-mutating-requests-inflight`), and all PriorityLevelConfigurations will see their maximum allowed concurrency go up (or down) by the same fracti... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/flow-control.md | main | kubernetes | [
0.012042508460581303,
-0.06727916747331619,
0.008674423210322857,
-0.0391169935464859,
-0.08615630865097046,
0.02963223308324814,
-0.029702844098210335,
0.007633151486515999,
0.07268203794956207,
0.08976643532514572,
-0.007098977919667959,
-0.01376433577388525,
0.02655327506363392,
-0.0012... | 0.07896 |
showing an interesting collection of shuffle sharding configurations, showing for each the probability that a given mouse (low-intensity flow) is squished by the elephants (high-intensity flows) for an illustrative collection of numbers of elephants. See https://play.golang.org/p/Gi0PLgVHiUg , which computes this table... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/flow-control.md | main | kubernetes | [
0.009861105121672153,
0.004081215709447861,
0.04860716313123703,
-0.016587989404797554,
-0.06077481806278229,
-0.010378805920481682,
0.08122807741165161,
-0.05998590588569641,
0.013325667008757591,
0.001721867360174656,
-0.015477070584893227,
-0.05751229077577591,
0.025860756635665894,
0.0... | 0.043609 |
subject to flow control at all: they will always be dispatched immediately. The mandatory `exempt` FlowSchema classifies all requests from the `system:masters` group into this priority level. You may define other FlowSchemas that direct other requests to this priority level, if appropriate. \* The mandatory `catch-all`... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/flow-control.md | main | kubernetes | [
-0.025121424347162247,
-0.028608741238713264,
-0.00878864899277687,
-0.00648596603423357,
0.00007868016109568998,
-0.04099133238196373,
0.008200340904295444,
-0.05193939805030823,
-0.0013799667358398438,
0.05042337626218796,
-0.011596530675888062,
-0.02192540653049946,
-0.06593909114599228,
... | 0.078528 |
version of the `kube-apiserver` is rolled out, albeit potentially with thrashing while there is a mixed population of servers. Maintenance of a suggested configuration object consists of creating it --- with the server's suggested spec --- if the object does not exist. OTOH, if the object already exists, maintenance be... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/flow-control.md | main | kubernetes | [
-0.03132990002632141,
0.028088990598917007,
0.025543374940752983,
0.01589195244014263,
-0.016005156561732292,
-0.04178043082356453,
0.026096655055880547,
-0.06068192049860954,
0.06966549158096313,
0.1067991778254509,
-0.03798384964466095,
-0.04885849356651306,
-0.027600696310400963,
-0.084... | 0.20219 |
than queue excess requests. \* `time-out`, indicating that the request was still in the queue when its queuing time limit expired. \* `cancelled`, indicating that the request is not purge locked and has been ejected from the queue. \* `apiserver\_flowcontrol\_dispatched\_requests\_total` is a counter vector (cumulative... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/flow-control.md | main | kubernetes | [
-0.0878056064248085,
-0.012147439643740654,
-0.05018456280231476,
0.05542892590165138,
-0.007774305529892445,
-0.044557325541973114,
0.024806521832942963,
-0.052854858338832855,
0.06765136867761612,
0.028764469549059868,
-0.00816640816628933,
0.0058141532354056835,
0.0064545865170657635,
-... | 0.223577 |
a write to cover for the corresponding notification work) of all requests except WATCHes; for those it considers only the initial stage that delivers notifications of pre-existing objects. Each histogram in the vector is also labeled with `phase: executing` (there is no seat limit for the waiting phase). \* `apiserver\... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/flow-control.md | main | kubernetes | [
-0.057554442435503006,
0.01501454971730709,
-0.014234945178031921,
0.03316860273480415,
0.005752516444772482,
-0.06072135642170906,
0.04918704926967621,
-0.041410475969314575,
0.10793016105890274,
0.039554063230752945,
-0.07470406591892242,
-0.05278177186846733,
0.024708282202482224,
-0.08... | 0.211489 |
a request being dispatched but did not, due to lack of available concurrency, broken down by `flow\_schema` and `priority\_level`. \* `apiserver\_flowcontrol\_epoch\_advance\_total` is a counter vector of the number of attempts to jump a priority level's progress meter backward to avoid numeric overflow, grouped by `pr... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/flow-control.md | main | kubernetes | [
-0.022425197064876556,
-0.05513906106352806,
0.020440666005015373,
-0.016791261732578278,
-0.03120661899447441,
-0.07826604694128036,
-0.0762958973646164,
-0.083005391061306,
0.0952414721250534,
0.09739502519369125,
-0.026956887915730476,
-0.03144700080156326,
-0.01360828522592783,
0.01122... | -0.028261 |
If possible, the number of seats available across all priority levels for a particular `kube-apiserver` can be increased by increasing the values for the `max-requests-inflight` and `max-mutating-requests-inflight` flags. Alternatively, horizontally scaling the number of `kube-apiserver` instances will increase the tot... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/flow-control.md | main | kubernetes | [
0.009921629913151264,
-0.06965576112270355,
0.003402477828785777,
-0.06337212026119232,
-0.10576772689819336,
-0.019893212243914604,
-0.04343344643712044,
-0.03478756546974182,
0.053531914949417114,
0.08232782036066055,
-0.0594789981842041,
-0.06582317501306534,
-0.00022851834364701062,
-0... | 0.085638 |
System component logs record events happening in cluster, which can be very useful for debugging. You can configure log verbosity to see more or less detail. Logs can be as coarse-grained as showing errors within a component, or as fine-grained as showing step-by-step traces of events (like HTTP access logs, pod state ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/system-logs.md | main | kubernetes | [
0.039205700159072876,
0.020686941221356392,
0.059137579053640366,
0.04191473498940468,
0.03875146806240082,
-0.03303243964910507,
0.03853433206677437,
-0.02698606438934803,
0.06385532766580582,
0.06403690576553345,
-0.042932428419589996,
-0.06541899591684341,
0.0162638071924448,
-0.0118758... | 0.174449 |
line [depending on the data](https://github.com/kubernetes/kubernetes/issues/106428). ``` I1025 00:15:15.525108 1 example.go:116] "Example" data="This is text with a line break\nand \"quotation marks\"." someInt=1 someFloat=0.1 someStruct={StringField: First line, second line.} ``` ### Contextual Logging {{< feature-st... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/system-logs.md | main | kubernetes | [
-0.008938915096223354,
0.05425256863236427,
0.11501137167215347,
-0.0004421605553943664,
-0.003951121121644974,
-0.026135750114917755,
0.0718739926815033,
0.015623241662979126,
0.08497346937656403,
0.029910018667578697,
-0.03790384531021118,
-0.10642867535352707,
-0.007556526456028223,
0.0... | 0.162457 |
a container. For example: \* The Kubernetes scheduler and kube-proxy run in a container. \* The kubelet and {{}} do not run in containers. On machines with systemd, the kubelet and container runtime write to journald. Otherwise, they write to `.log` files in the `/var/log` directory. System components inside containers... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/system-logs.md | main | kubernetes | [
0.05544699355959892,
0.018081247806549072,
0.019425611943006516,
0.017087258398532867,
0.028778498992323875,
-0.05995369702577591,
-0.020388413220643997,
-0.009541175328195095,
0.09846780449151993,
0.0929437130689621,
-0.016301000490784645,
0.04061621055006981,
-0.00937408022582531,
-0.031... | 0.101132 |
{{% thirdparty-content %}} Add-ons extend the functionality of Kubernetes. This page lists some of the available add-ons and links to their respective installation instructions. The list does not try to be exhaustive. ## Networking and Network Policy \* [ACI](https://www.github.com/noironetworks/aci-containers) provide... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/addons.md | main | kubernetes | [
-0.009927945211529732,
-0.009221131913363934,
-0.03684476763010025,
-0.006658402271568775,
0.01064317487180233,
0.009590556845068932,
0.006811989936977625,
-0.019357237964868546,
0.005477186292409897,
-0.016306094825267792,
-0.02451389469206333,
-0.05505085363984108,
-0.08273474872112274,
... | 0.253605 |
provide cloud native based Service function chaining(SFC). \* [NSX-T](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/index.html) Container Plug-in (NCP) provides integration between VMware NSX-T and container orchestrators such as Kubernetes, as well as integration between NSX-T and container-based CaaS/PaaS platf... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/addons.md | main | kubernetes | [
-0.0707707405090332,
0.0012235528556630015,
0.012768256478011608,
-0.049121350049972534,
0.0303040761500597,
0.0375654436647892,
-0.009534514509141445,
0.009727555327117443,
0.03298021852970123,
0.07487650215625763,
-0.028490735217928886,
-0.005349662154912949,
-0.05561283230781555,
-0.012... | 0.341312 |
The cluster administration overview is for anyone creating or administering a Kubernetes cluster. It assumes some familiarity with core Kubernetes [concepts](/docs/concepts/). ## Planning a cluster See the guides in [Setup](/docs/setup/) for examples of how to plan, set up, and configure Kubernetes clusters. The soluti... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/_index.md | main | kubernetes | [
0.022568481042981148,
-0.06485623121261597,
0.03666147217154503,
-0.007866906933486462,
-0.039742134511470795,
0.049020469188690186,
-0.030870508402585983,
0.03885012865066528,
-0.003829609602689743,
0.057232312858104706,
-0.0401008315384388,
-0.06317170709371567,
-0.013724555261433125,
-0... | 0.171211 |
Since release v1.32, we introduced configurable version compatibility and emulation options to Kubernetes control plane components to make upgrades safer by providing more control and increasing the granularity of steps available to cluster administrators. ## Emulated Version The emulation option is set by the `--emula... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/cluster-administration/compatibility-version.md | main | kubernetes | [
0.04390259087085724,
-0.02428428828716278,
0.06447262316942215,
-0.03222138062119484,
0.04571005329489708,
0.0032971063628792763,
-0.06420700997114182,
-0.053485844284296036,
0.0018883916782215238,
0.019586855545639992,
-0.0025844285264611244,
-0.04691092297434807,
0.022405045107007027,
-0... | 0.130414 |
This tutorial shows you how to run a sample app on Kubernetes using minikube. The tutorial provides a container image that uses NGINX to echo back all the requests. ## {{% heading "objectives" %}} \* Deploy a sample application to minikube. \* Run the app. \* View application logs. ## {{% heading "prerequisites" %}} Th... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/hello-minikube.md | main | kubernetes | [
0.01731846109032631,
0.058221034705638885,
0.02022448740899563,
-0.023290935903787613,
-0.010459482669830322,
0.0232338048517704,
-0.07710320502519608,
0.08635837584733963,
0.008156074211001396,
0.026639442890882492,
-0.07180413603782654,
-0.057238832116127014,
0.023571902886033058,
-0.047... | 0.03738 |
webserver kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.53 -- /agnhost netexec --http-port=8080 ``` 1. View the Deployment: ```shell kubectl get deployments ``` The output is similar to: ``` NAME READY UP-TO-DATE AVAILABLE AGE hello-node 1/1 1 1 1m ``` (It may take some time for... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/hello-minikube.md | main | kubernetes | [
0.0676581934094429,
-0.009622993879020214,
0.04374634847044945,
0.010220440104603767,
-0.012913552112877369,
-0.04894942045211792,
-0.06944358348846436,
0.005539574194699526,
0.04546782746911049,
0.08748724311590195,
0.04281546175479889,
-0.132842019200325,
-0.03451940417289734,
-0.0452845... | 0.124827 |
by installing that addon: ```shell kubectl get pod,svc -n kube-system ``` The output is similar to: ``` NAME READY STATUS RESTARTS AGE pod/coredns-5644d7b6d9-mh9ll 1/1 Running 0 34m pod/coredns-5644d7b6d9-pqd2t 1/1 Running 0 34m pod/metrics-server-67fb648c5 1/1 Running 0 26s pod/etcd-minikube 1/1 Running 0 34m pod/infl... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/hello-minikube.md | main | kubernetes | [
0.009314549155533314,
-0.039053622633218765,
-0.05792387202382088,
-0.001483311876654625,
-0.017300378531217575,
0.0027490316424518824,
-0.06812120974063873,
-0.010226214304566383,
0.07712946087121964,
0.07168056815862656,
0.01837518811225891,
-0.04386183246970177,
-0.0817219614982605,
-0.... | 0.13938 |
This section of the Kubernetes documentation contains tutorials. A tutorial shows how to accomplish a goal that is larger than a single [task](/docs/tasks/). Typically a tutorial has several sections, each of which has a sequence of steps. Before walking through each tutorial, you may want to bookmark the [Standardized... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/_index.md | main | kubernetes | [
0.004703354090452194,
-0.03436261788010597,
0.03820551559329033,
-0.007855864241719246,
-0.051711395382881165,
-0.016336645931005478,
-0.013392040506005287,
0.048384420573711395,
-0.0045189750380814075,
0.046205323189496994,
-0.022888803854584694,
-0.027670273557305336,
0.004235376138240099,... | 0.151179 |
This section is relevant for people adopting a new built-in [sidecar containers](/docs/concepts/workloads/pods/sidecar-containers/) feature for their workloads. Sidecar container is not a new concept as posted in the [blog post](/blog/2015/06/the-distributed-system-toolkit-patterns/). Kubernetes allows running multiple... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/configuration/pod-sidecar-containers.md | main | kubernetes | [
0.039293043315410614,
0.03559015691280365,
0.06257530301809311,
0.055772166699171066,
0.02599000371992588,
0.00767988245934248,
-0.053867828100919724,
-0.029012901708483696,
-0.08371267467737198,
0.01924312673509121,
-0.024521391838788986,
-0.012872292660176754,
-0.03352731466293335,
0.008... | 0.080174 |
on initialization. However, it is often unclear what caused the problem. Here are the considerations and troubleshooting steps that one can take while adopting sidecar containers for their workload. ### Ensure the feature gate is enabled As a very first step, make sure that both API server and Nodes are at Kubernetes v... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/configuration/pod-sidecar-containers.md | main | kubernetes | [
0.05757439136505127,
0.04317620024085045,
0.11642178148031235,
0.04920070245862007,
0.021486608311533928,
0.008934669196605682,
-0.07681787014007568,
-0.051429834216833115,
-0.017534157261252403,
0.04081819951534271,
0.00024936837144196033,
-0.013676795177161694,
-0.028526578098535538,
0.0... | -0.014859 |
landing on those nodes. 1. Check Nodes compatibility on injection. During sidecar injection, you may use the following strategies to check node compatibility: - query node version and assume the feature gate is enabled on the version 1.29+ - query node prometheus metrics and check feature enablement status - assume the... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/configuration/pod-sidecar-containers.md | main | kubernetes | [
-0.012385313399136066,
0.04161494970321655,
0.039550215005874634,
0.02733631432056427,
0.05986049026250839,
-0.06958204507827759,
-0.09913183748722076,
-0.044087670743465424,
-0.14466527104377747,
-0.03901388496160507,
0.01829787716269493,
-0.051518093794584274,
-0.016718951985239983,
0.00... | 0.07065 |
This page provides a step-by-step example of updating configuration within a Pod via a ConfigMap and builds upon the [Configure a Pod to Use a ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/) task. At the end of this tutorial, you will understand how to change the configuration for a running app... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/configuration/updating-configuration-via-a-configmap.md | main | kubernetes | [
0.021312672644853592,
-0.004178306553512812,
0.018395015969872475,
0.006265217904001474,
-0.015336725860834122,
-0.04953588917851448,
-0.06954348832368851,
0.02340572699904442,
-0.04909810423851013,
0.11216431856155396,
-0.06875470280647278,
-0.018280964344739914,
0.0280796829611063,
-0.01... | 0.07973 |
one of the pods that belongs to this Deployment: ```shell kubectl logs deployments/configmap-volume --follow ``` After few seconds, you should see the log output change as follows: ``` Thu Jan 4 14:11:36 UTC 2024 My preferred sport is football Thu Jan 4 14:11:46 UTC 2024 My preferred sport is football Thu Jan 4 14:11:5... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/configuration/updating-configuration-via-a-configmap.md | main | kubernetes | [
0.07083563506603241,
-0.01694737933576107,
0.0510840006172657,
-0.01667792536318302,
0.05206407234072685,
-0.061059579253196716,
-0.05276304483413696,
0.00463462108746171,
0.1100086197257042,
0.08786560595035553,
-0.007514092605561018,
-0.06253647804260254,
0.0009164253133349121,
-0.050744... | 0.171115 |
of apples Thu Jan 4 16:13:06 UTC 2024 The basket is full of apples Thu Jan 4 16:13:16 UTC 2024 The basket is full of apples Thu Jan 4 16:13:26 UTC 2024 The basket is full of apples ``` {{< note >}} Although the value of the key inside the ConfigMap has changed, the environment variable in the Pod still shows the earlie... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/configuration/updating-configuration-via-a-configmap.md | main | kubernetes | [
0.06949646025896072,
-0.019348127767443657,
0.07371097058057785,
-0.009837078861892223,
0.01295323483645916,
-0.049420151859521866,
-0.02021949551999569,
-0.026291949674487114,
0.031228292733430862,
0.0480816587805748,
0.05861957371234894,
-0.06941235810518265,
0.019864466041326523,
-0.100... | 0.110677 |
container serves the HTML via HTTP. {{% code\_sample file="deployments/deployment-with-configmap-two-containers.yaml" %}} Create the Deployment: ```shell kubectl apply -f https://k8s.io/examples/deployments/deployment-with-configmap-two-containers.yaml ``` Check the pods for this Deployment to ensure they are ready (ma... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/configuration/updating-configuration-via-a-configmap.md | main | kubernetes | [
0.018218232318758965,
0.02192177064716816,
0.07191134989261627,
-0.0014411179581657052,
-0.025377461686730385,
-0.05530213192105293,
0.0015200208872556686,
-0.03926869109272957,
0.02889299765229225,
0.03969913721084595,
0.0018426553579047322,
-0.13090786337852478,
0.015343322418630123,
-0.... | 0.05997 |
Sidecar Container writes a file in HTML that has its content based on a ConfigMap. The web server container serves the HTML via HTTP. {{% code\_sample file="deployments/deployment-with-configmap-and-sidecar-container.yaml" %}} Create the Deployment: ```shell kubectl apply -f https://k8s.io/examples/deployments/deployme... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/configuration/updating-configuration-via-a-configmap.md | main | kubernetes | [
0.010242336429655552,
0.03972792625427246,
0.05221619829535484,
0.02130243368446827,
0.00011447988072177395,
-0.03232221305370331,
0.00874950923025608,
-0.058095116168260574,
-0.010485596023499966,
0.030124157667160034,
0.07222922891378403,
-0.08666594326496124,
-0.03563934564590454,
-0.06... | 0.061055 |
pods for this Deployment to ensure they are ready (matching by {{< glossary\_tooltip text="selector" term\_id="selector" >}}): ```shell kubectl get pods --selector=app.kubernetes.io/name=immutable-configmap-volume ``` You should see an output similar to: ``` NAME READY STATUS RESTARTS AGE immutable-configmap-volume-78b... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/configuration/updating-configuration-via-a-configmap.md | main | kubernetes | [
0.03214607015252113,
-0.01438036747276783,
0.06564964354038239,
-0.005132684949785471,
-0.0015785866416990757,
-0.03525257483124733,
0.03009023331105709,
-0.009831377305090427,
0.012272242456674576,
0.044170837849378586,
0.03575041890144348,
-0.09507907181978226,
0.009203223511576653,
-0.0... | 0.155138 |
ConfigMap, it is advised to delete the old one. ```shell kubectl delete configmap company-name-20150801 ``` ## Summary Changes to a ConfigMap mounted as a Volume on a Pod are available seamlessly after the subsequent kubelet sync. Changes to a ConfigMap that configures environment variables for a Pod are available afte... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/configuration/updating-configuration-via-a-configmap.md | main | kubernetes | [
0.03024832345545292,
0.04068386182188988,
0.055146899074316025,
-0.043946925550699234,
-0.010529923252761364,
-0.06970266252756119,
0.0052721803076565266,
-0.04978061839938164,
0.03439394012093544,
0.02858636900782585,
0.03535747900605202,
-0.047402311116456985,
0.03592236712574959,
-0.045... | 0.095321 |
This page provides a real world example of how to configure Redis using a ConfigMap and builds upon the [Configure a Pod to Use a ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/) task. ## {{% heading "objectives" %}} \* Create a ConfigMap with Redis configuration values \* Create a Redis Pod tha... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/configuration/configure-redis-using-configmap.md | main | kubernetes | [
0.011426904238760471,
-0.0329350009560585,
-0.010101724416017532,
-0.005308111198246479,
0.03018423728644848,
-0.05315369740128517,
0.02355807088315487,
-0.003993283491581678,
-0.02409261278808117,
0.032967254519462585,
0.0050856624729931355,
-0.04667351767420769,
0.03811115771532059,
-0.0... | 0.146137 |
configuration values one last time: ```shell kubectl exec -it pod/redis -- redis-cli ``` Check `maxmemory`: ```shell 127.0.0.1:6379> CONFIG GET maxmemory ``` It should now return the updated value of 2097152: ```shell 1) "maxmemory" 2) "2097152" ``` Similarly, `maxmemory-policy` has also been updated: ```shell 127.0.0.... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/configuration/configure-redis-using-configmap.md | main | kubernetes | [
0.05859634652733803,
-0.002316736849024892,
-0.042423319071531296,
-0.03399048000574112,
-0.017850643023848534,
-0.06824379414319992,
0.024388829246163368,
0.03381805494427681,
0.023520158603787422,
0.047738008201122284,
0.014536597765982151,
-0.06013351306319237,
0.03289775922894478,
-0.0... | 0.104463 |
{{< feature-state feature\_gate\_name="AppArmor" >}} This page shows you how to load AppArmor profiles on your nodes and enforce those profiles in Pods. To learn more about how Kubernetes can confine Pods using AppArmor, see [Linux kernel security constraints for Pods and containers](/docs/concepts/security/linux-kerne... | https://github.com/kubernetes/website/blob/main//content/en/docs/tutorials/security/apparmor.md | main | kubernetes | [
0.04125595465302467,
0.02559712715446949,
0.05004219710826874,
-0.029389282688498497,
0.04061996564269066,
-0.015221339650452137,
0.012520890682935715,
0.05466856807470322,
-0.03275103121995926,
0.006540813948959112,
0.0031509161926805973,
-0.08580095320940018,
0.02607370726764202,
0.01405... | 0.172345 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.