content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 50
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
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 |
tracking {{< feature-state feature\_gate\_name="PersistentVolumeClaimUnusedSinceTime" >}} When enabled, the PVC protection controller adds an `Unused` [condition](/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions) to each PersistentVolumeClaim to indicate whether it is currently referenced by any non-terminal... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.00889330543577671,
-0.03787801042199135,
-0.0029688184149563313,
0.05318107455968857,
0.07187493145465851,
0.01576763018965721,
0.01921805739402771,
0.017412271350622177,
0.08599115908145905,
0.04951022192835808,
0.04600999131798744,
-0.035127904266119,
-0.018039800226688385,
0.01093132... | 0.174655 |
>}} ### Binding Block Volumes If a user requests a raw block volume by indicating this using the `volumeMode` field in the PersistentVolumeClaim spec, the binding rules differ slightly from previous releases that didn't consider this mode as part of the spec. Listed is a table of possible combinations the user and admi... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.07493074238300323,
-0.02971000038087368,
-0.04043805971741676,
-0.023020580410957336,
-0.03383183106780052,
-0.050083935260772705,
-0.04185043275356293,
0.06328770518302917,
-0.0012760543031618,
-0.007579183205962181,
0.016331003978848457,
-0.027642900124192238,
0.03943879157304764,
0.0... | 0.029926 |
The `dataSourceRef` field behaves almost the same as the `dataSource` field. If one is specified while the other is not, the API server will give both fields the same value. Neither field can be changed after creation, and attempting to specify different values for the two fields will result in a validation error. Ther... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.08919824659824371,
-0.0488300547003746,
0.04827965050935745,
0.027486292645335197,
-0.007105245254933834,
-0.0876728966832161,
0.011215351521968842,
-0.03737710043787956,
0.09106402844190598,
-0.03942783549427986,
0.0312318354845047,
-0.08941331505775452,
0.08726467192173004,
-0.0197375... | 0.048384 |
Configuration If you're writing configuration templates or examples that run on a wide range of clusters and need persistent storage, it is recommended that you use the following pattern: - Include PersistentVolumeClaim objects in your bundle of config (alongside Deployments, ConfigMaps, etc). - Do not include Persiste... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/persistent-volumes.md | main | kubernetes | [
-0.010937390848994255,
-0.01650150492787361,
-0.06920187920331955,
0.027252865955233574,
-0.04593045264482498,
0.04106784239411354,
0.026349809020757675,
0.03522288054227829,
-0.032330065965652466,
-0.022804467007517815,
0.028074640780687332,
-0.028742589056491852,
0.03720760717988014,
0.0... | -0.009168 |
Nodes have local ephemeral storage, backed by locally-attached writeable devices or, sometimes, by RAM. "Ephemeral" means that there is no long-term guarantee about durability. Pods use ephemeral local storage for scratch space, caching, and for logs. The kubelet can provide scratch space to Pods using local ephemeral ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/ephemeral-storage.md | main | kubernetes | [
0.01369106862694025,
0.03762815520167351,
0.05522778630256653,
0.028032928705215454,
0.012470952235162258,
-0.04762090742588043,
-0.018102530390024185,
0.029156213626265526,
0.09794659912586212,
0.04269580915570259,
-0.008187946863472462,
-0.05077235400676727,
0.009183380752801895,
-0.0227... | 0.190095 |
filesystems as `nodefs`, `imagefs`, and `containerfs`. Those names do not always mean separate mount points. The kubelet can measure local storage use when you set up the node using one of the supported configurations for local ephemeral storage. If you have a different configuration, then the kubelet does not apply re... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/ephemeral-storage.md | main | kubernetes | [
0.05487735942006111,
0.05550985038280487,
0.02773085981607437,
0.014431988820433617,
0.007301050703972578,
-0.0176410935819149,
-0.05291370674967766,
0.040025580674409866,
0.12640994787216187,
-0.027472207322716713,
0.003799125785008073,
-0.08645808696746826,
0.0005281294579617679,
0.00207... | 0.111092 |
summing the limits for the containers in that Pod. In this case, if the sum of the local ephemeral storage usage from all containers and also the Pod's `emptyDir` volumes exceeds the overall Pod storage limit, then the kubelet also marks the Pod for eviction. {{< caution >}} If the kubelet is not measuring local epheme... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/ephemeral-storage.md | main | kubernetes | [
0.027704907581210136,
0.057113636285066605,
0.09886236488819122,
0.036951418966054916,
0.023841043934226036,
-0.059247225522994995,
0.02676979824900627,
-0.016624372452497482,
0.1276770532131195,
0.02200406603515148,
0.028422443196177483,
-0.08466146886348724,
-0.018346616998314857,
-0.025... | 0.100389 |
All XFS filesystems support project quotas. For ext4 filesystems, you need to enable the project quota tracking feature while the filesystem is not mounted. ```bash # For ext4, with /dev/block-device not mounted sudo tune2fs -O project -Q prjquota /dev/block-device ``` \* Ensure that the root filesystem (or optional ru... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/ephemeral-storage.md | main | kubernetes | [
0.04751960188150406,
0.007392703089863062,
-0.02263724058866501,
-0.04464954510331154,
0.021197063848376274,
-0.03462697193026543,
0.014018719084560871,
0.06347695738077164,
0.10585763305425644,
0.010413908399641514,
0.039133619517087936,
-0.11717920005321503,
0.011463121511042118,
0.04303... | 0.000361 |
This page describes the maximum number of volumes that can be attached to a Node for various cloud providers. Cloud providers like Google, Amazon, and Microsoft typically have a limit on how many volumes can be attached to a Node. It is important for Kubernetes to respect those limits. Otherwise, Pods scheduled on a No... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/storage-limits.md | main | kubernetes | [
0.01650424487888813,
-0.028903089463710785,
0.048529598861932755,
0.009387269616127014,
-0.025177543982863426,
0.01048780046403408,
-0.09080570191144943,
-0.006535973399877548,
0.07361065596342087,
0.05717209354043007,
-0.06507131457328796,
0.037200525403022766,
0.06331241875886917,
-0.001... | 0.041396 |
will prevent pod placement to nodes that do not yet have CSI driver installed. For exmaple: ```yaml apiVersion: storage.k8s.io/v1 kind: CSIDriver metadata: name: hostpath.csi.k8s.io spec: preventPodSchedulingIfMissing: true ``` This limitation only applies to pods that require corresponding CSI volume. ### CSI volume a... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/storage-limits.md | main | kubernetes | [
0.07405595481395721,
0.006560217589139938,
0.03516439348459244,
0.04696057736873627,
0.009278712794184685,
-0.038835059851408005,
-0.008737141266465187,
-0.0256081223487854,
0.026367129758000374,
0.07005199044942856,
-0.003459902945905924,
-0.020374620333313942,
-0.002890781732276082,
0.04... | 0.149328 |
Kubernetes \_volumes\_ provide a way for containers in a {{< glossary\_tooltip text="Pod" term\_id="pod" >}} to access and share data via the filesystem. There are different kinds of volume that you can use for different purposes, such as: - populating a configuration file based on a {{< glossary\_tooltip text="ConfigM... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volumes.md | main | kubernetes | [
-0.06934083253145218,
0.0026714331470429897,
0.05597236379981041,
0.0068943677470088005,
-0.007250917609781027,
-0.034288059920072556,
0.06986643373966217,
-0.0029261528979986906,
0.0527954176068306,
0.01698337309062481,
0.009296850301325321,
-0.05079301446676254,
0.023955946788191795,
-0.... | 0.088476 |
a subsequent filesystem access. Volumes are mounted at [specified paths](#using-subpath) within the container filesystem. For each container defined within a Pod, you must independently specify where to mount each volume that the container uses. Volumes cannot mount within other volumes (but see [Using subPath](#using-... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volumes.md | main | kubernetes | [
0.05892137065529823,
-0.0438353456556797,
0.05365642532706261,
0.006807579193264246,
0.030595354735851288,
-0.04159582406282425,
0.0026570484042167664,
0.03356258198618889,
0.05330267176032066,
0.01588740199804306,
-0.01438396517187357,
-0.030582193285226822,
0.03759133815765381,
0.0049968... | 0.126748 |
network storage, depending on your environment. If you set the `emptyDir.medium` field to `"Memory"`, Kubernetes mounts a tmpfs (RAM-backed filesystem) for you instead. While tmpfs is very fast, be aware that, unlike disks, files you write count against the memory limit of the container that wrote them. A size limit ca... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volumes.md | main | kubernetes | [
0.08908697217702866,
0.02538680098950863,
0.004336112178862095,
0.030932627618312836,
0.07306604832410812,
-0.014054360799491405,
-0.048466756939888,
0.042635951191186905,
0.15464146435260773,
0.0899784043431282,
0.024567898362874985,
0.02197018265724182,
-0.019133729860186577,
-0.01208646... | 0.106633 |
If you are restricting access to specific directories on the node using admission-time validation, that restriction is only effective when you additionally require that any mounts of that `hostPath` volume are \*\*read only\*\*. If you allow a read-write mount of any host path by an untrusted Pod, the containers in tha... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volumes.md | main | kubernetes | [
0.07191845774650574,
0.028339743614196777,
0.046098463237285614,
0.04719734564423561,
0.04830636456608772,
-0.07077760249376297,
-0.030472109094262123,
0.016140222549438477,
0.07584342360496521,
0.06312570720911026,
-0.022442078217864037,
0.019084054976701736,
0.010850848630070686,
-0.0101... | 0.138646 |
node" codelang="yaml" >}} --- # This manifest mounts /data/foo on the host as /foo inside the # single container that runs within the hostpath-example-linux Pod. # # The mount into the container is read-only. apiVersion: v1 kind: Pod metadata: name: hostpath-example-linux spec: os: { name: linux } nodeSelector: kuberne... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volumes.md | main | kubernetes | [
0.05620682239532471,
0.012681413441896439,
0.05540802329778671,
0.01570642925798893,
0.03520427271723747,
-0.056404124945402145,
0.00034697502269409597,
0.009686507284641266,
0.07088876515626907,
0.02429313398897648,
0.023270346224308014,
-0.07546486705541611,
-0.020466087386012077,
0.0294... | 0.099813 |
be reported on the Pod reason and message. The types of objects that may be mounted by this volume are defined by the container runtime implementation on a host machine. At a minimum, they must include all valid types supported by the container image field. The OCI object gets mounted in a single directory (`spec.conta... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volumes.md | main | kubernetes | [
0.07576730102300644,
0.004077164456248283,
0.04772435873746872,
-0.0016097120242193341,
0.06534940749406815,
-0.06591406464576721,
-0.01068633422255516,
0.04837307333946228,
0.09830173850059509,
-0.022759253159165382,
-0.0017505198484286666,
-0.05705313757061958,
0.009862983599305153,
0.06... | 0.109293 |
PersistentVolume metadata: name: example-pv spec: capacity: storage: 100Gi volumeMode: Filesystem accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Delete storageClassName: local-storage local: path: /mnt/disks/ssd1 nodeAffinity: required: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname o... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volumes.md | main | kubernetes | [
-0.015627656131982803,
-0.017148509621620178,
0.029470175504684448,
0.0461537167429924,
-0.023884901776909828,
0.022867213934659958,
-0.05385013297200203,
-0.009343067184090614,
0.09294125437736511,
0.018315570428967476,
-0.05511118844151497,
-0.027446413412690163,
0.02116304449737072,
0.0... | 0.055833 |
an existing PortworxVolume with the name `pxvol` before using it in the Pod. {{< /note >}} #### Portworx CSI migration {{< feature-state feature\_gate\_name="CSIMigrationPortworx" >}} In Kubernetes {{% skew currentVersion %}}, all operations for the in-tree Portworx volumes are redirected to the `pxd.portworx.com` Cont... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volumes.md | main | kubernetes | [
0.009643667377531528,
-0.04435793310403824,
-0.0005909540923312306,
-0.021380800753831863,
-0.02563927322626114,
-0.02025778405368328,
-0.039382338523864746,
-0.029340270906686783,
0.04938493296504021,
0.0225774385035038,
0.011752110905945301,
0.012979193590581417,
0.03851373493671417,
0.0... | 0.090949 |
(CSI), and also FlexVolume (which is deprecated). These plugins enable storage vendors to create custom storage plugins without adding their plugin source code to the Kubernetes repository. Previously, all volume plugins were "in-tree". The "in-tree" plugins were built, linked, compiled, and shipped with the core Kuber... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volumes.md | main | kubernetes | [
-0.02871466428041458,
-0.05655796453356743,
-0.016761137172579765,
0.013008742593228817,
-0.010883825831115246,
-0.03332781791687012,
-0.05098699778318405,
0.03643942251801491,
0.0653766542673111,
0.07723827660083771,
0.0013468503020703793,
-0.005376818124204874,
0.0077460347674787045,
0.0... | 0.159271 |
via the `volume\_context` field in the `ControllerPublishVolumeRequest`, `NodeStageVolumeRequest`, and `NodePublishVolumeRequest`. \* `controllerPublishSecretRef`: A reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI `ControllerPublishVolume` and `ControllerUnp... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volumes.md | main | kubernetes | [
0.010345740243792534,
-0.01889370195567608,
0.00691952696070075,
0.011608272790908813,
0.008763876743614674,
0.011491390876471996,
0.025128798559308052,
-0.000988165382295847,
0.11266468465328217,
0.03980713337659836,
0.031097369268536568,
-0.06792382895946503,
0.05496963486075401,
-0.0877... | 0.160443 |
or PersistentVolumeClaims (referring to in-tree plugins) when transitioning to a CSI driver that supersedes an in-tree plugin. {{< note >}} Existing PVs created by an in-tree volume plugin can still be used in the future without any configuration changes, even after the migration to CSI is completed for that volume typ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volumes.md | main | kubernetes | [
-0.005147307179868221,
-0.029939966276288033,
0.014683916233479977,
-0.0009697889909148216,
0.031446997076272964,
-0.03080626204609871,
-0.028089724481105804,
-0.010113881900906563,
0.052806172519922256,
0.04397372528910637,
0.032948680222034454,
-0.017328450456261635,
0.02389427460730076,
... | 0.087014 |
mounted there. Similarly, if any Pod with `Bidirectional` mount propagation to the same volume mounts anything there, the container with `HostToContainer` mount propagation will see it. This mode is equal to `rslave` mount propagation as described in the [`mount(8)`](https://man7.org/linux/man-pages/man8/mount.8.html) ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volumes.md | main | kubernetes | [
0.052331846207380295,
0.0016295370878651738,
0.04188805818557739,
0.011774363927543163,
0.013052307069301605,
-0.07681936025619507,
-0.048025552183389664,
0.018084870651364326,
0.058900076895952225,
-0.007603529375046492,
0.008029960095882416,
0.005677800625562668,
0.004613928496837616,
-0... | 0.11603 |
Dynamic volume provisioning allows storage volumes to be created on-demand. Without dynamic provisioning, cluster administrators have to manually make calls to their cloud or storage provider to create new storage volumes, and then create [`PersistentVolume` objects](/docs/concepts/storage/persistent-volumes/) to repre... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/dynamic-provisioning.md | main | kubernetes | [
-0.011999002657830715,
0.004485737532377243,
0.017000872641801834,
0.07468497008085251,
-0.07576479762792587,
-0.0011611009249463677,
-0.01640816405415535,
0.011259774677455425,
0.09346860647201538,
0.024566123262047768,
-0.04060031846165657,
-0.021836737170815468,
0.0652887299656868,
0.02... | 0.09846 |
the most recently created default StorageClass. ## Topology Awareness In [Multi-Zone](/docs/setup/best-practices/multiple-zones/) clusters, Pods can be spread across Zones in a Region. Single-Zone storage backends should be provisioned in the Zones where Pods are scheduled. This can be accomplished by setting the [Volu... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/dynamic-provisioning.md | main | kubernetes | [
0.08350265026092529,
-0.07330183684825897,
-0.04080262780189514,
0.025361238047480583,
-0.02018948644399643,
-0.012251784093677998,
-0.10314327478408813,
0.03286922350525856,
-0.015623015351593494,
0.04588726535439491,
-0.013698983937501907,
0.0169083159416914,
-0.011440964415669441,
-0.00... | 0.121394 |
{{< feature-state feature\_gate\_name="VolumeAttributesClass" >}} This page assumes that you are familiar with [StorageClasses](/docs/concepts/storage/storage-classes/), [volumes](/docs/concepts/storage/volumes/) and [PersistentVolumes](/docs/concepts/storage/persistent-volumes/) in Kubernetes. A VolumeAttributesClass ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volume-attributes-classes.md | main | kubernetes | [
-0.051943160593509674,
0.014168213121592999,
0.039000265300273895,
0.011719712056219578,
-0.05009860917925835,
-0.010575768537819386,
0.03376656398177147,
-0.06631153076887131,
0.06868965178728104,
0.012838912196457386,
-0.057218942791223526,
0.010957563295960426,
0.041465308517217636,
-0.... | 0.058793 |
{{< feature-state for\_k8s\_version="v1.21" state="alpha" >}} {{< glossary\_tooltip text="CSI" term\_id="csi" >}} volume health monitoring allows CSI Drivers to detect abnormal volume conditions from the underlying storage systems and report them as events on {{< glossary\_tooltip text="PVCs" term\_id="persistent-volum... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/storage/volume-health-monitoring.md | main | kubernetes | [
-0.07931561022996902,
0.05620803311467171,
0.06579077243804932,
0.012395517900586128,
0.00035596100497059524,
-0.028666406869888306,
0.1044178158044815,
-0.021331045776605606,
0.08047115057706833,
0.009692047722637653,
0.02930580824613571,
-0.06410321593284607,
0.01615528017282486,
0.01741... | 0.161483 |
If you want to control traffic flow at the IP address or port level for TCP, UDP, and SCTP protocols, then you might consider using Kubernetes NetworkPolicies for particular applications in your cluster. NetworkPolicies are an application-centric construct which allow you to specify how a {{< glossary\_tooltip text="po... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/network-policies.md | main | kubernetes | [
0.0010393868433311582,
-0.047689199447631836,
0.002772331004962325,
-0.007307649124413729,
-0.04775223135948181,
0.0724111795425415,
0.04240997135639191,
-0.006158354226499796,
0.03924407437443733,
0.056225985288619995,
-0.05986827239394188,
-0.039314430207014084,
0.0030581080354750156,
-0... | 0.180218 |
the connections allowed in that direction from that pod is the union of what the applicable policies allow. Thus, order of evaluation does not affect the policy result. For a connection from a source pod to a destination pod to be allowed, both the egress policy on the source pod and the ingress policy on the destinati... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/network-policies.md | main | kubernetes | [
-0.014719601720571518,
0.05959124118089676,
0.0339830256998539,
0.009584128856658936,
-0.01479928195476532,
0.017325080931186676,
0.024562714621424675,
-0.033262237906455994,
0.01099588256329298,
0.08669853210449219,
-0.037561677396297455,
0.04967385157942772,
0.01583443209528923,
-0.02819... | 0.123141 |
selects particular namespaces for which all Pods should be allowed as ingress sources or egress destinations. \*\*namespaceSelector\*\* \*and\* \*\*podSelector\*\*: A single `to`/`from` entry that specifies both `namespaceSelector` and `podSelector` selects particular Pods within particular namespaces. Be careful to us... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/network-policies.md | main | kubernetes | [
-0.009545957669615746,
-0.012546523474156857,
0.015078946016728878,
0.014350240118801594,
0.010661465115845203,
-0.0034608403220772743,
0.1378049999475479,
-0.09067415446043015,
0.07467613369226456,
0.0229016225785017,
0.02209281735122204,
-0.0884178876876831,
0.004956847056746483,
-0.0423... | 0.158183 |
egress policy also blocks DNS traffic. If your workloads need DNS resolution, you must add a separate NetworkPolicy that allows egress to your cluster's DNS service. {{< /caution >}} ### Allow all egress traffic If you want to allow all connections from all pods in a namespace, you can create a policy that explicitly a... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/network-policies.md | main | kubernetes | [
0.010186688974499702,
0.03361072018742561,
0.060926586389541626,
0.013075144030153751,
-0.04213837906718254,
-0.002411786001175642,
0.05601731687784195,
-0.02770281583070755,
0.01370171457529068,
0.07832212001085281,
-0.023401621729135513,
-0.0054679992608726025,
-0.027011612430214882,
-0.... | 0.158224 |
to directly specify the name of the namespaces in a NetworkPolicy. You must use a `namespaceSelector` with `matchLabels` or `matchExpressions` to select the namespaces based on their labels. {{< /note >}} ## Targeting a Namespace by its name The Kubernetes control plane sets an immutable label `kubernetes.io/metadata.n... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/network-policies.md | main | kubernetes | [
-0.041509129106998444,
-0.029956387355923653,
0.001550368033349514,
0.04201136529445648,
-0.004020905587822199,
0.010242398828268051,
0.03705734759569168,
-0.03173721954226494,
0.07532992213964462,
0.003547285683453083,
-0.027395281940698624,
-0.10547219216823578,
0.020693767815828323,
-0.... | 0.126219 |
to/from the node IP. (This is the most common implementation.) This applies when 1. a `hostNetwork` pod is selected by `spec.podSelector`. ```yaml ... spec: podSelector: matchLabels: role: client ... ``` 1. a `hostNetwork` pod is selected by a `podSelector` or `namespaceSelector` in an `ingress` or `egress` rule. ```ya... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/network-policies.md | main | kubernetes | [
-0.022688057273626328,
0.01889711245894432,
0.035760700702667236,
-0.013642136007547379,
-0.004792334977537394,
0.011784069240093231,
0.05758952721953392,
-0.05216686427593231,
0.04510696232318878,
0.0959484726190567,
-0.036637164652347565,
-0.012500430457293987,
0.02490529976785183,
-0.03... | 0.133946 |
{{< feature-state for\_k8s\_version="v1.21" state="stable" >}} {{< glossary\_definition term\_id="endpoint-slice" length="short" >}} ## EndpointSlice API {#endpointslice-resource} In Kubernetes, an EndpointSlice contains references to a set of network endpoints. The control plane automatically creates EndpointSlices fo... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/endpoint-slices.md | main | kubernetes | [
-0.050849564373493195,
-0.021442880854010582,
0.06040291488170624,
-0.0369793102145195,
-0.08037085086107254,
0.0002663839841261506,
0.056271154433488846,
-0.056866880506277084,
0.06469857692718506,
0.02612043172121048,
-0.02076837420463562,
-0.07928316295146942,
-0.03603855147957802,
0.01... | 0.115544 |
can manage EndpointSlices without interfering with each other, Kubernetes defines the {{< glossary\_tooltip term\_id="label" text="label" >}} `endpointslice.kubernetes.io/managed-by`, which indicates the entity managing an EndpointSlice. The endpoint slice controller sets `endpointslice-controller.k8s.io` as the value ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/endpoint-slices.md | main | kubernetes | [
-0.032541047781705856,
-0.04364633560180664,
0.013463491573929787,
-0.03986993804574013,
-0.04328569397330284,
-0.00895567424595356,
0.060752157121896744,
-0.03376049920916557,
0.12518519163131714,
0.029755912721157074,
0.039561089128255844,
-0.002670726040378213,
-0.026022030040621758,
0.... | 0.162981 |
user workloads that expect {{}} to route traffic based on Endpoints resources, the cluster's control plane mirrors most user-created Endpoints resources to corresponding EndpointSlices. (However, this feature, like the rest of the Endpoints API, is deprecated. Users who manually specify endpoints for selectorless Servi... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/endpoint-slices.md | main | kubernetes | [
0.03339028358459473,
-0.01757519692182541,
0.015050917863845825,
0.011503838934004307,
-0.033326826989650726,
0.005199800245463848,
0.04267757385969162,
-0.07724831998348236,
0.07582063227891922,
0.05524648353457451,
-0.05585288628935814,
-0.026862477883696556,
-0.04851092770695686,
-0.002... | 0.165627 |
{{< feature-state for\_k8s\_version="v1.26" state="stable" >}} \_Service Internal Traffic Policy\_ enables internal traffic restrictions to only route internal traffic to endpoints within the node the traffic originated from. The "internal" traffic here refers to traffic originated from Pods in the current cluster. Thi... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service-traffic-policy.md | main | kubernetes | [
-0.013033296912908554,
-0.003476128913462162,
0.06445696204900742,
-0.040334198623895645,
-0.06132460758090019,
-0.030105018988251686,
0.036419231444597244,
-0.037559133023023605,
0.005835453048348427,
0.05934176221489906,
-0.0525454506278038,
-0.06109858304262161,
-0.022861793637275696,
-... | 0.150157 |
{{< note >}} The Kubernetes project recommends using [Gateway](https://gateway-api.sigs.k8s.io/) instead of [Ingress](/docs/concepts/services-networking/ingress/). The Ingress API has been frozen. This means that: \* The Ingress API is generally available, and is subject to the [stability guarantees](/docs/reference/us... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/ingress-controllers.md | main | kubernetes | [
-0.07046374678611755,
0.023758385330438614,
0.06350216269493103,
0.007281945087015629,
0.018847672268748283,
0.011248968541622162,
-0.023539235815405846,
-0.025379322469234467,
0.07405360043048859,
0.09093044698238373,
-0.009317146614193916,
0.012628012336790562,
-0.020568421110510826,
-0.... | 0.193641 |
deploy any number of ingress controllers using [ingress class](/docs/concepts/services-networking/ingress/#ingress-class) within a cluster. Note the `.metadata.name` of your ingress class resource. When you create an ingress you would need that name to specify the `ingressClassName` field on your Ingress object (refer ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/ingress-controllers.md | main | kubernetes | [
-0.011273828335106373,
-0.018194623291492462,
0.02803337574005127,
-0.003807715605944395,
0.01853516697883606,
0.035625990480184555,
0.0685010775923729,
-0.0035199997946619987,
0.023348860442638397,
0.07570566982030869,
0.02422310784459114,
-0.050342097878456116,
0.017313476651906967,
-0.0... | 0.192402 |
{{< feature-state for\_k8s\_version="v1.23" state="stable" >}} IPv4/IPv6 dual-stack networking enables the allocation of both IPv4 and IPv6 addresses to {{< glossary\_tooltip text="Pods" term\_id="pod" >}} and {{< glossary\_tooltip text="Services" term\_id="service" >}}. IPv4/IPv6 dual-stack networking is enabled by de... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/dual-stack.md | main | kubernetes | [
0.03058953769505024,
-0.03081228770315647,
0.07637683302164078,
-0.008849849924445152,
-0.060986146330833435,
0.08496566116809845,
-0.05528591200709343,
-0.06789015978574753,
0.017216084524989128,
0.025845758616924286,
-0.011809994466602802,
-0.04524512216448784,
-0.06752965599298477,
-0.0... | 0.11821 |
an existing Service. {{< /note >}} You can set `.spec.ipFamilies` to any of the following array values: - `["IPv4"]` - `["IPv6"]` - `["IPv4","IPv6"]` (dual stack) - `["IPv6","IPv4"]` (dual stack) The first family you list is used for the legacy `.spec.clusterIP` field. ### Dual-stack Service configuration scenarios The... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/dual-stack.md | main | kubernetes | [
-0.014735838398337364,
-0.02469630539417267,
0.0035155033692717552,
-0.01635027304291725,
-0.036899954080581665,
0.030467621982097626,
-0.018897581845521927,
-0.04083726555109024,
0.03934205323457718,
0.02243996411561966,
-0.004999035038053989,
-0.038997549563646317,
-0.04722537100315094,
... | 0.132311 |
selector: app.kubernetes.io/name: MyApp ``` #### Switching Services between single-stack and dual-stack Services can be changed from single-stack to dual-stack and from dual-stack to single-stack. 1. To change a Service from single-stack to dual-stack, change `.spec.ipFamilyPolicy` from `SingleStack` to `PreferDualStac... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/dual-stack.md | main | kubernetes | [
0.0011108232429251075,
-0.06242837756872177,
0.06051556393504143,
-0.04504521191120148,
-0.08280476927757263,
0.019668390974402428,
-0.03465991094708443,
-0.04821963235735893,
0.0699719488620758,
0.034589797258377075,
-0.006474699825048447,
-0.08085132390260696,
-0.05985286086797714,
-0.02... | 0.010426 |
Make network services available by using an extensible, role-oriented, protocol-aware configuration mechanism. [Gateway API](https://gateway-api.sigs.k8s.io/) is an {{}} containing API [kinds](https://gateway-api.sigs.k8s.io/references/spec/) that provide dynamic infrastructure provisioning and advanced traffic routing... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/gateway.md | main | kubernetes | [
-0.000576856080442667,
0.0009230999858118594,
0.02721594274044037,
-0.02612561732530594,
-0.09122608602046967,
0.023153426125645638,
0.013039088808000088,
0.030469980090856552,
0.038384515792131424,
0.01994279958307743,
-0.10429506003856659,
-0.03030567616224289,
0.004698611795902252,
-0.0... | 0.229141 |
name: example-gateway namespace: example-namespace spec: gatewayClassName: example-class listeners: - name: http protocol: HTTP port: 80 hostname: "www.example.com" allowedRoutes: namespaces: from: Same ``` In this example, an instance of traffic handling infrastructure is programmed to listen for HTTP traffic on port ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/gateway.md | main | kubernetes | [
-0.06392834335565567,
-0.013829914852976799,
-0.006956859026104212,
-0.010615277104079723,
-0.05848880112171173,
-0.04549885168671608,
0.01857895590364933,
-0.04272450879216194,
0.049605805426836014,
-0.0007097342167980969,
-0.05534573271870613,
-0.01606461964547634,
-0.011935302056372166,
... | 0.122221 |
a Gateway and an HTTPRoute: {{< figure src="/docs/images/gateway-request-flow.svg" alt="A diagram that provides an example of HTTP traffic being routed to a Service by using a Gateway and an HTTPRoute" class="diagram-medium" >}} In this example, the request flow for a Gateway implemented as a reverse proxy is: 1. The c... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/gateway.md | main | kubernetes | [
-0.06427282840013504,
-0.011939785443246365,
0.05235781520605087,
-0.03564449027180672,
-0.09125757217407227,
-0.0950801819562912,
0.004654413089156151,
-0.008611706085503101,
0.0691324770450592,
0.0012159564066678286,
-0.08521981537342072,
0.06273402273654938,
-0.01624746434390545,
-0.060... | 0.099719 |
In Kubernetes, [Services](/docs/concepts/services-networking/service/) are an abstract way to expose an application running on a set of Pods. Services can have a cluster-scoped virtual IP address (using a Service of `type: ClusterIP`). Clients can connect using that virtual IP address, and Kubernetes then load-balances... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/cluster-ip-allocation.md | main | kubernetes | [
-0.02728724293410778,
-0.022128542885184288,
0.029045002534985542,
-0.022791579365730286,
-0.038917433470487595,
0.04958697035908699,
0.056921180337667465,
-0.04561040922999382,
0.14854052662849426,
0.04733125492930412,
-0.04151209816336632,
0.004225835204124451,
0.005119341891258955,
-0.0... | 0.186381 |
10.96.0.0/20 "Static" : 256 "Dynamic" : 3838 {{< /mermaid >}} ### Example 3 {#allocation-example-3} This example uses the IP address range: 10.96.0.0/16 (CIDR notation) for the IP addresses of Services. Range Size: 216 - 2 = 65534 Band Offset: `min(max(16, 65536/16), 256)` = `min(4096, 256)` = 256 Static band start: 10... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/cluster-ip-allocation.md | main | kubernetes | [
0.03348657861351967,
0.05907999351620674,
-0.023106319829821587,
-0.045782413333654404,
-0.05230946093797684,
-0.02119813673198223,
0.0419851578772068,
-0.0093269357457757,
-0.0478663295507431,
-0.07889444380998611,
0.007829779759049416,
-0.06788165867328644,
0.01305982656776905,
-0.009773... | 0.09356 |
{{< glossary\_definition term\_id="service" length="short" prepend="In Kubernetes, a Service is" >}} A key aim of Services in Kubernetes is that you don't need to modify your existing application to use an unfamiliar service discovery mechanism. You can run code in Pods, whether this is a code designed for a cloud-nati... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md | main | kubernetes | [
-0.03861651569604874,
-0.009227069094777107,
0.0892239511013031,
-0.01902945339679718,
-0.04158494248986244,
-0.024530842900276184,
0.07997801899909973,
-0.04341964051127434,
0.07005385309457779,
0.039513226598501205,
0.0031212051399052143,
-0.03511407971382141,
0.024311991408467293,
-0.04... | 0.115485 |
>}} for matching EndpointSlices. Kubernetes updates the EndpointSlices for a Service whenever the set of Pods in a Service changes. For non-native applications, Kubernetes offers ways to place a network port or load balancer in between your application and the backend Pods. Either way, your workload can use these [serv... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md | main | kubernetes | [
-0.04236474260687828,
-0.029813634231686592,
0.006027990486472845,
-0.044716741889715195,
-0.06309807300567627,
-0.044258952140808105,
0.056906506419181824,
-0.010601509362459183,
0.09138733893632889,
0.012540234252810478,
-0.0417063906788826,
-0.035015977919101715,
-0.01272389106452465,
-... | 0.214775 |
point your Service to a Service in a different {{< glossary\_tooltip term\_id="namespace" >}} or on another cluster. \* You are migrating a workload to Kubernetes. While evaluating the approach, you run only a portion of your backends in Kubernetes. In any of these scenarios you can define a Service \_without\_ specify... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md | main | kubernetes | [
-0.013124287128448486,
-0.04537350311875343,
0.04753478243947029,
-0.03595367819070816,
-0.04285929352045059,
-0.02267542853951454,
0.06908748298883438,
-0.04434320330619812,
0.08639423549175262,
0.03971917927265167,
-0.02567177265882492,
-0.08195298165082932,
0.0003753617638722062,
0.0165... | 0.132848 |
the [ExternalName](#externalname) section. ### EndpointSlices {{< feature-state for\_k8s\_version="v1.21" state="stable" >}} [EndpointSlices](/docs/concepts/services-networking/endpoint-slices/) are objects that represent a subset (a \_slice\_) of the backing network endpoints for a Service. Your Kubernetes cluster tra... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md | main | kubernetes | [
0.0016132149612531066,
-0.05918336659669876,
0.05301525816321373,
-0.003927349112927914,
-0.015061942860484123,
0.029721030965447426,
0.009020037949085236,
-0.019792160019278526,
0.09319967776536942,
0.010242059826850891,
-0.006278490647673607,
-0.039630644023418427,
-0.004200128838419914,
... | 0.159641 |
glossary\_tooltip term\_id="name" text="names">}} in general, names for ports must only contain lowercase alphanumeric characters and `-`. Port names must also start and end with an alphanumeric character. For example, the names `123-abc` and `web` are valid, but `123\_abc` and `-web` are not. {{< /note >}} ## Service ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md | main | kubernetes | [
-0.054917607456445694,
-0.043490584939718246,
0.04637778177857399,
-0.046559471637010574,
-0.07224290072917938,
0.004079385660588741,
0.06812465190887451,
-0.043665241450071335,
0.08628369867801666,
0.0073841642588377,
0.0028785387985408306,
-0.05760796368122101,
-0.02620532549917698,
-0.0... | 0.123617 |
(the same port number on every Node) into your Service. Your Service reports the allocated port in its `.spec.ports[\*].nodePort` field. Using a NodePort gives you the freedom to set up your own load balancing solution, to configure environments that are not fully supported by Kubernetes, or even to expose one or more ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md | main | kubernetes | [
0.0022433027625083923,
-0.015168195590376854,
-0.017251964658498764,
-0.015048589557409286,
-0.03140459582209587,
0.05908215045928955,
0.019568730145692825,
-0.01847933419048786,
0.05473501235246658,
0.057784125208854675,
-0.10011658072471619,
-0.014124245382845402,
-0.014111088588833809,
... | 0.171528 |
ranges that kube-proxy should consider as local to this node. For example, if you start kube-proxy with the `--nodeport-addresses=127.0.0.0/8` flag, kube-proxy only selects the loopback interface for NodePort Services. The default for `--nodeport-addresses` is an empty list. This means that kube-proxy should consider a... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md | main | kubernetes | [
0.029126498848199844,
-0.001378157059662044,
0.015107887797057629,
-0.03416210412979126,
-0.03529496118426323,
0.03687722980976105,
0.0029498375952243805,
-0.040800660848617554,
0.020674630999565125,
0.02259097248315811,
-0.04857481271028519,
-0.002684509614482522,
-0.027687791734933853,
-... | 0.067872 |
must have the same protocol, and the protocol must be one which is supported by the cloud provider. The feature gate `MixedProtocolLBService` (enabled by default for the kube-apiserver as of v1.24) allows the use of different protocols for LoadBalancer type of Services, when there is more than one port defined. {{< not... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md | main | kubernetes | [
-0.03930828347802162,
-0.0017418868374079466,
0.012195277959108353,
-0.02644319273531437,
-0.04885073006153107,
0.00501964520663023,
-0.05610280483961105,
-0.05419349670410156,
0.04789013788104057,
0.049281053245067596,
-0.06337389349937439,
-0.019116338342428207,
0.012502268888056278,
-0.... | 0.070409 |
of the following annotations to your Service depending on the cloud service provider you're using: {{< tabs name="service\_tabs" >}} {{% tab name="Default" %}} Select one of the tabs. {{% /tab %}} {{% tab name="GCP" %}} ```yaml metadata: name: my-service annotations: networking.gke.io/load-balancer-type: "Internal" ```... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md | main | kubernetes | [
0.0019884181674569845,
0.024081453680992126,
0.029505014419555664,
-0.004961015190929174,
-0.007933061569929123,
-0.020965002477169037,
0.10431433469057083,
-0.057800959795713425,
0.093778096139431,
0.07838641107082367,
-0.016335202381014824,
-0.06739108264446259,
0.00397452712059021,
0.02... | 0.053926 |
Service allows a client to connect to whichever Pod it prefers, directly. Services that are headless don't configure routes and packet forwarding using [virtual IP addresses and proxies](/docs/reference/networking/virtual-ips/); instead, headless Services report the endpoint IP addresses of the individual pods via inte... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md | main | kubernetes | [
0.011861353181302547,
-0.008379891514778137,
0.01691899076104164,
-0.01797230914235115,
-0.0978359803557396,
0.021098442375659943,
-0.01935296319425106,
-0.012212385423481464,
0.08004670590162277,
0.04902442544698715,
-0.015758249908685684,
-0.0008811862790025771,
-0.027781710028648376,
-0... | 0.154704 |
able to find the service by doing a name lookup for `my-service` (`my-service.my-ns` would also work). Pods in other namespaces must qualify the name as `my-service.my-ns`. These names will resolve to the cluster IP assigned for the Service. Kubernetes also supports DNS SRV (Service) records for named ports. If the `my... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md | main | kubernetes | [
-0.011815275996923447,
-0.03133648633956909,
0.022515982389450073,
-0.05700449272990227,
-0.06632903963327408,
-0.0023246619384735823,
-0.0030359425581991673,
-0.01689096912741661,
0.07767399400472641,
0.053504202514886856,
-0.06534665077924728,
-0.04847731813788414,
-0.004474544897675514,
... | 0.165497 |
fit into Kubernetes: \* Follow the [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/) tutorial. \* Read about [Ingress](/docs/concepts/services-networking/ingress/), which exposes HTTP and HTTPS routes from outside the cluster to Services within your cluster. \* Read about [... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md | main | kubernetes | [
-0.00696357199922204,
-0.003545493585988879,
-0.00954581331461668,
-0.03529106080532074,
-0.0633530542254448,
0.021676087751984596,
0.00022076998720876873,
0.02001872844994068,
0.0403129905462265,
0.06654927134513855,
-0.04439372569322586,
-0.03011263720691204,
-0.008828955702483654,
-0.03... | 0.230553 |
{{< feature-state for\_k8s\_version="v1.23" state="beta" >}} {{< note >}} Prior to Kubernetes 1.27, this feature was known as \_Topology Aware Hints\_. {{}} \_Topology Aware Routing\_ adjusts routing behavior to prefer keeping traffic in the zone it originated from. In some cases this can help reduce costs or improve n... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/topology-aware-routing.md | main | kubernetes | [
-0.016779303550720215,
-0.044925421476364136,
0.05672956258058548,
0.025084948167204857,
-0.0001758920116117224,
0.030214598402380943,
0.08224525302648544,
-0.020677000284194946,
0.09260022640228271,
0.013481566682457924,
-0.03334709629416466,
-0.01828165352344513,
-0.008183577097952366,
-... | 0.162254 |
would result in some traffic being routed to other zones. ## Safeguards The Kubernetes control plane and the kube-proxy on each node apply some safeguard rules before using Topology Aware Hints. If these don't check out, the kube-proxy selects endpoints from anywhere in your cluster, regardless of the zone. 1. \*\*Insu... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/topology-aware-routing.md | main | kubernetes | [
0.04007275402545929,
-0.03439491242170334,
0.01724793203175068,
0.0025859959423542023,
0.0096685029566288,
0.022516127675771713,
-0.0006114662392064929,
-0.031204456463456154,
0.08378901332616806,
0.06481412798166275,
-0.10518420487642288,
-0.056167472153902054,
-0.020096709951758385,
-0.0... | 0.110551 |
is deployed in many different ways, there is no single heuristic for allocating endpoints to zones will work for every use case. A key goal of this feature is to enable custom heuristics to be developed if the built in heuristic does not work for your use case. The first steps to enable custom heuristics were included ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/topology-aware-routing.md | main | kubernetes | [
0.06467735767364502,
-0.022649426013231277,
-0.034616727381944656,
-0.084922656416893,
-0.049353912472724915,
0.0056010824628174305,
0.028286291286349297,
0.012710490263998508,
0.022806264460086823,
0.0863180086016655,
-0.0830225795507431,
-0.054568786174058914,
0.024203645065426826,
0.002... | 0.125598 |
Kubernetes supports running nodes on either Linux or Windows. You can mix both kinds of node within a single cluster. This page provides an overview to networking specific to the Windows operating system. ## Container networking on Windows {#networking} Networking for Windows containers is exposed through [CNI plugins]... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/windows-networking.md | main | kubernetes | [
0.040044691413640976,
0.017419040203094482,
-0.007617529481649399,
-0.009814214892685413,
-0.04020727053284645,
0.055042803287506104,
-0.009688830934464931,
-0.028026577085256577,
0.05048783868551254,
0.029739607125520706,
-0.0684860497713089,
-0.04237842559814453,
-0.021684447303414345,
-... | 0.200544 |
[win-overlay](https://www.cni.dev/plugins/current/main/win-overlay/), [Flannel VXLAN](https://github.com/flannel-io/flannel/blob/master/Documentation/backends.md#vxlan) (uses win-overlay) | win-overlay should be used when virtual container networks are desired to be isolated from underlay of hosts (e.g. for security re... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/windows-networking.md | main | kubernetes | [
-0.04223087057471275,
0.021567536517977715,
-0.02408631145954132,
-0.011767496354877949,
0.08355394750833511,
0.005023513454943895,
-0.010288076475262642,
-0.011305811814963818,
-0.0271603986620903,
-0.016638806089758873,
0.02205146662890911,
0.009411404840648174,
-0.030307188630104065,
-0... | 0.02972 |
Service: \* `NodePort` \* `ClusterIP` \* `LoadBalancer` \* `ExternalName` Windows container networking differs in some important ways from Linux networking. The [Microsoft documentation for Windows Container Networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture)... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/windows-networking.md | main | kubernetes | [
-0.05410194396972656,
-0.001527532353065908,
-0.03219174966216087,
0.0012991916155442595,
-0.05891401320695877,
0.022861534729599953,
0.020230818539857864,
-0.002642803592607379,
-0.00702710822224617,
0.035667967051267624,
-0.05325065925717354,
-0.004219169728457928,
-0.011698625981807709,
... | 0.096069 |
{{< feature-state for\_k8s\_version="v1.19" state="stable" >}} {{< glossary\_definition term\_id="ingress" length="all" >}} {{< note >}} The Kubernetes project recommends using [Gateway](https://gateway-api.sigs.k8s.io/) instead of [Ingress](/docs/concepts/services-networking/ingress/). The Ingress API has been frozen.... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/ingress.md | main | kubernetes | [
-0.05200319364666939,
0.031376682221889496,
0.08450838178396225,
0.0008818685892038047,
-0.0039529805071651936,
-0.005672886501997709,
-0.020835814997553825,
-0.03573870286345482,
0.032264143228530884,
0.050645194947719574,
0.01093367300927639,
-0.010685551911592484,
-0.02934715896844864,
... | 0.20923 |
the `ingressClassName` is omitted, a [default Ingress class](#default-ingress-class) should be defined. Some ingress controllers work even without the definition of a default IngressClass. Even if you use an ingress controller that is able to operate without any IngressClass, the Kubernetes project still recommends tha... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/ingress.md | main | kubernetes | [
-0.0780380591750145,
0.01689717546105385,
0.0471869520843029,
-0.05882062762975693,
-0.04147448390722275,
-0.028073148801922798,
0.06887312233448029,
-0.0446326769888401,
0.057739779353141785,
0.04767072573304176,
-0.023119064047932625,
-0.025922372937202454,
0.014338981360197067,
-0.04658... | 0.153249 |
A path element refers to the list of labels in the path split by the `/` separator. A request is a match for path \_p\_ if every \_p\_ is an element-wise prefix of \_p\_ of the request path. {{< note >}} If the last element of the path is a substring of the last element in request path, it is not a match (for example: ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/ingress.md | main | kubernetes | [
-0.059509601444005966,
0.05020882189273834,
0.10571525245904922,
0.008449628949165344,
-0.0147283049300313,
-0.007523278705775738,
0.0157475583255291,
0.03272806853055954,
0.039644405245780945,
-0.04314423352479935,
-0.035049472004175186,
-0.0009935343405231833,
0.009145760908722878,
-0.00... | 0.012211 |
{{< tabs name="tabs\_ingressclass\_parameter\_scope" >}} {{% tab name="Cluster" %}} The default scope for IngressClass parameters is cluster-wide. If you set the `.spec.parameters` field and don't set `.spec.parameters.scope`, or if you set `.spec.parameters.scope` to `Cluster`, then the IngressClass refers to a cluste... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/ingress.md | main | kubernetes | [
-0.03310904651880264,
0.023427192121744156,
-0.028156818822026253,
0.06436021625995636,
0.014819297008216381,
0.032110679894685745,
0.05252707004547119,
-0.021399904042482376,
-0.01653786189854145,
0.01851618103682995,
-0.012844329699873924,
-0.0860043540596962,
-0.0030282256193459034,
0.0... | 0.186691 |
as default in your cluster. {{< /caution >}} Start by defining a default IngressClass. It is recommended though, to specify the default IngressClass: {{% code\_sample file="service/networking/default-ingressclass.yaml" %}} ## Types of Ingress ### Ingress backed by a single Service {#single-service-ingress} There are ex... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/ingress.md | main | kubernetes | [
-0.012005100026726723,
0.005495742429047823,
0.007400846108794212,
0.011070377193391323,
-0.01953122951090336,
0.011158694513142109,
0.017854319885373116,
0.011979787610471249,
0.015306497924029827,
0.060693494975566864,
-0.03191160410642624,
-0.06471172720193863,
0.013211144134402275,
-0.... | 0.154778 |
controller supports SNI). The TLS secret must contain keys named `tls.crt` and `tls.key` that contain the certificate and private key to use for TLS. For example: ```yaml apiVersion: v1 kind: Secret metadata: name: testsecret-tls namespace: default data: tls.crt: base64 encoded cert tls.key: base64 encoded key type: ku... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/ingress.md | main | kubernetes | [
-0.03911970928311348,
0.07604565471410751,
-0.012935042381286621,
0.009014938026666641,
-0.03443304821848869,
-0.020637135952711105,
0.004247423727065325,
-0.00909089483320713,
0.12612015008926392,
0.07873725146055222,
-0.02148757129907608,
-0.11167161911725998,
0.020794346928596497,
0.041... | 0.038745 |
details. ## Alternatives You can expose a Service in multiple ways that don't directly involve the Ingress resource: \* Use [Service.Type=LoadBalancer](/docs/concepts/services-networking/service/#loadbalancer) \* Use [Service.Type=NodePort](/docs/concepts/services-networking/service/#type-nodeport) ## {{% heading "what... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/ingress.md | main | kubernetes | [
-0.08276408165693283,
0.028456706553697586,
0.0007959122303873301,
0.012490923516452312,
-0.0036824073176831007,
-0.007122172974050045,
0.03989144414663315,
0.034092508256435394,
0.034827083349227905,
0.037698496133089066,
-0.03329738974571228,
-0.015233771875500679,
0.02332116849720478,
-... | 0.223383 |
## The Kubernetes network model The Kubernetes network model is built out of several pieces: \* Each [pod](/docs/concepts/workloads/pods/) in a cluster gets its own unique cluster-wide IP address. \* A pod has its own private network namespace which is shared by all of the containers within the pod. Processes running i... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/_index.md | main | kubernetes | [
0.013190066441893578,
-0.015454589389264584,
0.01741638034582138,
-0.022694049403071404,
-0.0015809455653652549,
0.011483530513942242,
0.0447680689394474,
-0.05693245679140091,
0.09331093728542328,
0.018519742414355278,
-0.006720849312841892,
-0.0014436331111937761,
0.007546625565737486,
-... | 0.28602 |
be present, but it will have no effect.) \* There are many [implementations of the Gateway API](https://gateway-api.sigs.k8s.io/implementations/), some of which are specific to particular cloud environments, some more focused on "bare metal" environments, and others more generic. ## {{% heading "whatsnext" %}} The [Con... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/_index.md | main | kubernetes | [
-0.009587508626282215,
-0.023642636835575104,
0.021781377494335175,
0.007066164165735245,
-0.07140275090932846,
0.028096798807382584,
-0.030064284801483154,
0.003226189175620675,
0.028633389621973038,
0.012895324267446995,
-0.05637768283486366,
0.027612673118710518,
0.02002461440861225,
-0... | 0.22918 |
Kubernetes creates DNS records for Services and Pods. You can contact Services with consistent DNS names instead of IP addresses. Kubernetes publishes information about Pods and Services which is used to program DNS. kubelet configures Pods' DNS so that running containers can look up Services by name rather than IP. Se... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/dns-pod-service.md | main | kubernetes | [
-0.009092998690903187,
-0.05685044825077057,
0.08571381866931915,
-0.007259668782353401,
-0.0828048586845398,
-0.026591459289193153,
-0.008885516785085201,
-0.04681535065174103,
0.15199561417102814,
0.009930480271577835,
-0.042489852756261826,
-0.021615304052829742,
-0.004351576790213585,
... | 0.151996 |
a Pod in the `cafe` namespace has the IP address 172.17.0.3, is an endpoint of a Service named `barista`, and the domain name for your cluster is `cluster.local`, then the Pod would have this service-scoped DNS `A` record. ``` 172-17-0-3.barista.cafe.svc.cluster.local ``` ### Pod's hostname and subdomain fields {#pod-h... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/dns-pod-service.md | main | kubernetes | [
0.007510020397603512,
-0.033166706562042236,
0.005709060467779636,
0.025546174496412277,
-0.0022355488035827875,
-0.06519795954227448,
0.005568753927946091,
-0.024823397397994995,
0.061596017330884933,
0.00318063679151237,
-0.0387875959277153,
-0.0494295135140419,
0.004151960369199514,
-0.... | 0.19091 |
the kernel (the `nodename` field of `struct utsname`) is limited to 64 characters. If a Pod enables this feature and its FQDN is longer than 64 character, it will fail to start. The Pod will remain in `Pending` status (`ContainerCreating` as seen by `kubectl`) generating error events, such as Failed to construct FQDN f... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/dns-pod-service.md | main | kubernetes | [
0.013169187121093273,
0.02129116654396057,
-0.0011787933763116598,
-0.03884501755237579,
-0.07219447195529938,
-0.02609723061323166,
-0.03190263360738754,
-0.00024092465173453093,
0.03389820456504822,
0.040217943489551544,
0.0006621740176342428,
-0.04411035403609276,
0.004570082761347294,
... | 0.131455 |
32 search domains. - `options`: an optional list of objects where each object may have a `name` property (required) and a `value` property (optional). The contents in this property will be merged to the options generated from the specified DNS policy. Duplicate entries are removed. The following is an example Pod with ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/dns-pod-service.md | main | kubernetes | [
-0.0071593825705349445,
0.010810569860041142,
0.009869151748716831,
-0.0057246629148721695,
-0.07516303658485413,
-0.04896732047200203,
-0.03371444717049599,
-0.04547512158751488,
0.09429918229579926,
0.012666990049183369,
-0.02445380575954914,
-0.0529094822704792,
-0.054339759051799774,
-... | 0.112673 |
In order to support latency-critical and high-throughput workloads, Kubernetes offers a suite of Resource Managers. The managers aim to co-ordinate and optimize the alignment of node's resources for pods configured with a specific requirement for CPUs, devices, and memory (hugepages) resources. ## Topology manager {{< ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/resource-managers.md | main | kubernetes | [
0.04516463726758957,
-0.004214319866150618,
-0.017393196001648903,
0.033421166241168976,
-0.03542371839284897,
-0.01399438176304102,
-0.008836707100272179,
-0.03037116676568985,
0.06615132838487625,
0.030306534841656685,
-0.049125853925943375,
-0.040917206555604935,
-0.02980300784111023,
-... | 0.236563 |
become empty. {{< /note >}} As `Guaranteed` pods whose containers fit the requirements for being statically assigned are scheduled to the node, CPUs are removed from the shared pool and placed in the cpuset for the container. CFS quota is not used to bound the CPU usage of these containers as their usage is bound by th... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/resource-managers.md | main | kubernetes | [
-0.012052038684487343,
0.05145089328289032,
0.003863647812977433,
0.058830197900533676,
0.035647545009851456,
-0.06140480935573578,
0.039386652410030365,
-0.026408685371279716,
0.06756361573934555,
-0.01886414922773838,
-0.034234318882226944,
0.00006901428423589095,
-0.023259522393345833,
... | 0.173947 |
default) : Align CPUs by uncore (Last-Level) cache boundary on a best-effort way (available since Kubernetes v1.32) You can toggle groups of options on and off based upon their maturity level using the following feature gates: \* `CPUManagerPolicyBetaOptions` (default enabled). Disable to hide beta-level options. \* `C... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/resource-managers.md | main | kubernetes | [
0.02309064380824566,
0.027223393321037292,
0.01631251536309719,
0.014085079543292522,
-0.04627516493201256,
0.018879272043704987,
-0.04135787859559059,
-0.024085480719804764,
0.05105382204055786,
0.017843572422862053,
-0.014063327573239803,
-0.0548926405608654,
-0.08029165863990784,
-0.078... | 0.097144 |
ensures that CPUs are distributed across as many physical cores as possible, reducing the contention on the same physical core and thereby improving overall performance. However, it is important to note that this strategy might be less effective when the system is heavily loaded. Under such conditions, the benefit of r... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/resource-managers.md | main | kubernetes | [
-0.005937330424785614,
0.04128780961036682,
0.03555385023355484,
0.05190546065568924,
-0.002650235081091523,
0.030145706608891487,
-0.04295564815402031,
0.00501085864380002,
0.13144566118717194,
-0.01564740389585495,
-0.01842377707362175,
-0.025983713567256927,
-0.024223657324910164,
-0.08... | 0.22635 |
a kubelet component that allocates hardware devices to pods using the device plugin API. It consults with the Topology Manager, using topology information provided by device plugins, to make resource assignment decisions. To learn more, read [Device Plugin Integration with the Topology Manager](/docs/concepts/extend-ku... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/resource-managers.md | main | kubernetes | [
0.003157265018671751,
-0.0034801079891622066,
0.02013235166668892,
0.028342409059405327,
0.01068141683936119,
-0.029465001076459885,
0.01386671420186758,
0.01066395454108715,
0.0479670949280262,
0.017858009785413742,
-0.047649532556533813,
-0.027568845078349113,
0.0019665900617837906,
-0.0... | 0.240146 |
form a shared pool that is shared among all other containers in the pod that do not receive an exclusive allocation. While containers in this pool share resources with each other, they are strictly isolated from the exclusive slices and the general node-wide shared pool. Note that when standard init containers run to c... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/resource-managers.md | main | kubernetes | [
0.02584702894091606,
0.029467880725860596,
0.007139471359550953,
0.033161502331495285,
0.0612374022603035,
-0.07042457908391953,
0.0287754125893116,
-0.041487593203783035,
0.04630894958972931,
0.015736930072307587,
-0.028558004647493362,
-0.027469366788864136,
-0.01044781319797039,
0.00040... | 0.234564 |
the containers in the following pod spec, where the Topology Manager scope is `container` and the pod represents a workload with an infrastructure sidecar and two application workers, with a total budget of 4 CPUs. The `infrastructure-sidecar` gets an exclusive, NUMA-aligned 2 CPU slice. The two application workers (`w... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/resource-managers.md | main | kubernetes | [
0.01841544732451439,
0.011473064310848713,
0.009660767391324043,
0.03498886525630951,
0.04440002143383026,
-0.08888427168130875,
-0.01168082095682621,
-0.02270900085568428,
0.013316439464688301,
0.003790492657572031,
-0.016603529453277588,
-0.03331094607710838,
-0.041513387113809586,
-0.03... | 0.19853 |
You've deployed your application and exposed it via a Service. Now what? Kubernetes provides a number of tools to help you manage your application deployment, including scaling and updating. ## Organizing resource configurations Many applications require multiple resources to be created, such as a Deployment along with... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/management.md | main | kubernetes | [
-0.024295929819345474,
-0.00355789577588439,
0.016972551122307777,
0.0017328208778053522,
-0.05263135954737663,
-0.013384640216827393,
0.010869761928915977,
0.0074875676073133945,
0.1102997362613678,
0.03647274896502495,
-0.06764162331819534,
-0.016773981973528862,
0.0007219490362331271,
0... | 0.064752 |
``` With the above commands, first you create resources under `docs/concepts/cluster-administration/nginx/` and print the resources created with `-o name` output format (print each resource as resource/name). Then you `grep` only the Service, and then print it with [`kubectl get`](/docs/reference/kubectl/generated/kube... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/management.md | main | kubernetes | [
-0.0596601702272892,
0.04524252191185951,
0.005502379033714533,
0.003830353496596217,
-0.020855523645877838,
-0.05000688135623932,
0.0371612012386322,
-0.05309530347585678,
0.05687590315937996,
0.003745708614587784,
-0.009424020536243916,
-0.0854000672698021,
0.02476242370903492,
0.0100019... | 0.081291 |
### Managing rollouts You can use [`kubectl rollout`](/docs/reference/kubectl/generated/kubectl\_rollout/) to manage a progressive update of an existing application. For example: ```shell kubectl apply -f my-deployment.yaml # wait for rollout to finish kubectl rollout status deployment/my-deployment --timeout 10m # 10 ... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/management.md | main | kubernetes | [
0.05471264198422432,
-0.007392875850200653,
0.015139790251851082,
-0.024966731667518616,
-0.02817121334373951,
-0.0037581028882414103,
-0.05517268180847168,
-0.044643107801675797,
0.07054761797189713,
0.027063073590397835,
0.015206430107355118,
-0.013073228299617767,
-0.025772714987397194,
... | 0.090383 |
resources you've created. ### kubectl apply It is suggested to maintain a set of configuration files in source control (see [configuration as code](https://martinfowler.com/bliki/InfrastructureAsCode.html)), so that they can be maintained and versioned along with the code for the resources they configure. Then, you can... | https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/management.md | main | kubernetes | [
-0.017150012776255608,
0.010478782467544079,
0.05144495517015457,
0.008921965956687927,
-0.027357397601008415,
-0.0200608242303133,
-0.06091630831360817,
-0.04250495508313179,
0.012989301234483719,
0.028245242312550545,
-0.027957884594798088,
-0.032102085649967194,
-0.02084285393357277,
-0... | 0.029846 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.