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 |
|---|---|---|---|---|---|
- schedulerName: my-scheduler plugins: # Disable specific plugins for different extension points # You can disable all plugins for an extension point using "\*" queueSort: disabled: - name: "\*" # Disable all queueSort plugins # - name: "PrioritySort" # Disable specific queueSort plugin filter: disabled: - name: "\*" #... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/security/hardening-guide/scheduler.md | main | kubernetes | [
-0.02254214696586132,
0.014186852611601353,
0.0006705168634653091,
0.05507379397749901,
-0.01347291748970747,
0.01386305969208479,
0.003242564620450139,
-0.04669240489602089,
0.01440941821783781,
-0.0010286722099408507,
-0.04721330106258392,
-0.04706563428044319,
-0.04742247238755226,
-0.0... | 0.132727 |
Selecting the appropriate authentication mechanism(s) is a crucial aspect of securing your cluster. Kubernetes provides several built-in mechanisms, each with its own strengths and weaknesses that should be carefully considered when choosing the best authentication mechanism for your cluster. In general, it is recommen... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/security/hardening-guide/authentication-mechanisms.md | main | kubernetes | [
0.023637831211090088,
0.04256119951605797,
-0.005084216594696045,
-0.02494928054511547,
-0.009596058167517185,
0.02773718722164631,
0.09838748723268509,
-0.0019464220385998487,
0.1124722957611084,
0.02220795676112175,
-0.0662262886762619,
-0.0848710760474205,
0.0017225928604602814,
0.01030... | 0.081015 |
tokens that can be guessed by an attacker, which can be a security risk. - There is no lockout mechanism available to prevent brute-force attacks, making it easier for attackers to guess or crack the token. ## ServiceAccount secret tokens {#serviceaccount-secret-tokens} [Service account secrets](/docs/reference/access-... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/security/hardening-guide/authentication-mechanisms.md | main | kubernetes | [
-0.09080354124307632,
-0.0007507398258894682,
0.018389444798231125,
-0.006294194143265486,
-0.028989722952246666,
0.07952981442213058,
0.07366668432950974,
-0.027452640235424042,
0.13657502830028534,
0.052692823112010956,
-0.03958375006914139,
0.005435253493487835,
0.017141642048954964,
-0... | 0.185583 |
mitigate the risk of traffic interception or sniffing attacks. This ensures that the communication between the proxy and Kubernetes API server is secure. Secondly, it is important to be aware that an attacker who is able to modify the headers of the request may be able to gain unauthorized access to Kubernetes resource... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/security/hardening-guide/authentication-mechanisms.md | main | kubernetes | [
-0.11818590760231018,
0.15316501259803772,
0.014493144117295742,
-0.021805280819535255,
-0.0038653830997645855,
0.0005091797793284059,
0.07295111566781998,
0.023446382954716682,
0.06816504150629044,
0.003183589782565832,
-0.058274246752262115,
0.005557720083743334,
0.062096547335386276,
0.... | 0.123805 |
{{< feature-state feature\_gate\_name="NodeDeclaredFeatures" >}} Kubernetes nodes use \_declared features\_ to report the availability of specific features that are new or feature-gated. Control plane components utilize this information to make better decisions. The kube-scheduler, via the `NodeDeclaredFeatures` plugin... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/node-declared-features.md | main | kubernetes | [
0.04486239328980446,
-0.02713836170732975,
0.05086081475019455,
0.049683451652526855,
0.0768217071890831,
0.0038775536231696606,
-0.029908543452620506,
-0.0631011575460434,
0.03282120078802109,
0.019685814157128334,
0.00645419443026185,
-0.029676465317606926,
-0.0215290579944849,
-0.050315... | 0.17408 |
You can constrain a {{< glossary\_tooltip text="Pod" term\_id="pod" >}} so that it is \_restricted\_ to run on particular {{< glossary\_tooltip text="node(s)" term\_id="node" >}}, or to \_prefer\_ to run on particular nodes. There are several ways to do this and the recommended approaches all use [label selectors](/doc... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/assign-pod-node.md | main | kubernetes | [
-0.06742334365844727,
0.019462471827864647,
0.07137899100780487,
0.019859185442328453,
-0.002722226083278656,
-0.004839158151298761,
0.06525682657957077,
-0.0636930987238884,
0.050477586686611176,
0.015529636293649673,
-0.03021557256579399,
-0.05336400866508484,
0.010973582975566387,
-0.03... | 0.008784 |
on the node (or other topological domain), instead of just node labels, which allows you to define rules for which Pods can be co-located on a node. The affinity feature consists of two types of affinity: - \*Node affinity\* functions like the `nodeSelector` field but is more expressive and allows you to specify soft r... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/assign-pod-node.md | main | kubernetes | [
0.006492099724709988,
0.01290526520460844,
0.007422295864671469,
0.04296022281050682,
0.028146328404545784,
-0.003821983467787504,
0.03556670621037483,
-0.024277159944176674,
0.010388855822384357,
-0.029475750401616096,
-0.0020697228610515594,
-0.054249148815870285,
0.010618261061608791,
-... | 0.211937 |
the Pod onto the node with the highest final score. {{}} If you want Kubernetes to successfully schedule the Pods in this example, you must have existing nodes with the `kubernetes.io/os=linux` label. {{}} #### Node affinity per scheduling profile {{< feature-state for\_k8s\_version="v1.20" state="beta" >}} When config... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/assign-pod-node.md | main | kubernetes | [
0.04919671267271042,
-0.017284680157899857,
0.02844262309372425,
0.054063830524683,
-0.011948619037866592,
0.03309381380677223,
-0.03786424547433853,
-0.024233326315879822,
-0.009532934986054897,
0.017163053154945374,
-0.09202531725168228,
-0.04510034993290901,
0.011250784620642662,
0.0250... | 0.103076 |
spread Pods from a service across multiple cloud provider zones. To use inter-pod affinity, use the `affinity.podAffinity` field in the Pod spec. For inter-pod anti-affinity, use the `affinity.podAntiAffinity` field in the Pod spec. #### Scheduling Behavior When scheduling a new Pod, the Kubernetes scheduler evaluates ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/assign-pod-node.md | main | kubernetes | [
0.017026768997311592,
-0.03573786839842796,
0.06880486756563187,
0.04086752608418465,
0.056465715169906616,
-0.03772537410259247,
0.013142273761332035,
-0.029059357941150665,
-0.005199123173952103,
0.002851063385605812,
-0.02215772680938244,
-0.047578807920217514,
0.005664026364684105,
0.0... | 0.161423 |
work. In principle, the `topologyKey` can be any allowed label key with the following exceptions for performance and security reasons: - For Pod affinity and anti-affinity, an empty `topologyKey` field is not allowed in both `requiredDuringSchedulingIgnoredDuringExecution` and `preferredDuringSchedulingIgnoredDuringExe... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/assign-pod-node.md | main | kubernetes | [
0.05765264108777046,
-0.023074544966220856,
-0.03641238436102867,
-0.04984624311327934,
-0.025713926181197166,
0.04455976188182831,
0.050297822803258896,
0.004716531839221716,
0.014333370141685009,
0.010496909730136395,
0.004744932986795902,
-0.03694489970803261,
0.044035863131284714,
-0.0... | 0.117271 |
the labels that should not match with the incoming Pod's labels, when satisfying the Pod (anti)affinity. {{< caution >}} It's not recommended to use `mismatchLabelKeys` with labels that might be updated directly on pods. Even if you edit the pod's label that is specified at `mismatchLabelKeys` \*\*directly\*\*, (that i... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/assign-pod-node.md | main | kubernetes | [
0.07196028530597687,
-0.0066046505235135555,
0.010396372526884079,
-0.02715744823217392,
-0.019177835434675217,
0.0026219720020890236,
0.03609396144747734,
-0.04858282208442688,
0.07047096639871597,
-0.020440170541405678,
0.06992429494857788,
-0.07967018336057663,
0.011261144652962685,
-0.... | 0.095209 |
matchExpressions: - key: app operator: In values: - web-store topologyKey: "kubernetes.io/hostname" podAffinity: requiredDuringSchedulingIgnoredDuringExecution: - labelSelector: matchExpressions: - key: app operator: In values: - store topologyKey: "kubernetes.io/hostname" containers: - name: web-app image: nginx:1.16-... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/assign-pod-node.md | main | kubernetes | [
-0.026817843317985535,
0.07147066295146942,
0.04486642777919769,
0.0004741358570754528,
0.01052411925047636,
-0.06300128251314163,
0.013897489756345749,
-0.07696965336799622,
0.04564707353711128,
0.02405889518558979,
-0.005510029848664999,
-0.06285180151462555,
0.023589996621012688,
-0.074... | 0.119635 |
You might do this to improve performance, expected availability, or overall utilization. Read [Pod topology spread constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/) to learn more about how these work. ## Pod topology labels {{< feature-state feature\_gate\_name="PodTopologyLabelsAdmission" >... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/assign-pod-node.md | main | kubernetes | [
0.07486111670732498,
-0.006402109749615192,
-0.00873115099966526,
0.03686456382274628,
-0.007271393667906523,
-0.01114730816334486,
-0.02669636905193329,
-0.026203202083706856,
0.029956979677081108,
-0.010638737119734287,
-0.09155423194169998,
-0.020538898184895515,
-0.00960335973650217,
-... | 0.155918 |
{{< feature-state for\_k8s\_version="v1.19" state="stable" >}} The \_scheduling framework\_ is a pluggable architecture for the Kubernetes scheduler. It consists of a set of "plugin" APIs that are compiled directly into the scheduler. These APIs allow most scheduling features to be implemented as plugins, while keeping... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/scheduling-framework.md | main | kubernetes | [
-0.07219470292329788,
0.02978178858757019,
0.056441035121679306,
0.042752791196107864,
-0.03399110212922096,
0.009589468128979206,
-0.02024700492620468,
-0.046825092285871506,
0.066500224173069,
0.003861569333821535,
-0.0662480965256691,
-0.011303763836622238,
-0.05743493139743805,
0.00857... | 0.251967 |
If any filter plugin marks the node as infeasible, the remaining plugins will not be called for that node. Nodes may be evaluated concurrently. ### PostFilter {#post-filter} These plugins are called after the Filter phase, but only when no feasible nodes were found for the pod. Plugins are called in their configured or... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/scheduling-framework.md | main | kubernetes | [
-0.02391519956290722,
-0.002829618053510785,
0.035575371235609055,
0.0725897029042244,
0.04400527849793434,
0.04006243124604225,
-0.056052066385746,
-0.056414179503917694,
-0.00026187789626419544,
0.01770944520831108,
-0.04518386721611023,
0.020914895460009575,
-0.044269587844610214,
-0.01... | 0.177835 |
the `Reserve` method of all plugins succeed, the Reserve phase is considered to be successful and the rest of the scheduling cycle and the binding cycle are executed. The Unreserve phase is triggered if the Reserve phase or a later phase fails. When this happens, the `Unreserve` method of \*\*all\*\* Reserve plugins wi... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/scheduling-framework.md | main | kubernetes | [
-0.1019086241722107,
0.0037945150397717953,
0.022955145686864853,
0.09234242141246796,
0.06517645716667175,
0.025135179981589317,
-0.01786898449063301,
-0.07692088931798935,
-0.01120894867926836,
0.017123615369200706,
0.0373903252184391,
0.021108057349920273,
0.03867896646261215,
-0.049135... | 0.163442 |
configured along with default plugins. You can visit [scheduler-plugins](https://github.com/kubernetes-sigs/scheduler-plugins) for more details. If you are using Kubernetes v1.18 or later, you can configure a set of plugins as a scheduler profile and then define multiple profiles to fit various kinds of workload. Learn... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/scheduling-framework.md | main | kubernetes | [
0.010869369842112064,
-0.054705191403627396,
-0.0015053533716127276,
0.03676678240299225,
-0.06847328692674637,
0.016990819945931435,
-0.045165278017520905,
-0.031040307134389877,
0.06187157332897186,
0.0019096217583864927,
-0.11019743978977203,
-0.03893882408738136,
-0.015287834219634533,
... | 0.138498 |
{{< feature-state for\_k8s\_version="v1.30" state="stable" >}} Pods were considered ready for scheduling once created. Kubernetes scheduler does its due diligence to find nodes to place all pending Pods. However, in a real-world case, some Pods may stay in a "miss-essential-resources" state for a long period. These Pod... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md | main | kubernetes | [
-0.013661235570907593,
0.03595655411481857,
0.0542651005089283,
0.1051369309425354,
0.01843573898077011,
0.00361839821562171,
-0.03886140510439873,
-0.050168391317129135,
0.004797426052391529,
0.03915838897228241,
-0.04722768813371658,
0.026198919862508774,
-0.046268463134765625,
0.0139965... | 0.183612 |
terms are not authoritative, and so policy controllers don't validate those terms. ## {{% heading "whatsnext" %}} \* Read the [PodSchedulingReadiness KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/3521-pod-scheduling-readiness) for more details | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md | main | kubernetes | [
0.018797453492879868,
0.04762421175837517,
0.06872954964637756,
0.03659148886799812,
0.000008204550795198884,
0.014353638514876366,
0.02380211092531681,
-0.03233550861477852,
0.03013015352189541,
0.055425047874450684,
0.0034905089996755123,
-0.047357380390167236,
-0.02261143922805786,
-0.0... | 0.148923 |
{{}} The {{}} monitors resources like memory, disk space, and filesystem inodes on your cluster's nodes. When one or more of these resources reach specific consumption levels, the kubelet can proactively fail one or more pods on the node to reclaim resources and prevent starvation. During a node-pressure eviction, the ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/node-pressure-eviction.md | main | kubernetes | [
-0.001048995298333466,
0.07232581079006195,
0.06197831779718399,
0.04897323623299599,
-0.016491740942001343,
-0.040438853204250336,
-0.028142353519797325,
-0.02610802836716175,
0.10113619267940521,
-0.00039672947605140507,
-0.010561134666204453,
-0.034489426761865616,
-0.012257024645805359,
... | 0.192978 |
if users use the [node allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable) feature, out of resource decisions are made local to the end user Pod part of the cgroup hierarchy as well as the root node. This [script](/examples/admin/resource/memory-available.sh) or [cgroupv2 script](/e... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/node-pressure-eviction.md | main | kubernetes | [
0.02779776230454445,
0.04785370081663132,
-0.05577034875750542,
0.07735363394021988,
-0.026905763894319534,
0.03445855528116226,
-0.003416015300899744,
0.044969022274017334,
0.10418809205293655,
0.014896131120622158,
-0.007180199958384037,
-0.02949613519012928,
-0.02276998944580555,
-0.060... | 0.179435 |
and [hard](#hard-eviction-thresholds) eviction thresholds. Eviction thresholds have the form `[eviction-signal][operator][quantity]`, where: - `eviction-signal` is the [eviction signal](#eviction-signals) to use. - `operator` is the [relational operator](https://en.wikipedia.org/wiki/Relational\_operator#Standard\_rela... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/node-pressure-eviction.md | main | kubernetes | [
0.04040715470910072,
-0.0018985564820468426,
0.0004438383039087057,
0.02206660620868206,
-0.06464195996522903,
0.012416357174515724,
0.010400720871984959,
0.0067069996148347855,
0.09273193776607513,
-0.00912378914654255,
0.01057762186974287,
-0.06711237132549286,
0.029809199273586273,
0.00... | 0.147714 |
as such, be ignored. ## Eviction monitoring interval The kubelet evaluates eviction thresholds based on its configured `housekeeping-interval`, which defaults to `10s`. ## Node conditions {#node-conditions} The kubelet reports [node conditions](/docs/concepts/architecture/nodes/#condition) to reflect that the node is u... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/node-pressure-eviction.md | main | kubernetes | [
-0.03816215321421623,
0.07598517835140228,
0.09290777146816254,
0.00808830838650465,
-0.030706631019711494,
-0.044703081250190735,
-0.0164219718426466,
-0.04913010820746422,
0.08698362112045288,
-0.06524457782506943,
0.014997482299804688,
-0.08188429474830627,
0.015503867529332638,
-0.1002... | 0.064535 |
based on their Priority. {{}} The kubelet does not use the pod's [QoS class](/docs/concepts/workloads/pods/pod-qos/) to determine the eviction order. You can use the QoS class to estimate the most likely pod eviction order when reclaiming resources like memory. QoS classification does not apply to EphemeralStorage requ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/node-pressure-eviction.md | main | kubernetes | [
0.012350812554359436,
0.06417059898376465,
0.05063316971063614,
0.03798314183950424,
-0.0009546688525006175,
-0.025049252435564995,
0.009399058297276497,
-0.028707366436719894,
0.11313634365797043,
0.03671236336231232,
0.0003176578611601144,
0.03352592885494232,
0.015281254425644875,
-0.03... | 0.180543 |
if the `nodefs.available` signal meets the eviction threshold, the kubelet reclaims the resource until the signal reaches the threshold of 1GiB, and then continues to reclaim the minimum amount of 500MiB, until the available nodefs storage value reaches 1.5GiB. Similarly, the kubelet tries to reclaim the `imagefs` reso... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/node-pressure-eviction.md | main | kubernetes | [
0.017283208668231964,
0.05312316492199898,
0.04921073094010353,
0.07136397063732147,
0.004636506084352732,
-0.025428323075175285,
0.026842329651117325,
-0.01696794480085373,
0.11524044722318649,
0.0006975132855586708,
0.020893491804599762,
0.012661105021834373,
0.01758362166583538,
-0.0438... | 0.156521 |
memory usage stats at a regular interval. If memory usage increases within that window rapidly, the kubelet may not observe `MemoryPressure` fast enough, and the OOM killer will still be invoked. You can use the `--kernel-memcg-notification` flag to enable the `memcg` notification API on the kubelet to get notified imm... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/node-pressure-eviction.md | main | kubernetes | [
0.03639361262321472,
0.03120788186788559,
-0.003008012194186449,
0.054605431854724884,
0.014900648966431618,
-0.08095770329236984,
0.059838611632585526,
0.130522683262825,
0.1114833876490593,
0.06499352306127548,
-0.02157129906117916,
0.00281856139190495,
-0.03622688725590706,
-0.052390430... | 0.160825 |
{{< feature-state for\_k8s\_version="v1.14" state="stable" >}} [Pods](/docs/concepts/workloads/pods/) can have \_priority\_. Priority indicates the importance of a Pod relative to other Pods. If a Pod cannot be scheduled, the scheduler tries to preempt (evict) lower priority Pods to make scheduling of the pending Pod p... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/pod-priority-preemption.md | main | kubernetes | [
-0.014115174300968647,
0.059038978070020676,
0.0386488251388073,
0.06571336835622787,
0.018825948238372803,
-0.014583761803805828,
0.024451563134789467,
0.011893718503415585,
-0.008081633597612381,
0.048888228833675385,
-0.006755503825843334,
-0.010502743534743786,
0.004103056620806456,
0.... | 0.173812 |
of lower-priority pods, but they cannot preempt other pods. A non-preempting pod waiting to be scheduled will stay in the scheduling queue, until sufficient resources are free, and it can be scheduled. Non-preempting pods, like other pods, are subject to scheduler back-off. This means that if the scheduler tries these ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/pod-priority-preemption.md | main | kubernetes | [
-0.017460854724049568,
-0.029861118644475937,
0.053943853825330734,
0.042131926864385605,
-0.010786715894937515,
-0.011634650640189648,
-0.05412844195961952,
-0.02523116208612919,
0.04394618049263954,
0.05963916704058647,
0.02583177387714386,
0.0162755586206913,
-0.02000593952834606,
-0.02... | 0.127842 |
for Pod P and also gives users information about preemptions in their clusters. Please note that Pod P is not necessarily scheduled to the "nominated Node". The scheduler always tries the "nominated Node" before iterating over any other nodes. After victim Pods are preempted, they get their graceful termination period.... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/pod-priority-preemption.md | main | kubernetes | [
0.007990926504135132,
0.015216536819934845,
0.06327518820762634,
0.029346339404582977,
0.07993307709693909,
0.014730358496308327,
-0.021316897124052048,
-0.032227784395217896,
0.05524783208966255,
0.044203486293554306,
-0.011459064669907093,
0.05979900062084198,
-0.03180411458015442,
-0.01... | 0.162495 |
problem is to create inter-Pod affinity only towards equal or higher priority Pods. #### Cross node preemption Suppose a Node N is being considered for preemption so that a pending Pod P can be scheduled on N. P might become feasible on N only if a Pod on another Node is preempted. Here's an example: \* Pod P is being ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/pod-priority-preemption.md | main | kubernetes | [
-0.014793242327868938,
0.00708434171974659,
0.04396221041679382,
0.017635319381952286,
0.022368306294083595,
0.0017386105610057712,
0.010597252286970615,
-0.023498358204960823,
-0.0012024809839203954,
0.0503927581012249,
-0.017210621386766434,
-0.012489096261560917,
-0.03236638009548187,
-... | 0.163947 |
arbitrary node in order to make room for the pending pod. If a node with low priority Pods is not feasible to run the pending Pod, the scheduler may choose another node with higher priority Pods (compared to the Pods on the other node) for preemption. The victims must still have lower priority than the preemptor Pod. W... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/pod-priority-preemption.md | main | kubernetes | [
-0.014696987345814705,
0.005923601798713207,
0.04829251766204834,
0.011281725950539112,
0.014339612796902657,
-0.022388998419046402,
-0.0014554329682141542,
-0.029088394716382027,
0.04904422163963318,
0.08169089257717133,
-0.0015907404012978077,
0.03313950449228287,
-0.008791284635663033,
... | 0.128358 |
{{< feature-state feature\_gate\_name="GangScheduling" >}} Gang scheduling ensures that a group of Pods are scheduled on an "all-or-nothing" basis. If the cluster cannot accommodate the entire group (or a defined minimum number of Pods), none of the Pods are bound to a node. This feature depends on the [Workload API](/... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/gang-scheduling.md | main | kubernetes | [
-0.05461808294057846,
-0.0011875225463882089,
0.05009806156158447,
0.08691150695085526,
0.005282063037157059,
-0.020071230828762054,
-0.05144699662923813,
-0.06459343433380127,
0.0069045331329107285,
0.03448419272899628,
-0.023444123566150665,
-0.020112749189138412,
-0.02501625567674637,
-... | 0.157336 |
{{< feature-state feature\_gate\_name="DynamicResourceAllocation" >}} This page describes \_dynamic resource allocation (DRA)\_ in Kubernetes. ## About DRA {#about-dra} {{< glossary\_definition prepend="DRA is" term\_id="dra" length="all" >}} Allocating resources with DRA is a similar experience to [dynamic volume prov... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md | main | kubernetes | [
0.018289444968104362,
0.019568752497434616,
0.053808845579624176,
0.03345223143696785,
-0.04561411589384079,
-0.010875196196138859,
0.039464909583330154,
0.003678657580167055,
0.04026683419942856,
0.03544413670897484,
-0.06089385598897934,
-0.06876066327095032,
0.03210148587822914,
0.00641... | 0.140991 |
generates from the template is bound to a specific Pod. When the Pod terminates, Kubernetes deletes the corresponding ResourceClaim. ResourceSlice : Represents one or more resources that are attached to nodes, such as devices. Drivers create and manage ResourceSlices in the cluster. When a ResourceClaim is created and ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md | main | kubernetes | [
-0.010498086921870708,
0.056219346821308136,
0.05206599086523056,
0.024021267890930176,
0.05047095939517021,
0.003128736512735486,
0.031984202563762665,
-0.046157196164131165,
0.07653303444385529,
0.012016303837299347,
-0.022811638191342354,
-0.06599606573581696,
-0.00026680223527364433,
-... | 0.201168 |
be specified, which requests two devices with the color white and size small. The large black device will be allocated if it is available. If it is not, but two small white devices are available, the pod will still be able to run. ```yaml apiVersion: resource.k8s.io/v1 kind: ResourceClaimTemplate metadata: name: priori... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md | main | kubernetes | [
0.029467737302184105,
0.05556509643793106,
0.06461090594530106,
0.00827733613550663,
0.07979800552129745,
-0.022397153079509735,
0.016431163996458054,
-0.02530864253640175,
0.0635671317577362,
0.02870306931436062,
-0.011107594706118107,
-0.08186406642198563,
0.013242488726973534,
0.0340497... | 0.105392 |
any node in the cluster can access the devices. There's one device in the ResourceSlice, named `large-black-cat`, with the following attributes: \* `color`: `black` \* `size`: `large` \* `cat`: `true` A DeviceClass could select this ResourceSlice by using these attributes, and a ResourceClaim could filter for specific ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md | main | kubernetes | [
0.02317138947546482,
0.0243113674223423,
0.035039644688367844,
-0.0022587997373193502,
-0.0008174664108082652,
-0.013529974035918713,
0.04834869131445885,
-0.019208291545510292,
0.05910062417387962,
0.009355495683848858,
-0.05552796274423599,
-0.06744088232517242,
0.016288021579384804,
-0.... | 0.197489 |
you disable the `DRAResourceClaimDeviceStatus` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/), the `status.devices` field automatically gets cleared when storing the ResourceClaim. A ResourceClaim device status is supported when it is possible, from a DRA driver, to update an existing Resou... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md | main | kubernetes | [
-0.025198204442858696,
0.048529352992773056,
0.05143298581242561,
0.006118862424045801,
0.02647481858730316,
-0.05999834090471268,
0.030942073091864586,
-0.0242629311978817,
0.09380371868610382,
0.0610075443983078,
-0.06686928123235703,
-0.021551033481955528,
-0.021335314959287643,
0.05009... | 0.180396 |
allocationMode: All adminAccess: true ``` If this feature is disabled, the `adminAccess` field will be removed automatically when creating such a ResourceClaim. Admin access is a privileged mode and should not be granted to regular users in multi-tenant clusters. Starting with Kubernetes v1.33, only users authorized to... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md | main | kubernetes | [
-0.005489286035299301,
0.0022240544203668833,
0.0045583234168589115,
0.046785201877355576,
-0.016582932323217392,
0.014179691672325134,
0.03661954030394554,
-0.09125711023807526,
0.04816794767975807,
0.05680673569440842,
0.0023446448612958193,
-0.047742120921611786,
-0.04584198445081711,
0... | 0.089307 |
any CounterSet defined in the same resource pool as the device. Here is an example of two devices, each consuming 6Gi of memory from a shared counter with 8Gi of memory. Thus, only one of the devices can be allocated at any point in time. The scheduler handles this and it is transparent to the consumer as the ResourceC... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md | main | kubernetes | [
-0.06333339214324951,
-0.005167987197637558,
-0.060008980333805084,
0.05043336749076843,
-0.007284348364919424,
-0.04202805459499359,
0.03365618735551834,
-0.04187049716711044,
0.0974964126944542,
0.014453629031777382,
-0.043722592294216156,
-0.031023772433400154,
0.0484737753868103,
0.060... | 0.130719 |
taint has a string key, a string value, and an effect. The effect is applied to the ResourceClaim which is using a tainted device and to all Pods referencing that ResourceClaim. The "NoSchedule" effect prevents scheduling those Pods. Tainted devices are ignored when trying to allocate a ResourceClaim because using them... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md | main | kubernetes | [
0.010314753279089928,
0.036135438829660416,
0.05527082458138466,
0.009118527173995972,
0.07061587274074554,
0.015514295548200607,
0.01938874088227749,
0.007081923075020313,
0.09292584657669067,
0.008849403820931911,
0.04043752700090408,
-0.041289132088422775,
0.016508374363183975,
-0.02905... | 0.213556 |
select one specific device. The device name and pool name can also be used alone, if desired. For example, drivers for node-local devices are encouraged to use the node name as their pool name. Then tainting with that pool name automatically taints all devices on a node. Drivers might use stable names like "gpu-0" that... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md | main | kubernetes | [
-0.04653797671198845,
0.06544798612594604,
0.03835628926753998,
-0.022776197642087936,
0.057121507823467255,
-0.07384923845529556,
0.07823622226715088,
-0.020663347095251083,
0.03877487778663635,
-0.08394148200750351,
0.01480367872864008,
-0.10574636608362198,
0.008112489245831966,
0.01636... | 0.125409 |
waiting behavior is implemented in the [PreBind phase](/docs/concepts/scheduling-eviction/scheduling-framework/#pre-bind) of the scheduling framework. During this phase, the scheduler checks whether all required device conditions are satisfied before proceeding with binding. This improves scheduling reliability by avoi... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md | main | kubernetes | [
-0.058661799877882004,
-0.022962896153330803,
0.007326866500079632,
0.04960758984088898,
0.01875670626759529,
-0.022052191197872162,
-0.03001302108168602,
-0.050453055649995804,
0.025190893560647964,
0.020628873258829117,
-0.009705128148198128,
-0.018047597259283066,
0.001498697092756629,
... | 0.178262 |
{{< feature-state for\_k8s\_version="v1.24" state="stable" >}} When you run a Pod on a Node, the Pod itself takes an amount of system resources. These resources are additional to the resources needed to run the container(s) inside the Pod. In Kubernetes, \_Pod Overhead\_ is a way to account for the resources consumed b... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/pod-overhead.md | main | kubernetes | [
0.03395042195916176,
0.07779772579669952,
0.027454059571027756,
0.039952244609594345,
0.01178151834756136,
-0.04428448900580406,
0.029331907629966736,
0.02972199022769928,
0.056223344057798386,
0.016413887962698936,
-0.006075650453567505,
-0.020396441221237183,
-0.01874832808971405,
-0.078... | 0.219836 |
limit defined for each container (Guaranteed QoS or Burstable QoS with limits defined), the kubelet will set an upper limit for the pod cgroup associated with that resource (cpu.cfs\_quota\_us for CPU and memory.limit\_in\_bytes memory). This upper limit is based on the sum of the container limits plus the `overhead` d... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/pod-overhead.md | main | kubernetes | [
0.04820113629102707,
0.04558476433157921,
0.006878674495965242,
0.04761123284697533,
-0.042335063219070435,
-0.049941111356019974,
0.007900918833911419,
-0.01432611234486103,
0.05517030134797096,
0.02766050212085247,
-0.04914626106619835,
-0.030376998707652092,
-0.03464026749134064,
-0.034... | 0.16094 |
{{< feature-state for\_k8s\_version="v1.14" state="beta" >}} [kube-scheduler](/docs/concepts/scheduling-eviction/kube-scheduler/#kube-scheduler) is the Kubernetes default scheduler. It is responsible for placement of Pods on Nodes in a cluster. Nodes in a cluster that meet the scheduling requirements of a Pod are calle... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/scheduler-perf-tuning.md | main | kubernetes | [
-0.019829727709293365,
0.03294900804758072,
0.024593360722064972,
0.0690159946680069,
-0.013463064096868038,
-0.025337472558021545,
-0.05833755061030388,
-0.03254111483693123,
0.035688478499650955,
0.008181833662092686,
-0.07931648194789886,
-0.013059450313448906,
0.008356666192412376,
-0.... | 0.216641 |
low value for `percentageOfNodesToScore`, your change will have no or little effect, for a similar reason. If your cluster has several hundred Nodes or fewer, leave this configuration option at its default value. Making changes is unlikely to improve the scheduler's performance significantly. {{< /note >}} An important... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/scheduler-perf-tuning.md | main | kubernetes | [
0.0555114708840847,
0.029865281656384468,
0.00401398167014122,
0.061866406351327896,
0.008816546760499477,
-0.030049853026866913,
-0.07591316103935242,
0.00827920250594616,
0.021922029554843903,
0.025823179632425308,
-0.08362077176570892,
-0.041227541863918304,
-0.020348627120256424,
-0.03... | 0.136588 |
exclusively on nodes (i.e., placing more than one pod on one node invalidates the cache) Also, to enable this feature, the scheduler configuration needs to: 1. Disable [default topology spread](/docs/concepts/scheduling-eviction/topology-spread-constraints/#internal-default-constraints) (set empty) 1. Disable [DRAExten... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/scheduler-perf-tuning.md | main | kubernetes | [
-0.012537378817796707,
-0.002892408985644579,
0.04210765287280083,
0.0351884551346302,
-0.021730899810791016,
-0.04380633309483528,
-0.02025275118649006,
-0.028121264651417732,
0.007758167572319508,
-0.008277356624603271,
-0.06777051836252213,
-0.031945083290338516,
-0.021173037588596344,
... | 0.123762 |
In the [scheduling-plugin](/docs/reference/scheduling/config/#scheduling-plugins) `NodeResourcesFit` of kube-scheduler, there are two scoring strategies that support the bin packing of resources: `MostAllocated` and `RequestedToCapacityRatio`. ## Enabling bin packing using MostAllocated strategy The `MostAllocated` str... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/resource-bin-packing.md | main | kubernetes | [
-0.012491966597735882,
0.034387826919555664,
-0.016917698085308075,
0.05067851021885872,
0.009124074131250381,
-0.0018577806185930967,
0.013552241027355194,
-0.0278469230979681,
0.017094280570745468,
0.06072826310992241,
-0.09053391218185425,
-0.046351686120033264,
0.020125096663832664,
0.... | 0.141571 |
node score is calculated for a given set of values. Requested resources: ``` intel.com/foo : 2 memory: 256MB cpu: 2 ``` Resource weights: ``` intel.com/foo : 5 memory: 1 cpu: 3 ``` FunctionShapePoint {{0, 0}, {100, 10}} Node 1 spec: ``` Available: intel.com/foo: 4 memory: 1 GB cpu: 8 Used: intel.com/foo: 1 memory: 256M... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/resource-bin-packing.md | main | kubernetes | [
0.01683538779616356,
0.03453720360994339,
-0.08068004250526428,
0.1066289022564888,
0.03260190412402153,
-0.05680636689066887,
0.0030059406999498606,
0.06966768950223923,
-0.01649637147784233,
0.012553227134048939,
-0.07356195151805878,
-0.07131592184305191,
0.03999289497733116,
-0.0339768... | 0.138553 |
{{< glossary\_definition term\_id="api-eviction" length="short" >}} You can request eviction by calling the Eviction API directly, or programmatically using a client of the {{}}, like the `kubectl drain` command. This creates an `Eviction` object, which causes the API server to terminate the Pod. API-initiated eviction... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/api-eviction.md | main | kubernetes | [
-0.015047789551317692,
0.0693490281701088,
0.06227463111281395,
-0.028817925602197647,
-0.052505411207675934,
-0.03813181445002556,
-0.0471971370279789,
-0.03852026164531708,
0.07815811783075333,
0.04205051437020302,
0.0077949510887265205,
-0.03703504800796509,
-0.02622339315712452,
-0.026... | 0.100753 |
not enter a `Ready` state. You may also notice this behavior in cases where the last evicted Pod had a long termination grace period. If you notice stuck evictions, try one of the following solutions: \* Abort or pause the automated operation causing the issue. Investigate the stuck application before you restart the o... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/api-eviction.md | main | kubernetes | [
0.0618610642850399,
0.01000225730240345,
0.04408581182360649,
0.04505553096532822,
0.035226088017225266,
-0.04113437607884407,
-0.07116957753896713,
-0.055646512657403946,
0.005803392268717289,
0.053871043026447296,
0.049753446131944656,
0.0008050893666222692,
-0.01892726868391037,
-0.0202... | 0.108774 |
[\_Node affinity\_](/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity) is a property of {{< glossary\_tooltip text="Pods" term\_id="pod" >}} that \*attracts\* them to a set of {{< glossary\_tooltip text="nodes" term\_id="node" >}} (either as a preference or a hard requirement). \_Taints\_ a... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md | main | kubernetes | [
-0.059943608939647675,
-0.0009764101705513895,
0.04484452307224274,
0.04989269748330116,
0.058994632214307785,
-0.00524928979575634,
0.11074303835630417,
-0.06220374256372452,
0.0054392265155911446,
-0.011418106034398079,
0.02296084351837635,
-0.054509636014699936,
0.013918253593146801,
-0... | 0.194007 |
`NoSchedule` : No new Pods will be scheduled on the tainted node unless they have a matching toleration. Pods currently running on the node are \*\*not\*\* evicted. `PreferNoSchedule` : `PreferNoSchedule` is a "preference" or "soft" version of `NoSchedule`. The control plane will \*try\* to avoid placing a Pod that doe... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md | main | kubernetes | [
0.054269254207611084,
0.012677589431405067,
0.07742288708686829,
0.02832573838531971,
0.06172981485724449,
0.001672715530730784,
0.028345301747322083,
-0.09682569652795792,
0.08280865103006363,
0.03665042296051979,
-0.001221519778482616,
-0.029514862224459648,
0.012685246765613556,
-0.0526... | 0.13988 |
If either value cannot be parsed as an integer, the toleration does not match. {{< note >}} When you create a Pod that uses `Gt` or `Lt` tolerations operators, the API server validates that the toleration values are valid integers. Taint values on nodes are not validated at node registration time. If a node has a non-n... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md | main | kubernetes | [
0.0031036511063575745,
0.01884283311665058,
0.036908648908138275,
0.015999697148799896,
0.0233748871833086,
-0.02600032463669777,
-0.011975135654211044,
-0.013966198079288006,
0.03989623114466667,
0.0095502445474267,
-0.0438070222735405,
-0.05840161815285683,
0.018476832658052444,
0.000295... | 0.132764 |
need the specialized hardware. This can be done by tainting the nodes that have the specialized hardware (e.g. `kubectl taint nodes nodename special=true:NoSchedule` or `kubectl taint nodes nodename special=true:PreferNoSchedule`) and adding a corresponding toleration to pods that use the special hardware. As in the de... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md | main | kubernetes | [
0.03367520868778229,
0.043219901621341705,
0.047234807163476944,
0.0190206877887249,
0.021890146657824516,
-0.04395399987697601,
0.02500537969172001,
-0.021142246201634407,
0.0015523522160947323,
0.02846551686525345,
-0.05711079761385918,
-0.033356744796037674,
0.032643843442201614,
-0.019... | 0.175589 |
note >}} Kubernetes automatically adds a toleration for `node.kubernetes.io/not-ready` and `node.kubernetes.io/unreachable` with `tolerationSeconds=300`, unless you, or a controller, set those tolerations explicitly. These automatically-added tolerations mean that Pods remain bound to Nodes for 5 minutes after one of t... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md | main | kubernetes | [
0.015901943668723106,
-0.01231620367616415,
0.06052597239613533,
0.05088447779417038,
0.10235413908958435,
-0.012715906836092472,
0.008529573678970337,
-0.04177907481789589,
0.07605886459350586,
0.09458545595407486,
0.05532514676451683,
0.005953193176537752,
-0.002131051616743207,
-0.00214... | 0.143609 |
You can use \_topology spread constraints\_ to control how {{< glossary\_tooltip text="Pods" term\_id="Pod" >}} are spread across your cluster among failure-domains such as regions, zones, nodes, and other user-defined topology domains. This can help to achieve high availability as well as efficient resource utilizatio... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md | main | kubernetes | [
-0.004798560868948698,
-0.052679192274808884,
0.013608730398118496,
0.029221296310424805,
-0.01795843243598938,
-0.009895050898194313,
0.02154133841395378,
-0.017948314547538757,
0.0026091402396559715,
-0.0010240954579785466,
-0.03488743305206299,
-0.08348909765481949,
0.047264184802770615,
... | 0.088223 |
zero if the number of eligible domains is less than MinDomains). For example, if you have 3 zones with 2, 2 and 1 matching pods respectively, `MaxSkew` is set to 1 then the global minimum is 1. - if you select `whenUnsatisfiable: ScheduleAnyway`, the scheduler gives higher precedence to topologies that would help reduc... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md | main | kubernetes | [
0.033073943108320236,
-0.02515561133623123,
0.0367167703807354,
-0.04426604509353638,
0.019434668123722076,
-0.04436655715107918,
-0.0352143868803978,
-0.04396005719900131,
0.07916823774576187,
0.013159503228962421,
-0.015917088836431503,
-0.057808615267276764,
-0.01459150854498148,
0.0007... | 0.092533 |
update the `pod.spec` between different revisions. The controller/operator just needs to set different values to the same label key for different revisions. For example, if you are configuring a Deployment, you can use the label keyed with [pod-template-hash](/docs/concepts/workloads/controllers/deployment/#pod-templat... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md | main | kubernetes | [
0.016190387308597565,
0.01157311163842678,
0.05613350123167038,
-0.005849276203662157,
-0.018970869481563568,
0.03822110965847969,
-0.0352582186460495,
-0.05643245950341225,
0.11122381687164307,
0.05013638362288475,
-0.0005215320852585137,
-0.023751650005578995,
-0.03378210961818695,
-0.06... | 0.055228 |
Deployment, the pod template takes care of this for you. If you mix different spread constraints then Kubernetes follows the API definition of the field; however, the behavior is more likely to become confusing and troubleshooting is less straightforward. You need a mechanism to ensure that all the nodes in a topology ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md | main | kubernetes | [
0.06480240076780319,
-0.017326295375823975,
0.02180197276175022,
-0.023609153926372528,
0.02651924267411232,
0.03347477689385414,
-0.014588098973035812,
-0.06201108545064926,
0.013069319538772106,
-0.02488720417022705,
-0.033813126385211945,
-0.08392404764890671,
0.031711023300886154,
-0.0... | 0.068246 |
"zoneA" p1(Pod) --> n1(Node1) p2(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3 k8s; class p4 plain; class zoneA,... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md | main | kubernetes | [
0.027941318228840828,
0.005650533828884363,
-0.0006184683879837394,
-0.019474901258945465,
0.040153827518224716,
0.009013108909130096,
-0.02179863676428795,
-0.06082591041922569,
-0.05954820662736893,
-0.0007195415091700852,
-0.022240882739424706,
-0.06830193102359772,
-0.011666154488921165,... | 0.073768 |
be scheduled into zone `A`. 2. the incoming Pod has no chances to be scheduled onto this kind of nodes - in the above example, suppose a node `node5` has the \*\*mistyped\*\* label `zone-typo: zoneC` (and no `zone` label set). After node `node5` joins the cluster, it will be bypassed and Pods for this workload aren't s... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md | main | kubernetes | [
0.023361463099718094,
-0.008740453980863094,
0.026059802621603012,
0.03568597882986069,
0.020803311839699745,
0.0007965078111737967,
0.026203982532024384,
-0.07453577220439911,
0.006640201900154352,
0.010347956791520119,
-0.018892481923103333,
-0.023749178275465965,
0.037469495087862015,
-... | 0.143316 |
enforce the constraint. For finer control, you can specify topology spread constraints to distribute Pods across different topology domains - to achieve either high availability or cost-saving. This can also help on rolling update workloads and scaling out replicas smoothly. For more context, see the [Motivation](https... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md | main | kubernetes | [
0.004872030112892389,
0.02087676152586937,
0.08620597422122955,
0.022191468626260757,
-0.01986624114215374,
-0.017599424347281456,
-0.05077355355024338,
-0.029956268146634102,
0.014444943517446518,
0.034334003925323486,
-0.07101207971572876,
-0.02688612975180149,
0.009194967336952686,
-0.0... | 0.096764 |
In Kubernetes, \_scheduling\_ refers to making sure that {{< glossary\_tooltip text="Pods" term\_id="pod" >}} are matched to {{< glossary\_tooltip text="Nodes" term\_id="node" >}} so that {{< glossary\_tooltip term\_id="kubelet" >}} can run them. ## Scheduling overview {#scheduling} A scheduler watches for newly create... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/kube-scheduler.md | main | kubernetes | [
-0.03705579787492752,
0.005947981961071491,
0.08358725160360336,
0.038085952401161194,
-0.0011488159652799368,
-0.026210058480501175,
0.05028757452964783,
-0.09043759852647781,
0.11026977747678757,
0.0003803152358159423,
-0.027926448732614517,
-0.04003624618053436,
-0.017012862488627434,
-... | 0.1452 |
to run different profiles. ## {{% heading "whatsnext" %}} \* Read about [scheduler performance tuning](/docs/concepts/scheduling-eviction/scheduler-perf-tuning/) \* Read about [Pod topology spread constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/) \* Read the [reference documentation](/docs/r... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/kube-scheduler.md | main | kubernetes | [
0.0325201191008091,
-0.03449631109833717,
-0.003009881591424346,
0.018068069592118263,
-0.035686567425727844,
0.0059224627912044525,
-0.04792864993214607,
0.008979344740509987,
-0.03853040188550949,
-0.04352450743317604,
-0.05875514820218086,
-0.07184648513793945,
0.030943971127271652,
-0.... | 0.111926 |
In Kubernetes, scheduling refers to making sure that {{}} are matched to {{}} so that the {{}} can run them. Preemption is the process of terminating Pods with lower {{}} so that Pods with higher Priority can schedule on Nodes. Eviction is the process of terminating one or more Pods on Nodes. ## Scheduling \* [Kubernet... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/scheduling-eviction/_index.md | main | kubernetes | [
0.006016117986291647,
0.04713677987456322,
0.05213212966918945,
0.04267677664756775,
-0.0024006159510463476,
-0.011294948868453503,
-0.012132707051932812,
-0.04452333599328995,
0.04087177291512489,
0.038975365459918976,
0.0024270135909318924,
0.012834815308451653,
-0.04078572615981102,
-0.... | 0.200773 |
This document describes \_ephemeral volumes\_ in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/) is suggested, in particular PersistentVolumeClaim and PersistentVolume. Some applications need additional storage but don't care whether that data is stored persistently across restarts. For example,... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/ephemeral-volumes.md | main | kubernetes | [
0.019965199753642082,
0.013295798562467098,
0.019692258909344673,
0.00812778901308775,
-0.010353488847613335,
-0.007558236364275217,
-0.023555919528007507,
0.05547656491398811,
0.13789112865924835,
0.048053815960884094,
0.0012825281592085958,
0.07028856873512268,
0.001874758512713015,
-0.0... | 0.169992 |
prepared by the driver. These attributes are specific to each driver and not standardized. See the documentation of each CSI driver for further instructions. ### CSI driver restrictions CSI ephemeral volumes allow users to provide `volumeAttributes` directly to the CSI driver as part of the Pod spec. A CSI driver allow... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/ephemeral-volumes.md | main | kubernetes | [
0.046996209770441055,
0.07090992480516434,
-0.0268088448792696,
0.008756525814533234,
-0.003963951487094164,
-0.02731238305568695,
0.029332660138607025,
0.017986860126256943,
-0.01724415086209774,
0.012237351387739182,
0.030893003568053246,
-0.04578983411192894,
0.04791206493973732,
0.0441... | 0.123984 |
particular, they can be referenced as data source in volume cloning or snapshotting. The PVC object also holds the current status of the volume. ### PersistentVolumeClaim naming Naming of the automatically created PVCs is deterministic: the name is a combination of the Pod name and volume name, with a hyphen (`-`) in t... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/ephemeral-volumes.md | main | kubernetes | [
-0.09121046215295792,
-0.10195060074329376,
0.018857724964618683,
-0.05256538465619087,
0.01791837252676487,
-0.026498129591345787,
0.05179830268025398,
0.017367471009492874,
0.10046248883008957,
0.01278014201670885,
0.029235973954200745,
-0.06499426811933517,
0.05298684909939766,
-0.01182... | 0.137628 |
Storage capacity is limited and may vary depending on the node on which a pod runs: network-attached storage might not be accessible by all nodes, or storage is local to a node to begin with. {{< feature-state for\_k8s\_version="v1.24" state="stable" >}} This page describes how Kubernetes keeps track of storage capacit... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/storage-capacity.md | main | kubernetes | [
0.03581399843096733,
0.014269381761550903,
0.05074445903301239,
0.09172870218753815,
0.004696917720139027,
0.01783248409628868,
-0.07624176889657974,
-0.02323145419359207,
0.037898555397987366,
0.051114846020936966,
-0.05730835720896721,
-0.015695396810770035,
-0.005426822695881128,
0.0062... | 0.112731 |
Usually, the same retry mechanism as for scheduling without any storage capacity information handles scheduling failures. One situation where scheduling can fail permanently is when a Pod uses multiple volumes: one volume might have been created already in a topology segment which then does not have enough capacity lef... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/storage-capacity.md | main | kubernetes | [
0.007914192043244839,
0.027278997004032135,
0.09717701375484467,
0.09730050712823868,
-0.036106742918491364,
-0.019467921927571297,
-0.056723687797784805,
-0.03908662125468254,
0.02790580689907074,
0.024862539023160934,
-0.028760086745023727,
0.047277431935071945,
-0.012022115290164948,
-0... | 0.134958 |
This page provides an storage overview specific to the Windows operating system. ## Persistent storage {#storage} Windows has a layered filesystem driver to mount container layers and create a copy filesystem based on NTFS. All file paths in the container are resolved only within the context of that container. \* With ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/windows-storage.md | main | kubernetes | [
-0.019173286855220795,
-0.00734068313613534,
-0.056582506746053696,
0.08180782198905945,
0.019784487783908844,
0.016385605558753014,
-0.005712973419576883,
0.025447903200984,
0.030525190755724907,
0.025188017636537552,
-0.0600566491484642,
0.008589798584580421,
0.034522894769907,
0.0526610... | 0.026887 |
This document describes \_projected volumes\_ in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/) is suggested. ## Introduction A `projected` volume maps several existing volume sources into the same directory. Currently, the following types of volume sources can be projected: \* [`secret`](/docs... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/projected-volumes.md | main | kubernetes | [
-0.01896684244275093,
-0.046714991331100464,
0.007335084956139326,
-0.02355417236685753,
0.0014335073065012693,
-0.003698567161336541,
-0.025664735585451126,
-0.015946485102176666,
0.10738570243120193,
0.014841273427009583,
-0.022246014326810837,
-0.05693105235695839,
0.09269566088914871,
... | 0.101463 |
the pod from starting if the named ClusterTrustBundle is not found, or if `signerName` / `labelSelector` do not match any ClusterTrustBundles. If this behavior is not what you want, then set the `optional` field to `true`, and the pod will start up with an empty file at `path`. {{% code\_sample file="pods/storage/proje... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/projected-volumes.md | main | kubernetes | [
0.07619228959083557,
-0.010142211802303791,
0.005522436462342739,
0.047286782413721085,
0.04301949962973595,
0.021232735365629196,
-0.03205425664782524,
0.012410001829266548,
0.04839758947491646,
0.057149309664964676,
0.050873689353466034,
-0.07752879709005356,
0.008103515021502972,
0.0526... | 0.08002 |
in your application loading a mismatched key and certificate. {{< /note >}} {{% code\_sample file="pods/storage/projected-podcertificate.yaml" %}} ## SecurityContext interactions The [proposal](https://git.k8s.io/enhancements/keps/sig-storage/2451-service-account-token-volumes#proposal) for file permission handling in ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/projected-volumes.md | main | kubernetes | [
0.021243419498205185,
0.047365885227918625,
0.03209861367940903,
-0.009704533033072948,
-0.028910908848047256,
-0.03723863139748573,
0.025527164340019226,
0.03315548971295357,
0.06737083196640015,
0.04157298803329468,
0.005182781256735325,
-0.07060471177101135,
0.04117083176970482,
0.03962... | 0.095238 |
In Kubernetes, a \_VolumeSnapshot\_ represents a snapshot of a volume on a storage system. This document assumes that you are already familiar with Kubernetes [persistent volumes](/docs/concepts/storage/persistent-volumes/). ## Introduction Similar to how API resources `PersistentVolume` and `PersistentVolumeClaim` are... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/volume-snapshots.md | main | kubernetes | [
-0.04279160499572754,
-0.0033118959981948137,
0.00838396605104208,
-0.011429987847805023,
0.022788189351558685,
-0.020908048376441002,
0.020072847604751587,
0.004626413341611624,
0.10309887677431107,
-0.01797335594892502,
-0.015096059069037437,
-0.05190432816743851,
0.07308468222618103,
-0... | 0.134857 |
handles the binding of a `VolumeSnapshot` object with an appropriate `VolumeSnapshotContent` object, in both pre-provisioned and dynamically provisioned scenarios. The binding is a one-to-one mapping. In the case of pre-provisioned binding, the VolumeSnapshot will remain unbound until the requested VolumeSnapshotConten... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/volume-snapshots.md | main | kubernetes | [
-0.09916435927152634,
0.016638876870274544,
0.04501510411500931,
0.016193250194191933,
0.016591692343354225,
-0.0145265506580472,
0.0027175608556717634,
-0.04104863852262497,
0.0912388265132904,
0.04805348813533783,
0.03361843153834343,
-0.011706666089594364,
0.0709734857082367,
-0.0208663... | -0.020862 |
mode of a Snapshot {#convert-volume-mode} If the `VolumeSnapshots` API installed on your cluster supports the `sourceVolumeMode` field, then the API has the capability to prevent unauthorized users from converting the mode of a volume. To check if your cluster has capability for this feature, run the following command:... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/volume-snapshots.md | main | kubernetes | [
0.042364127933979034,
0.0007761384476907551,
0.0032735266722738743,
-0.04198829457163811,
-0.014858797192573547,
-0.02343270741403103,
-0.04216103255748749,
-0.022675907239317894,
0.03461260348558426,
0.02738252282142639,
-0.025090854614973068,
-0.08348491042852402,
0.0615910068154335,
-0.... | -0.011526 |
This document describes the concept of cloning existing CSI Volumes in Kubernetes. Familiarity with [Volumes](/docs/concepts/storage/volumes) is suggested. ## Introduction The {{< glossary\_tooltip text="CSI" term\_id="csi" >}} Volume Cloning feature adds support for specifying existing {{< glossary\_tooltip text="PVC"... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/volume-pvc-datasource.md | main | kubernetes | [
-0.1324126422405243,
-0.04573293775320053,
0.06420028954744339,
-0.04561594873666763,
-0.0476614385843277,
-0.044405583292245865,
0.07820142060518265,
-0.046381957828998566,
0.10530257970094681,
0.028342068195343018,
0.009980647824704647,
-0.05878563970327377,
0.06753452122211456,
-0.03187... | 0.071162 |
This document describes the concept of a StorageClass in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/) and [persistent volumes](/docs/concepts/storage/persistent-volumes) is suggested. A StorageClass provides a way for administrators to describe the \_classes\_ of storage they offer. Different... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/storage-classes.md | main | kubernetes | [
-0.058657702058553696,
0.014427806250751019,
0.003988089505583048,
0.01888941042125225,
-0.051255691796541214,
0.00755489943549037,
0.036326609551906586,
-0.012654813937842846,
0.06345251947641373,
0.014486530795693398,
-0.023313147947192192,
0.017773481085896492,
0.0585433728992939,
0.003... | 0.119293 |
FlexVolume | - | - | | iSCSI | - | - | | Local | - | [Local](#local) | | NFS | - | [NFS](#nfs) | | PortworxVolume | ✓ | [Portworx Volume](#portworx-volume) | | RBD | - | [Ceph RBD](#ceph-rbd) | | VsphereVolume | ✓ | [vSphere](#vsphere) | You are not restricted to specifying the "internal" provisioners listed here (whos... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/storage-classes.md | main | kubernetes | [
0.006111594848334789,
-0.067986860871315,
0.024779945611953735,
-0.013948977924883366,
0.024365369230508804,
-0.020204639062285423,
-0.07274594902992249,
0.05737103149294853,
0.021150045096874237,
0.00355662708170712,
-0.001095677725970745,
-0.08231210708618164,
0.013046476989984512,
0.011... | 0.164231 |
to the topology that is specified by the Pod's scheduling constraints. These include, but are not limited to, [resource requirements](/docs/concepts/configuration/manage-resources-containers/), [node selectors](/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector), [pod affinity and anti-affinity](/docs/con... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/storage-classes.md | main | kubernetes | [
0.004055976402014494,
-0.02559269219636917,
-0.007231409661471844,
0.0581347681581974,
0.00809544138610363,
-0.015356536954641342,
-0.011799695901572704,
-0.03522106260061264,
0.015267642214894295,
0.015314080752432346,
0.02158411778509617,
-0.029066644608974457,
0.005426882300525904,
0.00... | 0.138686 |
CSI Provisioner {#vsphere-provisioner-csi} The vSphere CSI StorageClass provisioner works with Tanzu Kubernetes clusters. For an example, refer to the [vSphere CSI repository](https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/example/vanilla-k8s-RWM-filesystem-volumes/example-sc.yaml). #### vCP Provisio... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/storage-classes.md | main | kubernetes | [
-0.0019225786672905087,
0.037414416670799255,
0.028780674561858177,
0.00798017904162407,
-0.00878533162176609,
-0.007538985460996628,
-0.041175298392772675,
0.05094097554683685,
0.040837790817022324,
0.08199750632047653,
0.0186450332403183,
-0.08046522736549377,
0.04644499719142914,
0.0532... | 0.090666 |
or "2". Default is "2". - `imageFeatures`: This parameter is optional and should only be used if you set `imageFormat` to "2". Currently supported features are `layering` only. Default is "", and no features are turned on. ### Azure Disk Kubernetes {{< skew currentVersion >}} does not include a `azureDisk` volume type.... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/storage-classes.md | main | kubernetes | [
0.011209730990231037,
0.02420041710138321,
0.008097234182059765,
0.04723580554127693,
0.015911061316728592,
0.038736797869205475,
-0.01169018168002367,
-0.014408967457711697,
0.09108015149831772,
0.08629147708415985,
0.038086920976638794,
-0.05732851102948189,
0.039253998547792435,
0.06619... | 0.026628 |
binding mode. Delaying volume binding allows the scheduler to consider all of a Pod's scheduling constraints when choosing an appropriate PersistentVolume for a PersistentVolumeClaim. | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/storage-classes.md | main | kubernetes | [
0.007096263580024242,
-0.046280164271593094,
0.04806433990597725,
0.030197707936167717,
-0.035660117864608765,
-0.005130918696522713,
-0.039585936814546585,
-0.02803332731127739,
0.08666545897722244,
-0.007666453253477812,
0.004744278732687235,
0.027214735746383667,
-0.02125588431954384,
-... | 0.122275 |
This document describes the concept of VolumeSnapshotClass in Kubernetes. Familiarity with [volume snapshots](/docs/concepts/storage/volume-snapshots/) and [storage classes](/docs/concepts/storage/storage-classes) is suggested. ## Introduction Just like StorageClass provides a way for administrators to describe the "cl... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/volume-snapshot-classes.md | main | kubernetes | [
-0.07718604058027267,
0.04122895747423172,
0.016484834253787994,
-0.046646520495414734,
-0.0239715576171875,
-0.01542690023779869,
-0.0011863675899803638,
-0.009304812178015709,
0.0551392138004303,
0.02162584476172924,
0.009091680869460106,
-0.01883942447602749,
0.08363285660743713,
-0.022... | 0.09558 |
This document describes \_persistent volumes\_ in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/), [StorageClasses](/docs/concepts/storage/storage-classes/) and [VolumeAttributesClasses](/docs/concepts/storage/volume-attributes-classes/) is suggested. ## Introduction Managing storage is a distin... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.04691171646118164,
-0.0012397324899211526,
0.0004473893204703927,
0.029567550867795944,
-0.015583823435008526,
-0.04291233792901039,
0.002636489225551486,
-0.008500384166836739,
0.1074359193444252,
0.01728088967502117,
-0.0265983734279871,
-0.006359395571053028,
0.04816427454352379,
0.0... | 0.165763 |
will always bind that PV to the PVC. Otherwise, the user will always get at least what they asked for, but the volume may be in excess of what was requested. Once bound, PersistentVolumeClaim binds are exclusive, regardless of how they were bound. A PVC to PV binding is a one-to-one mapping, using a ClaimRef which is a... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.03495413810014725,
-0.014167622663080692,
-0.0010966850677505136,
0.016490837559103966,
-0.0009924129117280245,
-0.002503753174096346,
0.05566563084721565,
0.03904799371957779,
0.04933551698923111,
0.018355829641222954,
-0.02375873364508152,
0.010347036644816399,
0.06564030051231384,
-0... | 0.054419 |
claim because the previous claimant's data remains on the volume. An administrator can manually reclaim the volume with the following steps. 1. Delete the PersistentVolume. The associated storage asset in external infrastructure still exists after the PV is deleted. 1. Manually clean up the data on the associated stora... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.039001692086458206,
0.04420461505651474,
0.06090303137898445,
0.016649460420012474,
-0.0028026564978063107,
-0.004642822779715061,
0.02193557843565941,
-0.02630612812936306,
0.09734417498111725,
0.03948246315121651,
0.017916740849614143,
0.006472717970609665,
0.06538711488246918,
0.0579... | 0.012039 |
is replaced by the `external-provisioner.volume.kubernetes.io/finalizer` finalizer. The finalizers ensure that the PV object is removed only after the volume is deleted from the storage backend provided the reclaim policy of the PV is `Delete`. This also ensures that the volume is deleted from storage backend irrespect... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.0327080637216568,
-0.04598035663366318,
0.028357738628983498,
0.024812525138258934,
-0.008202947676181793,
0.032460764050483704,
0.03805650770664215,
-0.01320009957998991,
0.10516183078289032,
0.051086604595184326,
0.0034532102290540934,
-0.01840965822339058,
0.03643301501870155,
-0.001... | 0.043865 |
Ext3, or Ext4. When a volume contains a file system, the file system is only resized when a new Pod is using the PersistentVolumeClaim in `ReadWrite` mode. File system expansion is either done when a Pod is starting up or when a Pod is running and the underlying file system supports online expansion. FlexVolumes (depre... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
0.03002157434821129,
-0.04141787439584732,
0.036893658339977264,
0.042328670620918274,
0.02199736423790455,
-0.008105499669909477,
-0.02827007882297039,
0.08448301255702972,
0.04964451491832733,
0.07609942555427551,
0.016512075439095497,
0.0559115931391716,
-0.04958935081958771,
-0.0313161... | 0.101835 |
current size. {{% /tab %}} {{% /tabs %}} ## Types of Persistent Volumes PersistentVolume types are implemented as plugins. Kubernetes currently supports the following plugins: \* [`csi`](/docs/concepts/storage/volumes/#csi) - Container Storage Interface (CSI) \* [`fc`](/docs/concepts/storage/volumes/#fc) - Fibre Channe... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
0.04293772950768471,
-0.00217609154060483,
-0.012401055544614792,
0.008556047454476357,
0.006185986567288637,
-0.009412290528416634,
-0.04941505938768387,
0.01118744071573019,
0.04161796346306801,
0.03464064374566078,
-0.01542050950229168,
-0.028027338907122612,
0.001751838019117713,
0.040... | 0.15837 |
volume is presented into a Pod as a block device, without any filesystem on it. This mode is useful to provide a Pod the fastest possible way to access a volume, without any filesystem layer between the Pod and the volume. On the other hand, the application running in the Pod must know how to handle a raw block device.... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
0.009065357968211174,
-0.0122861722484231,
0.012820366770029068,
0.02714850939810276,
0.022814041003584862,
-0.032134123146533966,
-0.040239185094833374,
0.026932403445243835,
0.06579332798719406,
0.014623288996517658,
-0.04019763693213463,
0.06803757697343826,
0.015614627860486507,
-0.020... | 0.16746 |
✓ | - | - | | FlexVolume | ✓ | ✓ | depends on the driver | - | | HostPath | ✓ | - | - | - | | iSCSI | ✓ | ✓ | - | - | | NFS | ✓ | ✓ | ✓ | - | | RBD | ✓ | ✓ | - | - | | VsphereVolume | ✓ | - | - (works when Pods are collocated) | - | | PortworxVolume | ✓ | - | ✓ | - | - | ### Class A PV can have a class, which is specif... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.04244323447346687,
0.018631204962730408,
0.012553228996694088,
0.023145904764533043,
0.030029157176613808,
-0.00634338241070509,
-0.018236419185996056,
0.011948703788220882,
0.04503631219267845,
-0.036219291388988495,
0.017642229795455933,
-0.007012306246906519,
0.00797506794333458,
0.0... | 0.11622 |
gate on the following components: - `kube-apiserver` - `kubelet` ### Phase A PersistentVolume will be in one of the following phases: `Available` : a free resource that is not yet bound to a claim `Bound` : the volume is bound to a claim `Released` : the claim has been deleted, but the associated storage resource is no... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.06324465572834015,
-0.001222848310135305,
0.0040314882062375546,
0.028281904757022858,
-0.011967005208134651,
0.010410289280116558,
-0.04151397570967674,
-0.008422251790761948,
0.10042471438646317,
0.01041977945715189,
-0.03211250528693199,
-0.08608987182378769,
-0.006007443182170391,
-... | 0.144253 |
equal to `""` is always interpreted to be requesting a PV with no class, so it can only be bound to PVs with no class (no annotation or one set equal to `""`). A PVC with no `storageClassName` is not quite the same and is treated differently by the cluster, depending on whether the [`DefaultStorageClass` admission plug... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.013953259214758873,
-0.005590703338384628,
0.026804175227880478,
0.021931402385234833,
-0.008150779642164707,
0.041067998856306076,
0.0401134118437767,
-0.030594071373343468,
0.07484997063875198,
0.03326737508177757,
0.0325809083878994,
-0.02270379103720188,
0.00180589419323951,
0.02756... | 0.065113 |
Volumes Pods access storage by using the claim as a volume. Claims must exist in the same namespace as the Pod using the claim. The cluster finds the claim in the Pod's namespace and uses it to get the PersistentVolume backing the claim. The volume is then mounted to the host and into the Pod. ```yaml apiVersion: v1 ki... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.020014328882098198,
-0.018892765045166016,
-0.0027838738169521093,
0.05517375469207764,
0.07966100424528122,
-0.049224723130464554,
-0.016956990584731102,
0.02879817970097065,
0.0952400267124176,
0.04628467559814453,
-0.00078868173295632,
0.0032802573405206203,
0.0436059944331646,
0.042... | 0.13324 |
FAQ](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md). ### Create a PersistentVolumeClaim from a Volume Snapshot {#create-persistent-volume-claim-from-volume-snapshot} ```yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: name: restore-pvc spec: storageClassName: csi-hostpath... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.056731224060058594,
-0.04478543624281883,
-0.011337199248373508,
-0.0281215850263834,
-0.02191065065562725,
-0.006527742370963097,
-0.024453721940517426,
0.004912511445581913,
0.07508834451436996,
0.04524778202176094,
0.02922101505100727,
-0.042157553136348724,
0.03724701330065727,
0.01... | 0.086027 |
and newer controllers are able to interoperate because the fields are the same. ### Using volume populators Volume populators are {{< glossary\_tooltip text="controllers" term\_id="controller" >}} that can create non-empty volumes, where the contents of the volume are determined by a Custom Resource. Users create a pop... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.063026562333107,
-0.10993858426809311,
-0.04111479967832565,
-0.022633502259850502,
-0.03568706661462784,
-0.046349313110113144,
0.024692479521036148,
0.023212533444166183,
0.10236574709415436,
0.0278153158724308,
0.02154865860939026,
-0.060959767550230026,
0.05876948684453964,
0.012527... | 0.002893 |
more about [Creating a PersistentVolume](/docs/tasks/configure-pod-container/configure-persistent-volume-storage/#create-a-persistentvolume). \* Learn more about [Creating a PersistentVolumeClaim](/docs/tasks/configure-pod-container/configure-persistent-volume-storage/#create-a-persistentvolumeclaim). \* Read the [Pers... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.04323768615722656,
-0.0007839694153517485,
0.009562451392412186,
0.014552820473909378,
-0.052004773169755936,
-0.0030314638279378414,
-0.03707180917263031,
0.056212328374385834,
0.07339474558830261,
0.03384678065776825,
-0.028191519901156425,
0.010194577276706696,
0.04753011837601662,
0... | 0.119035 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.