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 |
|---|---|---|---|---|---|
container runtime garbage collection, intermitted connectivity issues with the control plane may cause the state loss and containers may be re-run even when you expect a container not to be restarted. #### Restart All Containers {#restart-all-containers} {{< feature-state feature\_gate\_name="RestartAllContainersOnCont... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-lifecycle.md | main | kubernetes | [
0.05460655316710472,
-0.028335759416222572,
0.04745912179350853,
0.0760674998164177,
0.0007901045610196888,
0.007130815647542477,
-0.011105464771389961,
-0.06143423169851303,
0.013422378338873386,
0.0355805829167366,
-0.022259628400206566,
0.03134635090827942,
-0.03625481575727463,
-0.0163... | 0.156167 |
start retries from the default of 300s (5 minutes). This configuration is set per node using kubelet configuration. In your [kubelet configuration](/docs/tasks/administer-cluster/kubelet-config-file/), under `crashLoopBackOff` set the `maxContainerRestartPeriod` field between `"1s"` and `"300s"`. As described above in ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-lifecycle.md | main | kubernetes | [
0.04338422417640686,
-0.02309797890484333,
0.04157433286309242,
-0.006008306052535772,
-0.07123745232820511,
0.010087663307785988,
-0.0583222433924675,
-0.003254022216424346,
0.061714183539152145,
0.010667822323739529,
-0.020012326538562775,
-0.03393363207578659,
-0.014232342131435871,
-0.... | 0.129468 |
ready: true ... ``` The Pod conditions you add must have names that meet the Kubernetes [label key format](/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set). ### Status for Pod readiness {#pod-readiness-status} The `kubectl patch` command does not support patching object status. To set thes... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-lifecycle.md | main | kubernetes | [
-0.008224417455494404,
0.017804695293307304,
0.08437848091125488,
-0.02310597151517868,
-0.05909410119056702,
-0.002933003008365631,
0.051890864968299866,
-0.043056245893239975,
0.012136202305555344,
0.08505105972290039,
0.009703156538307667,
-0.10200218856334686,
-0.014327931217849255,
-0... | 0.111646 |
the Pod's desired state using the `/resize` subresource. The kubelet then attempts to apply the new resource values to the running containers. The Pod {{< glossary\_tooltip text="conditions" term\_id="condition" >}} `PodResizePending` and `PodResizeInProgress` (described in [Pod conditions](#pod-conditions)) indicate t... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-lifecycle.md | main | kubernetes | [
0.019705755636096,
0.049771081656217575,
0.04451846703886986,
0.015960801392793655,
-0.05471411347389221,
-0.019187135621905327,
0.019223693758249283,
0.03873363882303238,
0.0019963651429861784,
0.03930101916193962,
-0.030152736231684685,
-0.007177671417593956,
-0.02464648336172104,
-0.010... | 0.134146 |
(no action should be taken, and the kubelet will make further checks). ### Types of probe The kubelet can optionally perform and react to three kinds of probes on running containers: `livenessProbe` : Indicates whether the container is running. If the liveness probe fails, the kubelet kills the container, and the conta... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-lifecycle.md | main | kubernetes | [
0.0032880129292607307,
0.023407235741615295,
0.05312487855553627,
0.010714635252952576,
0.00846769753843546,
0.0005206226487644017,
0.022196751087903976,
-0.06472867727279663,
0.08223110437393188,
0.03834917023777962,
0.020039711147546768,
-0.06492317467927933,
-0.04130048304796219,
-0.014... | 0.165849 |
`ready` condition will be set to `false`, so load balancers will not use the Pod for regular traffic. See [Pod termination](#pod-termination) for more information about how the kubelet handles Pod deletion. {{< /note >}} #### When should you use a startup probe? Startup probes are useful for Pods that have containers t... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-lifecycle.md | main | kubernetes | [
-0.007319067604839802,
0.02165163680911064,
0.03616243973374367,
0.007771884556859732,
-0.030766550451517105,
-0.03772827982902527,
-0.048180799931287766,
-0.022632887586951256,
0.05190778896212578,
0.028982723131775856,
0.00006274785118876025,
-0.029801122844219208,
-0.03856174275279045,
... | 0.136609 |
and SIGKILL as valid signals. Here is an example Pod spec defining a custom stop signal: ```yaml spec: os: name: linux containers: - name: my-container image: container-image:latest lifecycle: stopSignal: SIGUSR1 ``` If a stop signal is defined in the lifecycle, this will override the signal defined in the container im... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-lifecycle.md | main | kubernetes | [
0.022765809670090675,
0.016744311898946762,
0.08784399926662445,
-0.022043611854314804,
0.04593709111213684,
-0.050414908677339554,
-0.007780125364661217,
-0.029553433880209923,
0.10622913390398026,
0.026715056970715523,
0.010290263220667839,
0.016902653500437737,
-0.046138275414705276,
-0... | 0.20552 |
period expires, if there is still any container running in the Pod, the kubelet triggers forcible shutdown. The container runtime sends `SIGKILL` to any processes still running in any container in the Pod. The kubelet also cleans up a hidden `pause` container if that container runtime uses one. 1. The kubelet transitio... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-lifecycle.md | main | kubernetes | [
0.023510782048106194,
0.043082110583782196,
0.09045454114675522,
0.021429358050227165,
0.03203398361802101,
-0.03007945790886879,
-0.03068818338215351,
-0.06923716515302658,
0.15527990460395813,
0.005734835285693407,
0.002704402431845665,
0.026023857295513153,
-0.030461939051747322,
-0.046... | 0.195579 |
garbage collector (PodGC), which is a controller in the control plane, cleans up terminated Pods (with a phase of `Succeeded` or `Failed`), when the number of Pods exceeds the configured threshold (determined by `terminated-pod-gc-threshold` in the kube-controller-manager). This avoids a resource leak as Pods are creat... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-lifecycle.md | main | kubernetes | [
0.00992458313703537,
0.0006434593815356493,
0.0737946406006813,
0.03335651382803917,
0.07299241423606873,
-0.054701633751392365,
0.02635706216096878,
-0.028008123859763145,
0.10530592501163483,
0.06582242995500565,
0.021604543551802635,
0.004254902247339487,
-0.020469939336180687,
-0.04669... | 0.213778 |
for Pod. | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-lifecycle.md | main | kubernetes | [
-0.0011320862686261535,
0.053603120148181915,
0.0491311140358448,
0.0028420444577932358,
0.028609411790966988,
0.01047702506184578,
0.05676950886845589,
-0.03679615631699562,
-0.0029136519879102707,
0.022748032584786415,
0.04045220836997032,
0.09653041511774063,
-0.05391965061426163,
-0.02... | 0.244081 |
This guide is for application owners who want to build highly available applications, and thus need to understand what types of disruptions can happen to Pods. It is also for cluster administrators who want to perform automated cluster actions, like upgrading and autoscaling clusters. ## Voluntary and involuntary disru... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/disruptions.md | main | kubernetes | [
0.0347367525100708,
0.0045921895653009415,
0.08452867716550827,
0.03397563844919205,
0.09077279269695282,
-0.028768867254257202,
0.043068449944257736,
0.042418524622917175,
0.042984120547771454,
0.073126420378685,
0.04036038741469383,
-0.009027146734297276,
0.03399871289730072,
-0.05369273... | 0.238033 |
of a replicated application that are down simultaneously from voluntary disruptions. For example, a quorum-based application would like to ensure that the number of replicas running is never brought below the number needed for a quorum. A web front end might want to ensure that the number of replicas serving load never... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/disruptions.md | main | kubernetes | [
-0.012081630527973175,
-0.022486336529254913,
0.0348811149597168,
-0.0037816816475242376,
-0.0051783546805381775,
-0.0622575618326664,
-0.07030725479125977,
-0.011090482585132122,
0.09729572385549545,
0.04529054835438728,
-0.006736353505402803,
0.02178683876991272,
0.033350855112075806,
-0... | 0.216039 |
administrator first tries to drain `node-1` using the `kubectl drain` command. That tool tries to evict `pod-a` and `pod-x`. This succeeds immediately. Both pods go into the `terminating` state at the same time. This puts the cluster in this state: | node-1 \*draining\* | node-2 | node-3 | |:--------------------:|:----... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/disruptions.md | main | kubernetes | [
-0.0002306175447301939,
0.021815890446305275,
0.0656915232539177,
0.04973527044057846,
0.023747721686959267,
-0.056469161063432693,
-0.007547349669039249,
-0.03536965698003769,
0.042709123343229294,
0.0632142424583435,
0.06420842558145523,
-0.02909778617322445,
0.00273272767663002,
-0.0506... | 0.167487 |
For more information, see [Pod priority preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/). `DeletionByTaintManager` : Pod is due to be deleted by Taint Manager (which is part of the node lifecycle controller within `kube-controller-manager`) due to a `NoExecute` taint that the Pod does not tolera... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/disruptions.md | main | kubernetes | [
0.01895950920879841,
0.05564858391880989,
0.05725724995136261,
0.019054565578699112,
0.06650759279727936,
-0.02465590462088585,
-0.005029015708714724,
-0.046664122492074966,
0.09961868822574615,
0.06873349845409393,
0.03851694613695145,
0.020518742501735687,
-0.04459940269589424,
-0.020660... | 0.180896 |
This page covers advanced Pod configuration topics including [PriorityClasses](#priorityclasses), [RuntimeClasses](#runtimeclasses), [security context](#security-context) within Pods, and introduces aspects of [scheduling](/docs/concepts/scheduling-eviction/#scheduling). ## PriorityClasses \_PriorityClasses\_ allow you... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/advanced-pod-config.md | main | kubernetes | [
-0.028471186757087708,
0.029623588547110558,
0.09047501534223557,
0.05219363793730736,
-0.023709604516625404,
-0.0304365586489439,
0.008900614455342293,
-0.05089212954044342,
0.03268234431743622,
0.05731352046132088,
-0.047022879123687744,
-0.05200270190834999,
-0.05936800315976143,
0.0195... | 0.085107 |
drop Linux capabilities - \*\*Seccomp Profiles\*\*: Set security computing profiles - \*\*SELinux Options\*\*: Configure SELinux context - \*\*AppArmor\*\*: Configure AppArmor profiles for additional access control - \*\*Windows Options\*\*: Configure Windows-specific security settings {{< caution >}} You can also use ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/advanced-pod-config.md | main | kubernetes | [
0.0800900012254715,
0.061769161373376846,
-0.03849317505955696,
-0.014269986189901829,
0.029327191412448883,
-0.0020306999795138836,
0.03776243329048157,
0.06623823940753937,
-0.049354299902915955,
-0.025043930858373642,
-0.0004701717698480934,
-0.0900585949420929,
0.018758272752165794,
0.... | 0.130725 |
This page explains how to set a Pod's hostname, potential side effects after configuration, and the underlying mechanics. ## Default Pod hostname When a Pod is created, its hostname (as observed from within the Pod) is derived from the Pod's metadata.name value. Both the hostname and its corresponding fully qualified d... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-hostname.md | main | kubernetes | [
0.043311502784490585,
-0.007065237499773502,
0.0476507693529129,
0.005156680941581726,
-0.032753728330135345,
-0.07709100842475891,
-0.004096002317965031,
0.002972664777189493,
0.06002439931035042,
0.04748064652085304,
-0.018201377242803574,
-0.039668530225753784,
-0.0024114360567182302,
-... | 0.107347 |
command: - sleep - "3600" name: busybox ``` {{< note >}} This only affects the hostname within the Pod; it does not affect the Pod's A or AAAA records in the cluster DNS server. {{< /note >}} If `hostnameOverride` is set alongside `hostname` and `subdomain` fields: \* The hostname inside the Pod is overridden to the `h... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-hostname.md | main | kubernetes | [
-0.00679620448499918,
-0.017858512699604034,
0.07382369041442871,
0.05195675045251846,
-0.0690789446234703,
-0.05155816301703453,
-0.06719686090946198,
-0.09996573626995087,
0.06946711242198944,
0.060237858444452286,
-0.04119916632771492,
-0.009313015267252922,
-0.04021169990301132,
-0.048... | 0.132391 |
This page introduces \_Quality of Service (QoS) classes\_ in Kubernetes, and explains how Kubernetes assigns a QoS class to each Pod as a consequence of the resource constraints that you specify for the containers in that Pod. Kubernetes relies on this classification to make decisions about which Pods to evict when the... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-qos.md | main | kubernetes | [
-0.05051825940608978,
0.018579958006739616,
0.059937842190265656,
-0.010212619788944721,
0.025544246658682823,
-0.033607397228479385,
0.10348287969827652,
-0.0827324390411377,
0.08157096058130264,
0.0022292081266641617,
-0.04420900344848633,
-0.011588545516133308,
0.012169559486210346,
0.0... | 0.206674 |
request or limit, or the Pod has a Pod-level memory or CPU request or limit. ### BestEffort Pods in the `BestEffort` QoS class can use node resources that aren't specifically assigned to Pods in other QoS classes. For example, if you have a node with 16 CPU cores available to the kubelet, and you assign 4 CPU cores to ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-qos.md | main | kubernetes | [
0.03861892968416214,
0.017297258600592613,
0.0071283262223005295,
0.008390191942453384,
0.037855785340070724,
-0.006107942666858435,
0.008048283867537975,
0.017754539847373962,
0.044636864215135574,
0.03147884085774422,
-0.011618154123425484,
0.01770922914147377,
-0.024854302406311035,
-0.... | 0.237984 |
Containers](/docs/concepts/configuration/manage-resources-containers/). \* Learn about [Node-pressure eviction](/docs/concepts/scheduling-eviction/node-pressure-eviction/). \* Learn about [Pod priority and preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/). \* Learn about [Pod disruptions](/docs/c... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/pod-qos.md | main | kubernetes | [
0.04289921373128891,
0.022734439000487328,
-0.01717212051153183,
0.03628183528780937,
0.001820635749027133,
-0.040969762951135635,
0.01923934556543827,
0.013964561745524406,
-0.08675973862409592,
0.03490510210394859,
0.025529760867357254,
0.02277470752596855,
-0.055705610662698746,
-0.0466... | 0.241318 |
This page provides an overview of init containers: specialized containers that run before app containers in a {{< glossary\_tooltip text="Pod" term\_id="pod" >}}. Init containers can contain utilities or setup scripts not present in an app image. You can specify init containers in the Pod specification alongside the `c... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/init-containers.md | main | kubernetes | [
-0.0257529579102993,
0.024515455588698387,
0.0991554781794548,
0.003031012834981084,
0.03674572706222534,
-0.030812598764896393,
0.05289420858025551,
-0.015410257503390312,
0.038635123521089554,
0.01770261861383915,
0.021816972643136978,
-0.020883090794086456,
-0.018155528232455254,
-0.053... | 0.152746 |
an image `FROM` another image just to use a tool like `sed`, `awk`, `python`, or `dig` during setup. \* The application image builder and deployer roles can work independently without the need to jointly build a single app image. \* Init containers can run with a different view of the filesystem than app containers in ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/init-containers.md | main | kubernetes | [
-0.11254831403493881,
0.05343703553080559,
0.07111099362373352,
0.0029690354131162167,
0.049938514828681946,
-0.0943964421749115,
0.05326360836625099,
-0.01743447780609131,
0.034690771251916885,
0.023274803534150124,
0.06273144483566284,
-0.039787210524082184,
0.05668700486421585,
-0.02840... | 0.063038 |
16s 1 {kubelet 172.17.4.201} spec.initContainers{init-myservice} Normal Pulling pulling image "busybox" 13s 13s 1 {kubelet 172.17.4.201} spec.initContainers{init-myservice} Normal Pulled Successfully pulled image "busybox" 13s 13s 1 {kubelet 172.17.4.201} spec.initContainers{init-myservice} Normal Created Created conta... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/init-containers.md | main | kubernetes | [
0.04142926633358002,
0.016445687040686607,
0.03843763843178749,
-0.02727345936000347,
0.028533650562167168,
-0.08276262134313583,
0.015427278354763985,
-0.024392632767558098,
0.045748576521873474,
0.04430273547768593,
0.05651849880814552,
-0.0682014524936676,
-0.03037002868950367,
-0.00486... | 0.119489 |
if teams deploy their application as a Job, because `activeDeadlineSeconds` has an effect even after initContainer finished. The Pod which is already running correctly would be killed by `activeDeadlineSeconds` if you set. The name of each app and init container in a Pod must be unique; a validation error is thrown for... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/init-containers.md | main | kubernetes | [
-0.0450945645570755,
0.032288528978824615,
-0.02028920128941536,
0.006974483374506235,
0.023056596517562866,
-0.06998085230588913,
0.021702367812395096,
-0.025727152824401855,
0.0253963153809309,
0.034545619040727615,
0.010361202992498875,
0.02900414727628231,
0.014627124182879925,
0.01909... | 0.212344 |
{{< feature-state state="stable" for\_k8s\_version="v1.25" >}} This page provides an overview of ephemeral containers: a special type of container that runs temporarily in an existing {{< glossary\_tooltip term\_id="pod" >}} to accomplish user-initiated actions such as troubleshooting. You use ephemeral containers to i... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/ephemeral-containers.md | main | kubernetes | [
-0.04065050557255745,
0.028419844806194305,
0.12896226346492767,
-0.000023684866391704418,
0.0006271390011534095,
0.00188967096619308,
0.048808373510837555,
-0.025280075147747993,
0.03535927087068558,
0.035939693450927734,
0.013428429141640663,
-0.06753048300743103,
-0.026658646762371063,
... | 0.085297 |
\_Pods\_ are the smallest deployable units of computing that you can create and manage in Kubernetes. A \_Pod\_ (as in a pod of whales or pea pod) is a group of one or more {{< glossary\_tooltip text="containers" term\_id="container" >}}, with shared storage and network resources, and a specification for how to run the... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/_index.md | main | kubernetes | [
0.01725844293832779,
-0.010631612502038479,
0.06035918742418289,
0.007600277662277222,
0.005533927120268345,
-0.04828968644142151,
0.021883489564061165,
-0.010149500332772732,
0.10072126239538193,
0.05081338435411453,
0.014572559855878353,
-0.04307670518755913,
-0.013371780514717102,
-0.05... | 0.219858 |
created and managed as a group by a workload resource and its {{< glossary\_tooltip text="controller" term\_id="controller" >}}. See [Pods and controllers](#pods-and-controllers) for more information on how Kubernetes uses workload resources, and their controllers, to implement application scaling and auto-healing. Pod... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/_index.md | main | kubernetes | [
-0.03521762788295746,
-0.05741447955369949,
0.045955296605825424,
0.07475052773952484,
-0.011724154464900494,
-0.0299094058573246,
0.05869073048233986,
-0.054497551172971725,
0.11071460694074631,
0.06919912993907928,
0.03134880214929581,
-0.031767357140779495,
0.010925856418907642,
-0.0380... | 0.156347 |
the entire group at once. ### Pod templates Controllers for {{< glossary\_tooltip text="workload" term\_id="workload" >}} resources create Pods from a \_pod template\_ and manage those Pods on your behalf. PodTemplates are specifications for creating Pods, and are included in workload resources such as [Deployments](/d... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/_index.md | main | kubernetes | [
-0.030911317095160484,
-0.013948324136435986,
0.022410200908780098,
0.03476780280470848,
-0.020320171490311623,
-0.017784923315048218,
0.04824550449848175,
-0.022065700963139534,
0.0402333103120327,
0.02458951808512211,
0.010965665802359581,
-0.05825674161314964,
-0.048566315323114395,
-0.... | 0.115432 |
`resize` subresource allows container resources (`spec.containers[\*].resources`) to be updated. See [Resize Container Resources](/docs/tasks/configure-pod-container/resize-container-resources/) for more details. - \*\*Ephemeral Containers:\*\* The `ephemeralContainers` subresource allows {{< glossary\_tooltip text="ep... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/_index.md | main | kubernetes | [
-0.03921302407979965,
0.028793442994356155,
0.03974538296461105,
0.03229215741157532,
-0.0260907094925642,
-0.019566800445318222,
0.04877166077494621,
0.008076915517449379,
0.0073774284683167934,
0.04205639287829399,
-0.02446821704506874,
-0.03718499839305878,
-0.04530853033065796,
-0.0606... | 0.120168 |
shares the network namespace, including the IP address and network ports. Inside a Pod (and \*\*only\*\* then), the containers that belong to the Pod can communicate with one another using `localhost`. When containers in a Pod communicate with entities \*outside the Pod\*, they must coordinate how they use the shared n... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/_index.md | main | kubernetes | [
0.06649810820817947,
-0.02302348054945469,
0.02423456497490406,
-0.001308131730183959,
-0.003934219479560852,
-0.025928646326065063,
0.004158463329076767,
-0.016358288004994392,
0.07687751203775406,
0.004487057216465473,
-0.0269212294369936,
0.0017768011894077063,
0.005930477753281593,
-0.... | 0.209109 |
observing them. Whereas most Pods are managed by the control plane (for example, a {{< glossary\_tooltip text="Deployment" term\_id="deployment" >}}), for static Pods, the kubelet directly supervises each static Pod (and restarts it if it fails). Static Pods are always bound to one {{< glossary\_tooltip term\_id="kubel... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/_index.md | main | kubernetes | [
0.004913679789751768,
-0.04403143748641014,
0.07977007329463959,
0.02917594462633133,
-0.04784763976931572,
-0.024973342195153236,
0.002556832740083337,
-0.03431600332260132,
0.1062682569026947,
0.049606118351221085,
-0.008860397152602673,
-0.07362814247608185,
0.0025996663607656956,
-0.05... | 0.146497 |
diagnostic, the kubelet can invoke different actions: - `ExecAction` (performed with the help of the container runtime) - `TCPSocketAction` (checked directly by the kubelet) - `HTTPGetAction` (checked directly by the kubelet) You can read more about [probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/pods/_index.md | main | kubernetes | [
0.008221885189414024,
0.0298667810857296,
0.050515756011009216,
0.027347231283783913,
-0.017093833535909653,
-0.0318252295255661,
-0.002684471197426319,
0.0060816192999482155,
0.07459435611963272,
0.021393120288848877,
-0.024934617802500725,
-0.04063258320093155,
-0.036217402666807175,
-0.... | 0.264849 |
In Kubernetes, a \_HorizontalPodAutoscaler\_ automatically updates a workload resource (such as a {{< glossary\_tooltip text="Deployment" term\_id="deployment" >}} or {{< glossary\_tooltip text="StatefulSet" term\_id="statefulset" >}}), with the aim of automatically scaling capacity to match demand. Horizontal scaling ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale.md | main | kubernetes | [
-0.021046524867415428,
0.006336533464491367,
0.05203865095973015,
0.007941650226712227,
-0.08087258785963058,
-0.03646422177553177,
-0.00014893956540618092,
-0.004202910233289003,
0.07383473962545395,
0.03039284609258175,
-0.008343575522303581,
0.0009879992576316,
0.0015658256597816944,
-0... | 0.132501 |
with raw values, not utilization values. - For object metrics and external metrics, a single metric is fetched, which describes the object in question. This metric is compared to the target value, to produce a ratio as above. In the `autoscaling/v2` API version, this value can optionally be divided by the number of Pod... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale.md | main | kubernetes | [
-0.00689772330224514,
-0.03273424878716469,
-0.014294621534645557,
0.05376632139086723,
-0.07932968437671661,
-0.03032856620848179,
-0.016144225373864174,
0.04436233639717102,
0.05288349464535713,
-0.019451556727290154,
-0.016128897666931152,
-0.14342451095581055,
-0.026313653215765953,
0.... | 0.157989 |
\\( currentMetricValue \over desiredMetricValue \\) base scale ratio is then calculated, using the remaining pods not set aside or discarded from above. If there were any missing metrics, the control plane recomputes the average more conservatively, assuming those pods were consuming 100% of the desired value in case o... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale.md | main | kubernetes | [
0.00677333353087306,
-0.035918641835451126,
-0.01732824370265007,
0.0802977904677391,
0.017159633338451385,
0.0089572723954916,
-0.06228527054190636,
0.05501437932252884,
0.08330891281366348,
0.07463786005973816,
0.09150348603725433,
-0.018520552664995193,
0.016131334006786346,
-0.04680546... | 0.096253 |
a Pod rapidly toggles between `Ready` and `Unready`, metrics are ignored until it’s considered stably `Ready`. ### Good practice for pod readiness {#pod-readiness-good-practices} - Configure a `startupProbe` that doesn't pass until the high CPU usage has passed, or - Ensure your `readinessProbe` only reports `Ready` \*... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale.md | main | kubernetes | [
0.011931675486266613,
-0.03124304860830307,
0.052365221083164215,
0.06705353409051895,
-0.024870671331882477,
-0.03633255511522293,
-0.05962522700428963,
-0.002269246382638812,
0.04603534936904907,
0.04276532679796219,
-0.0038870915304869413,
-0.0142727205529809,
-0.07699869573116302,
-0.0... | 0.19358 |
configure scaling thresholds for the containers that matter most in a particular Pod. For example, if you have a web application and a sidecar container that provides logging, you can scale based on the resource use of the web application, ignoring the sidecar container and its resource use. If you revise the target re... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale.md | main | kubernetes | [
0.019053444266319275,
0.033898234367370605,
-0.018415939062833786,
0.02609301544725895,
-0.008292829617857933,
-0.08787218481302261,
-0.009660805575549603,
0.040432605892419815,
-0.04101492837071419,
-0.01038308348506689,
-0.018869338557124138,
-0.07117689400911331,
-0.058248065412044525,
... | 0.080815 |
`external.metrics.k8s.io` [API](/docs/reference/external-api/external-metrics.v1beta1/). It may be provided by the custom metrics adapters provided above. For more information on these different metrics paths and how they differ please see the relevant design proposals for [the HPA V2](https://git.k8s.io/design-proposa... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale.md | main | kubernetes | [
-0.07828186452388763,
-0.04795440286397934,
-0.03852666914463043,
-0.000676831288728863,
-0.05828969553112984,
-0.026869414374232292,
-0.05624477192759514,
0.10559525340795517,
0.04587428644299507,
-0.054372984915971756,
-0.0004221807175781578,
-0.058684222400188446,
-0.04483043774962425,
... | 0.180374 |
the target should be scaled down the algorithm looks into previously computed desired states, and uses the highest value from the specified interval. In the above example, all desired states from the past 5 minutes will be considered. This approximates a rolling maximum, and avoids having the scaling algorithm frequent... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale.md | main | kubernetes | [
0.015862921252846718,
0.008073078468441963,
-0.037973787635564804,
0.003925842233002186,
-0.03492172062397003,
-0.044443659484386444,
-0.0361897237598896,
0.04527835175395012,
-0.008793570101261139,
-0.039299946278333664,
0.0003703781112562865,
-0.015856262296438217,
-0.014471860602498055,
... | 0.136708 |
scaling the given direction. So to prevent downscaling the following policy would be used: ```yaml behavior: scaleDown: selectPolicy: Disabled ``` ## Support for HorizontalPodAutoscaler in kubectl HorizontalPodAutoscaler, like every API resource, is supported in a standard way by `kubectl`. You can create a new autosca... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale.md | main | kubernetes | [
-0.030304986983537674,
0.03965264558792114,
0.05098859220743179,
-0.00799906998872757,
-0.10504335910081863,
-0.07750110328197479,
-0.04522555321455002,
0.002588608069345355,
0.0004231645434629172,
0.03538280725479126,
-0.0016364582115784287,
-0.040852271020412445,
-0.04676228016614914,
-0... | 0.116009 |
documentation for [`kubectl autoscale`](/docs/reference/generated/kubectl/kubectl-commands/#autoscale). - If you would like to write your own custom metrics adapter, check out the [boilerplate](https://github.com/kubernetes-sigs/custom-metrics-apiserver) to get started. - Read the [API reference](/docs/reference/kubern... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale.md | main | kubernetes | [
0.020694486796855927,
-0.010148578323423862,
0.027176789939403534,
-0.03268555924296379,
-0.11368420720100403,
-0.0008597050909884274,
-0.027194054797291756,
0.0666840448975563,
0.025367816910147667,
0.004775614477694035,
-0.025424739345908165,
-0.06079631671309471,
-0.031608108431100845,
... | 0.120842 |
In Kubernetes, a \_VerticalPodAutoscaler\_ automatically updates a workload management {{< glossary\_tooltip text="resource" term\_id="api-resource" >}} (such as a {{< glossary\_tooltip text="Deployment" term\_id="deployment" >}} or {{< glossary\_tooltip text="StatefulSet" term\_id="statefulset" >}}), with the aim of a... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/autoscaling/vertical-pod-autoscale.md | main | kubernetes | [
-0.05542536824941635,
0.024758324027061462,
0.0793326124548912,
0.02906484343111515,
-0.07736480236053467,
-0.05267370119690895,
0.05007140710949898,
-0.036715127527713776,
0.08310655504465103,
0.030738383531570435,
-0.0281054750084877,
-0.028336884453892708,
-0.012129967100918293,
-0.0241... | 0.115032 |
triggering their recreation with new resource requests (traditional approach) - Update Pod resources in place without eviction, when the cluster supports in-place Pod resource updates The chosen method depends on the configured update mode, cluster capabilities, and the type of resource change needed. In-place updates,... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/autoscaling/vertical-pod-autoscale.md | main | kubernetes | [
-0.005970560014247894,
-0.04171227291226387,
0.05357612669467926,
0.014217001385986805,
0.03646448627114296,
-0.0539461150765419,
0.01461960468441248,
-0.034444574266672134,
0.05864652991294861,
0.07698101550340652,
0.03135737404227257,
0.023124143481254578,
0.01866750232875347,
-0.0579656... | 0.170041 |
strategies. ## Resource policies Resource policies allow you to fine-tune how the VerticalPodAutoscaler generates recommendations and applies updates. You can set boundaries for resource recommendations, specify which resources to manage, and configure different policies for individual containers within a Pod. You defi... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/autoscaling/vertical-pod-autoscale.md | main | kubernetes | [
-0.00604008324444294,
0.04123681038618088,
-0.004216442815959454,
-0.003120180917903781,
-0.006851102691143751,
-0.03171920031309128,
-0.044428762048482895,
0.031707312911748886,
0.0052787065505981445,
0.028934389352798462,
-0.016869405284523964,
0.0009708883007988334,
0.02179253101348877,
... | 0.083674 |
{{< feature-state for\_k8s\_version="v1.23" state="stable" >}} When your Job has finished, it's useful to keep that Job in the API (and not immediately delete the Job) so that you can tell whether the Job succeeded or failed. Kubernetes' TTL-after-finished {{}} provides a TTL (time to live) mechanism to limit the lifet... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/ttlafterfinished.md | main | kubernetes | [
-0.030547553673386574,
0.02330128662288189,
0.07075488567352295,
0.00881022959947586,
-0.020693190395832062,
0.00874380487948656,
-0.03790011256933212,
-0.06236384063959122,
0.07994340360164642,
0.019413968548178673,
-0.03196224197745323,
0.015388159081339836,
-0.03793209418654442,
0.00539... | 0.110384 |
{{< feature-state for\_k8s\_version="v1.21" state="stable" >}} A \_CronJob\_ creates {{< glossary\_tooltip term\_id="job" text="Jobs" >}} on a repeating schedule. CronJob is meant for performing regular scheduled actions such as backups, report generation, and so on. One CronJob object is like one line of a \_crontab\_... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/cron-jobs.md | main | kubernetes | [
-0.14827324450016022,
-0.02018497884273529,
-0.01707279309630394,
0.01588079333305359,
-0.04506261646747589,
-0.011287172324955463,
0.055101849138736725,
-0.05439237505197525,
0.006005927454680204,
-0.006755684036761522,
-0.023312905803322792,
-0.030763961374759674,
0.020427091047167778,
-... | 0.170342 |
\* \* | | @weekly | Run once a week at midnight on Sunday morning | 0 0 \* \* 0 | | @daily (or @midnight) | Run once a day at midnight | 0 0 \* \* \* | | @hourly | Run once an hour at the beginning of the hour | 0 \* \* \* \* | To generate CronJob schedule expressions, you can also use web tools like [crontab.guru](htt... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/cron-jobs.md | main | kubernetes | [
-0.1562274694442749,
0.029150431975722313,
-0.02447040192782879,
0.04477269947528839,
-0.0648433268070221,
0.015136150643229485,
-0.03606727346777916,
-0.035401761531829834,
-0.07944116741418839,
-0.010480571538209915,
-0.05649982765316963,
-0.07887174934148788,
0.006277607288211584,
0.038... | 0.000837 |
the CronJob controller does not start the Jobs to run the tasks) until you unsuspend the CronJob. {{< caution >}} Executions that are suspended during their scheduled time count as missed Jobs. When `.spec.suspend` changes from `true` to `false` on an existing CronJob without a [starting deadline](#starting-deadline), ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/cron-jobs.md | main | kubernetes | [
-0.10399635881185532,
0.011744119226932526,
0.0018497096607461572,
0.06643515080213547,
0.04002100229263306,
0.025648005306720734,
-0.0471733920276165,
-0.012859368696808815,
-0.08818628638982773,
-0.008414961397647858,
-0.00007257991092046723,
-0.018327997997403145,
0.008131899870932102,
... | 0.013707 |
If there are more than 100 missed schedules, then it does not start the Job and logs the error. ``` too many missed start times. Set or decrease .spec.startingDeadlineSeconds or check clock skew ``` This behavior is applicable for catch-up scheduling and does not mean the CronJob will stop running. For example, when us... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/cron-jobs.md | main | kubernetes | [
-0.08584725856781006,
-0.044584669172763824,
-0.05533508211374283,
0.03813573718070984,
0.013788901269435883,
0.0034356594551354647,
-0.016588760539889336,
-0.020741097629070282,
0.04622603952884674,
0.01813783496618271,
0.043735604733228683,
-0.04387614130973816,
0.024917444214224815,
-0.... | 0.025621 |
A \_DaemonSet\_ ensures that all (or some) Nodes run a copy of a Pod. As nodes are added to the cluster, Pods are added to them. As nodes are removed from the cluster, those Pods are garbage collected. Deleting a DaemonSet will clean up the Pods it created. Some typical uses of a DaemonSet are: - running a cluster stor... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/daemonset.md | main | kubernetes | [
-0.0330006368458271,
0.02824706770479679,
0.013907836750149727,
0.027511542662978172,
0.04049254208803177,
-0.038595639169216156,
0.013445096090435982,
-0.012991932220757008,
0.08913913369178772,
0.032226551324129105,
-0.000689104781486094,
0.012195250019431114,
0.01069599948823452,
-0.087... | 0.227909 |
adds the `spec.affinity.nodeAffinity` field of the Pod to match the target host. After the Pod is created, the default scheduler typically takes over and then binds the Pod to the target host by setting the `.spec.nodeName` field. If the new Pod cannot fit on the node, the default scheduler may preempt (evict) some of ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/daemonset.md | main | kubernetes | [
-0.0004736102418974042,
0.0022806550841778517,
0.030843792483210564,
0.05819001793861389,
0.03727862983942032,
-0.036922551691532135,
-0.020473847165703773,
-0.01390128955245018,
-0.004861032124608755,
0.0089576356112957,
-0.011682447977364063,
-0.002374703297391534,
-0.039092157036066055,
... | 0.122603 |
They do not have clients. - \*\*NodeIP and Known Port\*\*: Pods in the DaemonSet can use a `hostPort`, so that the pods are reachable via the node IPs. Clients know the list of node IPs somehow, and know the port by convention. - \*\*DNS\*\*: Create a [headless service](/docs/concepts/services-networking/service/#headl... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/daemonset.md | main | kubernetes | [
-0.035475198179483414,
-0.036023057997226715,
0.03034823387861252,
-0.03264826536178589,
-0.05759384483098984,
-0.0447617843747139,
-0.0006687974091619253,
-0.038549039512872696,
0.060028668493032455,
0.05835878849029541,
-0.014211258850991726,
0.020786551758646965,
0.01309980172663927,
-0... | 0.191684 |
Pods to run correctly on that particular node. For example, [network plugins](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/) often include a component that runs as a DaemonSet. The DaemonSet component makes sure that the node where it's running has working cluster networking. ## {{% heading "wha... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/daemonset.md | main | kubernetes | [
0.002776756649836898,
-0.02867501601576805,
0.023288730531930923,
0.05021410062909126,
-0.007434606086462736,
0.005266173742711544,
-0.011292963288724422,
-0.0062147644348442554,
0.03216595947742462,
0.06360616534948349,
-0.0008318859618157148,
0.02514936961233616,
-0.04466448351740837,
-0... | 0.179794 |
A \_Deployment\_ provides declarative updates for {{< glossary\_tooltip text="Pods" term\_id="pod" >}} and {{< glossary\_tooltip term\_id="replica-set" text="ReplicaSets" >}}. You describe a \_desired state\_ in a Deployment, and the Deployment {{< glossary\_tooltip term\_id="controller" >}} changes the actual state to... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
-0.06276048719882965,
-0.037218790501356125,
0.0883634015917778,
-0.017394982278347015,
-0.03408537805080414,
-0.05041898041963577,
0.06987310945987701,
-0.10028190910816193,
0.06638434529304504,
0.08490025997161865,
0.05518738552927971,
-0.06027211993932724,
0.02244611643254757,
-0.057519... | 0.062707 |
`kubectl get deployments` to check if the Deployment was created. If the Deployment is still being created, the output is similar to the following: ``` NAME READY UP-TO-DATE AVAILABLE AGE nginx-deployment 0/3 0 0 1s ``` When you inspect the Deployments in your cluster, the following fields are displayed: \* `NAME` list... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
-0.014701560139656067,
0.015564560890197754,
-0.024317637085914612,
0.0030299555510282516,
-0.02260657027363777,
-0.023732777684926987,
-0.06087828800082207,
-0.06681539118289948,
0.08175746351480484,
0.06665243953466415,
0.001440137391909957,
-0.0768941193819046,
0.009884214028716087,
-0.... | 0.144298 |
to the ReplicaSet selector, Pod template labels, and in any existing Pods that the ReplicaSet might have. ## Updating a Deployment {{< note >}} A Deployment's rollout is triggered if and only if the Deployment's Pod template (that is, `.spec.template`) is changed, for example if the labels or container images of the te... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
0.03546261787414551,
0.04836989566683769,
0.06651099771261215,
-0.0038526388816535473,
-0.013350342400372028,
-0.005036485381424427,
-0.050936561077833176,
-0.04574483633041382,
0.03630445525050163,
0.04942344129085541,
0.012697050347924232,
-0.0184091255068779,
-0.036774035543203354,
-0.0... | 0.063933 |
be between 3 and 5. \* Get details of your Deployment: ```shell kubectl describe deployments ``` The output is similar to this: ``` Name: nginx-deployment Namespace: default CreationTimestamp: Thu, 30 Nov 2017 10:56:25 +0000 Labels: app=nginx Annotations: deployment.kubernetes.io/revision=2 Selector: app=nginx Replicas... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
0.01079177763313055,
0.027903271839022636,
0.03294099122285843,
-0.03567548468708992,
-0.02694237418472767,
-0.024474309757351875,
-0.07065124809741974,
-0.014679765328764915,
0.07304441928863525,
0.0513041652739048,
-0.02338959462940693,
-0.11164301633834839,
-0.020456189289689064,
-0.050... | 0.092901 |
It does not wait for the 5 replicas of `nginx:1.14.2` to be created before changing course. ### Label selector updates It is generally discouraged to make label selector updates and it is suggested to plan your selectors up front. A Deployment's label selector is \*\*immutable\*\* after creation; it cannot be updated v... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
-0.05814023315906525,
0.042627543210983276,
0.1133197620511055,
-0.04175194725394249,
0.028185652568936348,
0.004761401563882828,
-0.013827352784574032,
-0.10565170645713806,
0.0398106575012207,
0.04880497604608536,
0.026768216863274574,
-0.03295231983065605,
-0.02409251220524311,
-0.02913... | 0.05338 |
the number of new replicas (from `nginx-deployment-3066724191`) is 1. ```shell kubectl get rs ``` The output is similar to this: ``` NAME DESIRED CURRENT READY AGE nginx-deployment-1564180365 3 3 3 25s nginx-deployment-2035384211 0 0 0 36s nginx-deployment-3066724191 1 1 0 6s ``` \* Looking at the Pods created, you see... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
-0.013591025024652481,
-0.03395388647913933,
0.017597878351807594,
-0.0021268241107463837,
0.0035399680491536856,
-0.06187530606985092,
-0.022318745031952858,
-0.05447341874241829,
0.08457743376493454,
0.019626734778285027,
0.041508227586746216,
-0.048476606607437134,
0.004049938637763262,
... | 0.118798 |
nginx: Image: nginx:1.16.1 Port: 80/TCP QoS Tier: cpu: BestEffort memory: BestEffort Environment Variables: No volumes. ``` ### Rolling Back to a Previous Revision Follow the steps given below to rollback the Deployment from the current version to the previous version, which is version 2. 1. Now you've decided to undo ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
0.00699254497885704,
0.0993206575512886,
0.059075552970170975,
-0.011972984299063683,
-0.05034551024436951,
-0.009157453663647175,
-0.06430649012327194,
-0.056504521518945694,
0.057562146335840225,
0.045884501188993454,
0.002120367716997862,
0.05232556164264679,
-0.02187192626297474,
-0.00... | -0.042975 |
risk. This is called \*proportional scaling\*. For example, you are running a Deployment with 10 replicas, [maxSurge](#max-surge)=3, and [maxUnavailable](#max-unavailable)=2. \* Ensure that the 10 replicas in your Deployment are running. ```shell kubectl get deploy ``` The output is similar to this: ``` NAME DESIRED CU... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
-0.008490112610161304,
-0.009384791366755962,
0.038554877042770386,
-0.006286855321377516,
-0.01704336144030094,
-0.059015143662691116,
-0.09974619746208191,
-0.009078077040612698,
0.00878257304430008,
0.0422278568148613,
0.03689432889223099,
-0.029690930619835854,
0.05651140958070755,
-0.... | 0.085696 |
CHANGE-CAUSE 1 ``` \* Get the rollout status to verify that the existing ReplicaSet has not changed: ```shell kubectl get rs ``` The output is similar to this: ``` NAME DESIRED CURRENT READY AGE nginx-2142116321 3 3 3 2m ``` \* You can make as many updates as you wish, for example, update the resources that will be use... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
-0.01101872231811285,
0.01785142906010151,
-0.001764003885909915,
-0.03805110603570938,
-0.0332239493727684,
-0.04829329997301102,
-0.04409630224108696,
-0.07224573940038681,
0.0555841363966465,
0.0705208107829094,
0.00221890676766634,
-0.05681973323225975,
0.01955590397119522,
-0.07668230... | 0.124029 |
instead affect the `Available` condition). You can check if a Deployment has completed by using `kubectl rollout status`. If the rollout completed successfully, `kubectl rollout status` returns a zero exit code. ```shell kubectl rollout status deployment/nginx-deployment ``` The output is similar to this: ``` Waiting f... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
0.02628631517291069,
0.010611476376652718,
0.024665547534823418,
-0.02890353463590145,
-0.005917713046073914,
-0.039342887699604034,
-0.0888599157333374,
-0.05940713733434677,
0.0527186319231987,
0.06573418527841568,
0.017044777050614357,
-0.0854983776807785,
-0.0006037675775587559,
-0.018... | 0.037267 |
exceeded, Kubernetes updates the status and the reason for the Progressing condition: ``` Conditions: Type Status Reason ---- ------ ------ Available True MinimumReplicasAvailable Progressing False ProgressDeadlineExceeded ReplicaFailure True FailedCreate ``` You can address an issue of insufficient quota by scaling do... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
0.013593994081020355,
-0.05493239313364029,
0.03433912992477417,
-0.018437359482049942,
-0.0613371767103672,
-0.026936214417219162,
-0.047979746013879776,
-0.01673431694507599,
0.050222236663103104,
0.13186682760715485,
0.0318310521543026,
-0.07675320655107498,
0.02161916345357895,
-0.0388... | 0.049953 |
the control plane creates new Pods for a Deployment, the `.metadata.name` of the Deployment is part of the basis for naming those Pods. The name of a Deployment must be a valid [DNS subdomain](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names) value, but this can produce unexpected results for the ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
-0.025266259908676147,
-0.0182010680437088,
0.06660116463899612,
0.002589660231024027,
-0.0545649379491806,
-0.04275104030966759,
-0.013198401778936386,
0.005018592346459627,
0.043093059211969376,
0.04409189894795418,
-0.026215365156531334,
-0.06426967680454254,
-0.07526937872171402,
-0.00... | 0.121218 |
the old Pod is still in a Terminating state). If you need an "at most" guarantee for your Pods, you should consider using a [StatefulSet](/docs/concepts/workloads/controllers/statefulset/). {{< /note >}} #### Rolling Update Deployment The Deployment updates Pods in a rolling update fashion (gradually scale down the old... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
0.01600799523293972,
-0.023666532710194588,
-0.015758665278553963,
-0.0008973939693532884,
-0.028512107208371162,
-0.07157764583826065,
-0.06366311013698578,
0.03841163590550423,
-0.03083920106291771,
0.08079152554273605,
0.032971903681755066,
0.03746771439909935,
-0.009956701658666134,
-0... | 0.100165 |
a condition with `type: Progressing`, `status: "False"`. and `reason: ProgressDeadlineExceeded` in the status of the resource. The Deployment controller will keep retrying the Deployment. This defaults to 600. In the future, once automatic rollback will be implemented, the Deployment controller will roll back a Deploym... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/deployment.md | main | kubernetes | [
0.04469101130962372,
-0.009055950678884983,
0.029856711626052856,
0.0770043358206749,
-0.006723111029714346,
-0.03135892003774643,
-0.0456419512629509,
-0.01373475044965744,
0.01913401670753956,
0.0779063031077385,
0.03074418567121029,
0.031855929642915726,
-0.042014267295598984,
-0.022469... | 0.138812 |
StatefulSet is the workload API object used to manage stateful applications. {{< glossary\_definition term\_id="statefulset" length="all" >}} ## Using StatefulSets StatefulSets are valuable for applications that require one or more of the following: \* Stable, unique network identifiers. \* Stable, persistent storage. ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/statefulset.md | main | kubernetes | [
-0.006021921522915363,
-0.0356716588139534,
-0.01688295230269432,
0.019070129841566086,
-0.061745189130306244,
-0.015393666923046112,
-0.040966324508190155,
0.0011013125767931342,
0.0014097071252763271,
0.0725516751408577,
-0.045228105038404465,
0.04807261750102043,
0.002696857787668705,
-... | 0.141056 |
a PersistentVolume with the correct StorageClass and sufficient available storage space. ### Minimum ready seconds {{< feature-state for\_k8s\_version="v1.25" state="stable" >}} `.spec.minReadySeconds` is an optional field that specifies the minimum number of seconds for which a newly created Pod should be running and ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/statefulset.md | main | kubernetes | [
0.007563621271401644,
-0.019579678773880005,
0.022878235206007957,
0.06460247933864594,
0.005311621818691492,
-0.0038539133965969086,
-0.03078707866370678,
-0.02162006124854088,
0.05590884014964104,
0.030833924189209938,
0.0023245513439178467,
0.036990370601415634,
-0.024414079263806343,
-... | 0.190182 |
-------------- | ----------------- | --------------------- | ------------------------------- | -------------------------------------------- | ------------ | | cluster.local | default/nginx | default/web | nginx.default.svc.cluster.local | web-{0..N-1}.nginx.default.svc.cluster.local | web-{0..N-1} | | cluster.local | f... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/statefulset.md | main | kubernetes | [
0.0033405933063477278,
-0.006348114460706711,
-0.05005044490098953,
0.011122279800474644,
0.06733474880456924,
-0.005930569488555193,
-0.04256175085902214,
-0.056204408407211304,
0.011236928403377533,
-0.02364523336291313,
0.06323815882205963,
-0.047782763838768005,
-0.06102858483791351,
0... | 0.039459 |
field. #### OrderedReady Pod Management `OrderedReady` pod management is the default for StatefulSets. It implements the behavior described in [Deployment and Scaling Guarantees](#deployment-and-scaling-guarantees). #### Parallel Pod Management `Parallel` pod management tells the StatefulSet controller to launch or ter... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/statefulset.md | main | kubernetes | [
-0.016558034345507622,
-0.04305212199687958,
-0.025398219004273415,
0.00975874811410904,
-0.04110203683376312,
-0.05170769244432449,
-0.06845302879810333,
-0.019048981368541718,
-0.01584445871412754,
0.1030406504869461,
0.04633055254817009,
0.06103294715285301,
-0.009362722747027874,
-0.09... | 0.198553 |
in Beta stage and it is enabled by default. {{< /note >}} ### Forced rollback When using [Rolling Updates](#rolling-updates) with the default [Pod Management Policy](#pod-management-policies) (`OrderedReady`), it's possible to get into a broken state that requires manual intervention to repair. If you update the Pod te... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/statefulset.md | main | kubernetes | [
0.010750528424978256,
0.0004470532003324479,
0.1019306555390358,
0.018331056460738182,
-0.0182005874812603,
0.004194984212517738,
-0.07544346898794174,
-0.08115651458501816,
-0.004370014648884535,
0.08546211570501328,
-0.01289656013250351,
0.12155284732580185,
-0.03344694897532463,
-0.0386... | 0.133498 |
the value to either `Delete` or `Retain`. `Delete` : The PVCs created from the StatefulSet `volumeClaimTemplate` are deleted for each Pod affected by the policy. With the `whenDeleted` policy all PVCs from the `volumeClaimTemplate` are deleted after their Pods have been deleted. With the `whenScaled` policy, only PVCs ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/statefulset.md | main | kubernetes | [
-0.0653388574719429,
-0.004910527728497982,
0.04460317641496658,
0.022889768704771996,
0.062305767089128494,
0.07087746262550354,
0.047388408333063126,
-0.044890280812978745,
0.06196685507893562,
0.05189863219857216,
0.049485333263874054,
0.027973709627985954,
0.02653343789279461,
-0.01327... | 0.12207 |
similar API for horizontal scaling) is managing scaling for a Statefulset, don't set `.spec.replicas`. Instead, allow the Kubernetes {{}} to manage the `.spec.replicas` field automatically. ## {{% heading "whatsnext" %}} \* Learn about [Pods](/docs/concepts/workloads/pods). \* Find out how to use StatefulSets \* Follow... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/statefulset.md | main | kubernetes | [
0.019421366974711418,
0.03127868101000786,
0.005351583007723093,
0.041110292077064514,
-0.09352212399244308,
-0.03440432995557785,
-0.07732247561216354,
0.0146726593375206,
-0.011946498416364193,
0.06317714601755142,
-0.044027164578437805,
-0.055776454508304596,
0.03640415146946907,
-0.036... | 0.143001 |
A ReplicaSet's purpose is to maintain a stable set of replica Pods running at any given time. As such, it is often used to guarantee the availability of a specified number of identical Pods. ## How a ReplicaSet works A ReplicaSet is defined with fields, including a selector that specifies how to identify Pods it can ac... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/replicaset.md | main | kubernetes | [
-0.020438574254512787,
-0.00177835114300251,
0.026208890601992607,
0.0011802701046690345,
0.02982032671570778,
-0.0033121241722255945,
0.029650337994098663,
-0.0437772199511528,
0.11775081604719162,
0.023077024146914482,
-0.005686653312295675,
-0.007580601144582033,
0.024579793214797974,
-... | 0.210414 |
the Pods running: ```shell kubectl get pods frontend-gbgfx -o yaml ``` The output will look similar to this, with the frontend ReplicaSet's info set in the metadata's ownerReferences field: ```yaml apiVersion: v1 kind: Pod metadata: creationTimestamp: "2024-02-28T22:30:44Z" generateName: frontend- labels: tier: fronten... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/replicaset.md | main | kubernetes | [
0.021828962489962578,
0.004231722559779882,
0.043960485607385635,
-0.008131253533065319,
0.024828998371958733,
0.0011057958472520113,
-0.02183784916996956,
-0.03546230494976044,
0.08628660440444946,
0.036069244146347046,
0.03853403776884079,
-0.0814724862575531,
-0.014047833159565926,
-0.0... | 0.082158 |
is `Always`, which is the default. ### Pod Selector The `.spec.selector` field is a [label selector](/docs/concepts/overview/working-with-objects/labels/). As discussed [earlier](#how-a-replicaset-works) these are the labels used to identify potential Pods to acquire. In our `frontend.yaml` example, the selector was: `... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/replicaset.md | main | kubernetes | [
-0.02048579975962639,
0.014567411504685879,
0.01461494155228138,
0.025716464966535568,
0.04554247856140137,
-0.023017054423689842,
-0.00017506552103441209,
-0.030703507363796234,
0.060690876096487045,
-0.016641095280647278,
0.0062631880864501,
-0.057744305580854416,
-0.016102638095617294,
... | 0.138743 |
more replicas come before pods on nodes with fewer replicas. 1. If the pods' creation times differ, the pod that was created more recently comes before the older pod (the creation times are bucketed on an integer log scale). If all of the above match, then selection is random. ### Pod deletion cost {{< feature-state fo... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/replicaset.md | main | kubernetes | [
-0.0006049923831596971,
0.01734665222465992,
0.08261767774820328,
0.023625634610652924,
0.0922279879450798,
0.007499142549932003,
0.07501841336488724,
-0.035308126360177994,
0.15765073895454407,
0.05375995486974716,
0.02155448868870735,
-0.02380187436938286,
-0.00023244571639224887,
-0.036... | 0.139872 |
requires only a single Pod. Think of it similarly to a process supervisor, only it supervises multiple Pods across multiple nodes instead of individual processes on a single node. A ReplicaSet delegates local container restarts to some agent on the node such as Kubelet. ### Job Use a [`Job`](/docs/concepts/workloads/co... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/replicaset.md | main | kubernetes | [
-0.03634198009967804,
-0.03990801051259041,
0.005726237315684557,
0.0003170934214722365,
0.028715146705508232,
0.010407442227005959,
-0.027401152998209,
-0.0291921254247427,
0.06648941338062286,
0.05240171402692795,
-0.03590918332338333,
0.026120690628886223,
-0.019029775634407997,
-0.0291... | 0.246395 |
A Job creates one or more Pods and will continue to retry execution of the Pods until a specified number of them successfully terminate. As pods successfully complete, the Job tracks the successful completions. When a specified number of successful completions is reached, the task (ie, Job) is complete. Deleting a Job ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
-0.04721604287624359,
-0.023575467988848686,
0.011756082065403461,
0.06397971510887146,
0.0030678610783070326,
-0.04076340049505234,
-0.04546281322836876,
-0.05230122059583664,
0.021000783890485764,
0.04583517089486122,
-0.010986591689288616,
0.03892342001199722,
-0.013258432038128376,
-0.... | 0.196307 |
Writing a Job spec As with all other Kubernetes config, a Job needs `apiVersion`, `kind`, and `metadata` fields. When the control plane creates new Pods for a Job, the `.metadata.name` of the Job is part of the basis for naming those Pods. The name of a Job must be a valid [DNS subdomain](/docs/concepts/overview/workin... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
-0.06502047181129456,
-0.012073139660060406,
0.023211942985653877,
-0.01614469662308693,
-0.08843913674354553,
-0.06255214661359787,
-0.02128208614885807,
-0.044451404362916946,
0.02756296657025814,
0.00028693670174106956,
-0.08206561952829361,
-0.05679332837462425,
-0.05029766634106636,
0... | 0.112498 |
(`.spec.parallelism`) can be set to any non-negative value. If it is unspecified, it defaults to 1. If it is specified as 0, then the Job is effectively paused until it is increased. Actual parallelism (number of pods running at any instant) may be more or less than requested parallelism, for a variety of reasons: - Fo... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
-0.07413549721240997,
-0.059612881392240524,
-0.01408139057457447,
0.029257992282509804,
-0.016509532928466797,
-0.034854453057050705,
-0.02424883469939232,
-0.055185701698064804,
0.051108334213495255,
0.082151859998703,
0.07509064674377441,
-0.035287145525217056,
-0.038059432059526443,
-0... | 0.108269 |
it is restarted locally, or else specify `.spec.template.spec.restartPolicy = "Never"`. See [pod lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy) for more information on `restartPolicy`. An entire Pod can also fail, for a number of reasons, such as when the pod is kicked off the node (node is upg... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
0.01284304540604353,
-0.03156931698322296,
0.01127098873257637,
0.05540113151073456,
0.03614749386906624,
-0.005347770638763905,
-0.04817609116435051,
0.025984710082411766,
0.0020766856614500284,
0.02566693350672722,
-0.009193122386932373,
0.09042446315288544,
-0.043101970106363297,
-0.046... | 0.167652 |
feature\_gate\_name="JobBackoffLimitPerIndex" >}} When you run an [indexed](#completion-mode) Job, you can choose to handle retries for pod failures independently for each index. To do so, set the `.spec.backoffLimitPerIndex` to specify the maximal number of pod failures per index. When the per-index backoff limit is e... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
0.02539285644888878,
-0.0007524692337028682,
0.06262179464101791,
0.07966060936450958,
0.00039580988232046366,
-0.018008971586823463,
0.006727381143718958,
-0.05658724531531334,
0.01950085535645485,
0.0019456316949799657,
-0.058330584317445755,
0.024007966741919518,
-0.024563580751419067,
... | 0.116699 |
caused by disruptions (such as {{< glossary\_tooltip text="preemption" term\_id="preemption" >}}, {{< glossary\_tooltip text="API-initiated eviction" term\_id="api-eviction" >}} or {{< glossary\_tooltip text="taint" term\_id="taint" >}}-based eviction) so that they don't count towards the `.spec.backoffLimit` limit of ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
-0.05926914140582085,
0.021708156913518906,
0.08044680953025818,
0.026240352541208267,
-0.005331705790013075,
-0.03500289469957352,
0.021534351631999016,
-0.05140848457813263,
-0.0045450590550899506,
0.02179620787501335,
0.027016043663024902,
-0.029399044811725616,
-0.007711475715041161,
-... | 0.035674 |
terminal phase. Since Kubernetes 1.27, Kubelet transitions deleted pods to a terminal phase (see: [Pod Phase](/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase)). This ensures that deleted pods have their finalizers removed by the Job controller. {{< /note >}} {{< note >}} Starting with Kubernetes v1.28, when Pod ... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
0.015072546899318695,
-0.0023724273778498173,
0.09962522983551025,
0.009662057273089886,
0.03858242556452751,
0.005214728880673647,
-0.03466876968741417,
-0.045717887580394745,
0.08863552659749985,
0.042061302810907364,
0.005322601180523634,
0.03392089158296585,
-0.004860298242419958,
-0.0... | 0.121603 |
terminating policy and ignores the success policy. {{< /note >}} ## Job termination and cleanup When a Job completes, no more Pods are created, but the Pods are [usually](#pod-backoff-failure-policy) not deleted either. Keeping them around allows you to still view the logs of completed pods to check for errors, warning... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
-0.01020264532417059,
0.012268942780792713,
0.03258032351732254,
0.021576594561338425,
0.04866103082895279,
-0.048323098570108414,
-0.012662703171372414,
-0.09976831823587418,
0.05541350319981575,
0.04532793536782265,
0.014170568436384201,
0.04386216774582863,
-0.036099500954151154,
-0.053... | 0.170289 |
delays the addition of the terminal conditions,`Failed` or `Complete`, until all of the Job Pods are terminated. In Kubernetes v1.30 and earlier, the Job controller added the `Complete` or the `Failed` Job terminal conditions as soon as the Job termination process was triggered and all Pod finalizers were removed. Howe... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
0.03349387273192406,
-0.018964942544698715,
0.07995621114969254,
0.0054581961594522,
0.03342897817492485,
-0.0024332082830369473,
-0.04093683883547783,
-0.04611615091562271,
0.07976198196411133,
0.09375549852848053,
0.019029298797249794,
-0.000516951025929302,
-0.016841858625411987,
-0.016... | 0.095859 |
because unmanaged jobs (Jobs that you created directly, and not indirectly through other workload APIs such as CronJob) have a default deletion policy of `orphanDependents` causing Pods created by an unmanaged Job to be left around after that Job is fully deleted. Even though the {{< glossary\_tooltip text="control pla... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
-0.06294743716716766,
-0.030346840620040894,
0.05566905811429024,
0.08066616952419281,
0.04127928614616394,
-0.044285789132118225,
0.029003305360674858,
-0.10425528883934021,
0.09961370378732681,
0.03772847726941109,
-0.002951083006337285,
0.008048167452216148,
-0.04812369868159294,
0.0001... | 0.115761 |
the required settings for `.spec.parallelism` and `.spec.completions` for each of the patterns. Here, `W` is the number of work items. | Pattern | `.spec.completions` | `.spec.parallelism` | | ----------------------------------------------- |:-------------------:|:--------------------:| | [Queue with Pod Per Work Item]... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
-0.044477544724941254,
0.008875507861375809,
-0.025590064004063606,
0.043869875371456146,
-0.058619242161512375,
-0.05553404614329338,
0.06146884337067604,
-0.06954390555620193,
-0.056973446160554886,
0.014261994510889053,
0.03230329230427742,
-0.0496981255710125,
-0.053089044988155365,
-0... | 0.130899 |
```shell kubectl describe jobs/myjob ``` ``` Name: myjob ... Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal SuccessfulCreate 12m job-controller Created pod: myjob-hlrpl Normal SuccessfulDelete 11m job-controller Deleted pod: myjob-hlrpl Normal Suspended 11m job-controller Job suspended Normal... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
-0.025851193815469742,
-0.009801145642995834,
0.05678922310471535,
0.047039732336997986,
0.03342105448246002,
0.03211664408445358,
-0.01858513057231903,
-0.05014058202505112,
0.049013569951057434,
0.04341670870780945,
0.025774899870157242,
0.005343222990632057,
-0.025121569633483887,
-0.03... | 0.154892 |
is chosen, then other controllers (e.g. ReplicationController) and their Pods may behave in unpredictable ways too. Kubernetes will not stop you from making a mistake when specifying `.spec.selector`. Here is an example of a case when you might want to use this feature. Say Job `old` is already running. You want existi... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
-0.027608323842287064,
-0.010486139915883541,
0.021816158667206764,
0.0045967441983520985,
0.029080085456371307,
-0.011695163324475288,
-0.013586440123617649,
-0.1172160878777504,
0.08046599477529526,
0.05008388310670853,
0.032842934131622314,
0.021391820162534714,
-0.02945282682776451,
-0... | 0.121665 |
the control plane sees that a Pod for this Job has `deletionTimestamp` set). For Jobs with a Pod failure policy set, the default `podReplacementPolicy` is `Failed`, and no other value is permitted. See [Pod failure policy](#pod-failure-policy) to learn more about Pod failure policies for Jobs. ```yaml kind: Job metadat... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
0.015432890504598618,
-0.03222823888063431,
-0.02072061598300934,
0.047580890357494354,
0.03522917628288269,
-0.0171162448823452,
0.027987195178866386,
-0.060818661004304886,
0.010045218281447887,
0.05357380211353302,
0.004894104786217213,
-0.012476630508899689,
-0.034699440002441406,
-0.0... | 0.197501 |
Queue](/docs/tasks/job/coarse-parallel-processing-work-queue/) \* [Fine Parallel Processing Using a Work Queue](/docs/tasks/job/fine-parallel-processing-work-queue/) \* Use an [indexed Job for parallel processing with static work assignment](/docs/tasks/job/indexed-parallel-processing-static/) \* Create multiple Jobs b... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/job.md | main | kubernetes | [
-0.0734645202755928,
0.0012396742822602391,
0.012356371618807316,
-0.010888609103858471,
-0.058224812150001526,
-0.025342434644699097,
-0.024360831826925278,
-0.06338264048099518,
0.010356391780078411,
0.03684329241514206,
-0.014700055122375488,
-0.026444289833307266,
-0.013028697110712528,
... | 0.162146 |
Kubernetes provides several built-in APIs for declarative management of your {{< glossary\_tooltip text="workloads" term\_id="workload" >}} and the components of those workloads. Ultimately, your applications run as containers inside {{< glossary\_tooltip term\_id="Pod" text="Pods" >}}; however, managing individual Pod... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/_index.md | main | kubernetes | [
-0.025058364495635033,
-0.009233055636286736,
0.08028741180896759,
0.013798514381051064,
-0.055924996733665466,
-0.045588139444589615,
0.061614155769348145,
-0.011117551475763321,
0.09019558876752853,
0.025438647717237473,
-0.039260122925043106,
-0.0457732118666172,
-0.021477922797203064,
... | 0.100066 |
{{< note >}} A [`Deployment`](/docs/concepts/workloads/controllers/deployment/) that configures a [`ReplicaSet`](/docs/concepts/workloads/controllers/replicaset/) is now the recommended way to set up replication. {{< /note >}} A \_ReplicationController\_ ensures that a specified number of pod replicas are running at an... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/replicationcontroller.md | main | kubernetes | [
-0.03037889301776886,
-0.09706129878759384,
-0.06445758044719696,
-0.00903519056737423,
0.009261714294552803,
0.002291112905368209,
-0.032145462930202484,
0.005719681270420551,
0.02187923900783062,
0.09491005539894104,
0.06895775347948074,
0.06870926916599274,
0.03618994355201721,
-0.04923... | 0.131023 |
ReplicationController must be a valid [DNS subdomain](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names) value, but this can produce unexpected results for the Pod hostnames. For best compatibility, the name should follow the more restrictive rules for a [DNS label](/docs/concepts/overview/working-... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/replicationcontroller.md | main | kubernetes | [
-0.042656995356082916,
-0.025092624127864838,
0.023601915687322617,
-0.008394671604037285,
-0.04562579467892647,
-0.028565499931573868,
-0.020015297457575798,
-0.013486020267009735,
0.0116111533716321,
0.036088909953832626,
-0.03571410849690437,
-0.020506620407104492,
-0.03547373414039612,
... | 0.098215 |
ReplicationController object. Once the original is deleted, you can create a new ReplicationController to replace it. As long as the old and new `.spec.selector` are the same, then the new one will adopt the old pods. However, it will not make any effort to make existing pods match a new, different pod template. To upd... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/replicationcontroller.md | main | kubernetes | [
-0.023286743089556694,
-0.06398065388202667,
-0.014328503981232643,
0.027575744315981865,
0.04647374153137207,
0.004499190021306276,
-0.02405169978737831,
-0.05289287120103836,
0.000022706783056491986,
0.06720559298992157,
0.03755006194114685,
0.05842652916908264,
-0.028660977259278297,
-0... | 0.127347 |
be created and destroyed over the lifetime of a service (for instance, to perform an update of pods that run the service). Both services themselves and their clients should remain oblivious to the ReplicationControllers that maintain the pods of the services. ## Writing programs for Replication Pods created by a Replic... | https://github.com/kubernetes/website/blob/main//content/en/docs/concepts/workloads/controllers/replicationcontroller.md | main | kubernetes | [
-0.044892314821481705,
-0.04523729905486107,
-0.0459325835108757,
0.018406741321086884,
-0.06659625470638275,
-0.03230834752321243,
-0.005604699719697237,
-0.017358604818582535,
0.020278912037611008,
0.0991266518831253,
-0.014435661025345325,
0.12007994204759598,
0.04487346112728119,
-0.01... | 0.18914 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.