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 |
|---|---|---|---|---|---|
MiB: {{% code\_sample file="pods/resource/memory-request-limit-2.yaml" options="hl\_lines=10-14" %}} In the `args` section of the configuration file, you can see that the Container will attempt to allocate 250 MiB of memory, which is well above the 100 MiB limit. Create the Pod: ```shell kubectl apply -f https://k8s.io... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-memory-resource.md | main | kubernetes | [
0.06420023739337921,
0.026794051751494408,
0.020966414362192154,
0.03622736036777496,
-0.0381595604121685,
-0.07586009055376053,
-0.02300173044204712,
0.08647585660219193,
0.037365492433309555,
0.06964601576328278,
-0.017468534409999847,
-0.014996083453297615,
-0.03310822695493698,
-0.0227... | 0.147957 |
``` View detailed information about the Pod, including events: ```shell kubectl describe pod memory-demo-3 --namespace=mem-example ``` The output shows that the Container cannot be scheduled because of insufficient memory on the Nodes: ``` Events: ... Reason Message ------ ------- ... FailedScheduling No nodes are avai... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-memory-resource.md | main | kubernetes | [
0.07335331290960312,
0.0616728849709034,
-0.023055871948599815,
0.057729754596948624,
-0.023584427312016487,
-0.02235282026231289,
0.039114922285079956,
0.05384473502635956,
0.08282189816236496,
0.059816379100084305,
0.011690226383507252,
-0.07422415912151337,
0.024182690307497978,
-0.0288... | 0.240556 |
This page shows how to attach handlers to Container lifecycle events. Kubernetes supports the postStart and preStop events. Kubernetes sends the postStart event immediately after a Container is started, and it sends the preStop event immediately before the Container is terminated. A Container may specify one handler pe... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md | main | kubernetes | [
0.004820053465664387,
0.036700863391160965,
0.052587490528821945,
0.016232214868068695,
-0.006443624384701252,
0.015168777666985989,
-0.015218297950923443,
-0.04677460715174675,
0.038242846727371216,
0.0740223303437233,
-0.03312154859304428,
0.016752002760767937,
-0.06526726484298706,
0.02... | 0.101415 |
{{< feature-state feature\_gate\_name="ImageVolume" >}} This page shows how to configure a pod using image volumes. This allows you to mount content from OCI registries inside containers. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} - The container runtime needs to... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/image-volumes.md | main | kubernetes | [
0.0639309361577034,
-0.010270180180668831,
0.022075658664107323,
0.04335450381040573,
0.021931614726781845,
-0.07779058814048767,
-0.02323555387556553,
0.09513145685195923,
-0.03045758605003357,
0.0368335135281086,
-0.009086680598556995,
-0.07319872081279755,
-0.00350167672149837,
0.057822... | 0.100793 |
{{< feature-state for\_k8s\_version="v1.26" state="stable" >}} Windows HostProcess containers enable you to run containerized workloads on a Windows host. These containers operate as normal processes but have access to the host network namespace, storage, and devices when given the appropriate user privileges. HostProc... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md | main | kubernetes | [
0.025256022810935974,
0.04624851793050766,
0.014535984955728054,
0.026208508759737015,
0.0017357239266857505,
0.0032838608603924513,
0.002501501701772213,
-0.03670573607087135,
0.0014903561677783728,
0.06678163260221481,
-0.08329793065786362,
-0.002558105392381549,
-0.000309377268422395,
0... | 0.175726 |
on the host. - Both Named pipe mounts and Unix domain sockets are \*\*not\*\* supported and should instead be accessed via their path on the host (e.g. \\\\.\\pipe\\\\*) ## HostProcess Pod configuration requirements Enabling a Windows HostProcess pod requires setting the right configurations in the pod security configu... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md | main | kubernetes | [
0.08135656267404556,
-0.011470288038253784,
-0.0013188617303967476,
-0.037031468003988266,
-0.044130317866802216,
-0.05442029982805252,
-0.03880912438035011,
0.05237282067537308,
0.030296528711915016,
0.07095713913440704,
-0.046826209872961044,
-0.0319814495742321,
-0.020079046487808228,
0... | 0.084202 |
should select an appropriate Windows service account for each HostProcess container, aiming to limit the degree of privileges so as to avoid accidental (or even malicious) damage to the host. The LocalSystem service account has the highest level of privilege of the three and should be used only if absolutely necessary.... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md | main | kubernetes | [
0.020526139065623283,
0.02051345445215702,
-0.033724140375852585,
-0.032643191516399384,
-0.0243076104670763,
0.0025416819844394922,
0.05035344511270523,
0.0049445233307778835,
0.0006161434575915337,
0.07630935311317444,
-0.07722381502389908,
-0.054804764688014984,
0.03488703817129135,
0.0... | 0.026579 |
Many applications rely on configuration which is used during either application initialization or runtime. Most times, there is a requirement to adjust values assigned to configuration parameters. ConfigMaps are a Kubernetes mechanism that let you inject configuration data into application {{< glossary\_tooltip text="p... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md | main | kubernetes | [
-0.012571363709867,
0.014030574820935726,
0.03283979743719101,
-0.017895247787237167,
-0.03743277117609978,
-0.05336456745862961,
0.044663023203611374,
0.027024317532777786,
0.009566377848386765,
0.02918383665382862,
-0.005043965298682451,
-0.031385116279125214,
0.024523884057998657,
-0.05... | 0.133431 |
how.nice.to.look=fairlyNice ``` The `game.properties` and `ui.properties` files in the `configure-pod-container/configmap/` directory are represented in the `data` section of the ConfigMap. ```shell kubectl get configmaps game-config -o yaml ``` The output is similar to this: ```yaml apiVersion: v1 kind: ConfigMap meta... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md | main | kubernetes | [
0.016000796109437943,
0.012462451122701168,
0.0029151784256100655,
-0.006929436698555946,
0.01467079110443592,
-0.03216342255473137,
0.004268633667379618,
-0.0017319292528554797,
0.0428430438041687,
0.06884600967168808,
0.026389867067337036,
-0.10936106741428375,
0.03356708958745003,
-0.05... | 0.1559 |
where the output is similar to this: ```yaml apiVersion: v1 kind: ConfigMap metadata: creationTimestamp: 2022-02-18T18:54:22Z name: game-config-3 namespace: default resourceVersion: "530" uid: 05f8da22-d671-11e5-8cd0-68f728db1985 data: game-special-key: | enemies=aliens lives=3 enemies.cheat=true enemies.cheat.level=no... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md | main | kubernetes | [
0.033513665199279785,
0.029081610962748528,
-0.054162316024303436,
-0.029042867943644524,
-0.02090221829712391,
-0.017894765362143517,
-0.018921492621302605,
-0.006341860163956881,
0.05037030950188637,
0.048140112310647964,
0.04379797354340553,
-0.12951870262622833,
0.042049258947372437,
-... | 0.106644 |
single ConfigMap 1. Define an environment variable as a key-value pair in a ConfigMap: ```shell kubectl create configmap special-config --from-literal=special.how=very ``` 2. Assign the `special.how` value defined in the ConfigMap to the `SPECIAL\_LEVEL\_KEY` environment variable in the Pod specification. {{% code\_sam... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md | main | kubernetes | [
0.0749678835272789,
0.016977310180664062,
0.04355578497052193,
0.023343274369835854,
-0.02789049595594406,
-0.050237007439136505,
0.023546127602458,
0.04257417470216751,
0.004322337917983532,
0.016115298494696617,
-0.015735339373350143,
-0.12699712812900543,
0.0398101881146431,
-0.05139847... | 0.07043 |
```shell kubectl delete pod dapi-test-pod --now ``` ### Add ConfigMap data to a specific path in the Volume Use the `path` field to specify the desired file path for specific ConfigMap items. In this case, the `SPECIAL\_LEVEL` item will be mounted in the `config-volume` volume at `/etc/config/keys`. {{% code\_sample fi... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md | main | kubernetes | [
0.04919851943850517,
0.014500265009701252,
0.027910644188523293,
-0.011029208078980446,
0.012091416865587234,
-0.06043987721204758,
0.030700558796525,
0.04006559029221535,
0.05362015962600708,
0.0189411249011755,
0.018763234838843346,
-0.02323147840797901,
0.04541298747062683,
-0.036441762... | 0.094072 |
these into the `binaryData` field of the ConfigMap, and not in `data`. Both text and binary data sources can be combined in one ConfigMap. If you want to view the `binaryData` keys (and their values) in a ConfigMap, you can run `kubectl get configmap -o jsonpath='{.binaryData}' `. Pods can load data from a ConfigMap th... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md | main | kubernetes | [
0.06163591146469116,
0.01591307669878006,
0.027368053793907166,
0.03302648663520813,
0.019210094586014748,
-0.05692703649401665,
0.014590401202440262,
0.0051959422416985035,
0.046431295573711395,
0.001967034302651882,
0.007081575691699982,
-0.142718106508255,
0.0026089439634233713,
-0.0483... | 0.122846 |
and Pods that you made: ```bash kubectl delete configmaps/game-config configmaps/game-config-2 configmaps/game-config-3 \ configmaps/game-config-env-file kubectl delete pod dapi-test-pod --now # You might already have removed the next set kubectl delete configmaps/special-config configmaps/env-config kubectl delete con... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md | main | kubernetes | [
0.047178056091070175,
0.010523985140025616,
0.028271857649087906,
-0.05174343287944794,
0.044049616903066635,
-0.038625117391347885,
0.031584981828927994,
-0.04125277325510979,
0.03638952970504761,
0.0458764024078846,
0.025128383189439774,
-0.043470703065395355,
-0.01570710353553295,
-0.03... | 0.110492 |
{{< feature-state feature\_gate\_name="InPlacePodVerticalScaling" >}} This page explains how to change the CPU and memory resource requests and limits assigned to a container \*without recreating the Pod\*. Traditionally, changing a Pod's resource requirements necessitated deleting the existing Pod and creating a repla... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/resize-container-resources.md | main | kubernetes | [
0.05271945893764496,
0.04469730332493782,
0.0038581977132707834,
0.09016227722167969,
0.009272221475839615,
-0.05649428442120552,
0.014137059450149536,
0.02460869774222374,
-0.02738170325756073,
0.056948330253362656,
-0.01565530337393284,
0.041523877531290054,
-0.054403822869062424,
-0.049... | 0.197418 |
block the remaining pending resizes from being attempted; all remaining pending resizes will still be retried even if a higher-priority resize gets deferred again. ### Leveraging `observedGeneration` Fields {{< feature-state feature\_gate\_name="PodObservedGenerationTracking" >}} \* The top-level `status.observedGenera... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/resize-container-resources.md | main | kubernetes | [
0.029490305110812187,
0.022318674251437187,
0.07040777802467346,
0.04441007971763611,
-0.0178601685911417,
-0.021620796993374825,
-0.02591528557240963,
0.01296307798475027,
-0.0013983602402731776,
0.07143022865056992,
-0.03326104208827019,
0.001963807037100196,
-0.05588730797171593,
-0.040... | 0.128401 |
can only be changed to different values. \* \*\*Operating System:\*\* Windows pods do not support in-place resize. \* \*\*Node Policies:\*\* Pods managed by [static CPU or Memory manager policies](/docs/tasks/administer-cluster/cpu-management-policies/) cannot be resized in-place. \* \*\*Swap:\*\* Pods utilizing [swap ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/resize-container-resources.md | main | kubernetes | [
0.053199898451566696,
0.012452325783669949,
-0.03008793294429779,
0.049789492040872574,
-0.08341318368911743,
0.02780764363706112,
0.001111082499846816,
0.028674636036157608,
0.02093276008963585,
0.08022600412368774,
-0.03560318425297737,
0.013101508840918541,
-0.010725616477429867,
-0.001... | 0.177585 |
to this failed attempt. To fix this, you would need to patch the pod again with feasible resource values. ## Clean up Delete your namespace. This deletes all the Pods that you created for this task: ```shell kubectl delete namespace qos-example ``` ## {{% heading "whatsnext" %}} ### For application developers \* [Assig... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/resize-container-resources.md | main | kubernetes | [
0.05605343356728554,
0.010887221433222294,
-0.004997422453016043,
0.03493960574269295,
-0.07357574254274368,
-0.027145490050315857,
0.005465805996209383,
-0.027249669656157494,
-0.0024868259206414223,
0.08335503935813904,
-0.034652337431907654,
-0.08747107535600662,
-0.003364342264831066,
... | 0.166607 |
This page shows how to assign a Kubernetes Pod to a particular node using Node Affinity in a Kubernetes cluster. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## Add a label to a node 1. List the nodes in your cluster, along with their labels: ```shell kubectl get n... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity.md | main | kubernetes | [
0.056491918861866,
0.035151079297065735,
-0.025756720453500748,
0.022684603929519653,
0.003722299123182893,
0.04564089700579643,
0.03855863958597183,
-0.04443516954779625,
-0.009918068535625935,
0.0019524676026776433,
0.005860417149960995,
-0.10490531474351883,
0.03319317102432251,
-0.0383... | 0.137599 |
This page shows how to assign a CPU \*request\* and a CPU \*limit\* to a container. Containers cannot use more CPU than the configured limit. Provided the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-cpu-resource.md | main | kubernetes | [
0.061705850064754486,
0.012451731599867344,
-0.005350555293262005,
0.007123603951185942,
-0.039862945675849915,
-0.045471105724573135,
-0.010939295403659344,
-0.04414081946015358,
0.03542545065283775,
0.05559781193733215,
-0.06538055092096329,
-0.1270311325788498,
-0.025276580825448036,
-0... | 0.038364 |
\*CPU\* units. One CPU, in Kubernetes, is equivalent to: \* 1 AWS vCPU \* 1 GCP Core \* 1 Azure vCore \* 1 Hyperthread on a bare-metal Intel processor with Hyperthreading Fractional values are allowed. A Container that requests 0.5 CPU is guaranteed half as much CPU as a Container that requests 1 CPU. You can use the s... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-cpu-resource.md | main | kubernetes | [
0.05979159474372864,
0.006318128202110529,
0.012697970494627953,
0.04752397537231445,
-0.028439579531550407,
-0.0804867297410965,
-0.0024236440658569336,
-0.050493206828832626,
0.07719680666923523,
0.055754076689481735,
-0.00292134378105402,
-0.08990692347288132,
-0.010376425459980965,
-0.... | 0.169694 |
matches the limit. Similarly, if a Container specifies its own memory limit, but does not specify a memory request, Kubernetes automatically assigns a memory request that matches the limit. ## Motivation for CPU requests and limits By configuring the CPU requests and limits of the Containers that run in your cluster, y... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-cpu-resource.md | main | kubernetes | [
0.08926832675933838,
0.04162456840276718,
0.009233491495251656,
0.043217144906520844,
-0.012360919266939163,
0.004245704039931297,
0.0014712790725752711,
-0.008494525216519833,
0.07421743124723434,
0.04467525705695152,
-0.05673146992921829,
-0.01368718408048153,
-0.025790736079216003,
-0.0... | 0.178741 |
This page shows how to configure liveness, readiness and startup probes for containers. For more information about probes, see [Liveness, Readiness and Startup Probes](/docs/concepts/configuration/liveness-readiness-startup-probes) The [kubelet](/docs/reference/command-line-tools-reference/kubelet/) uses liveness probe... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md | main | kubernetes | [
-0.010492962785065174,
-0.012058786116540432,
0.006870587356388569,
0.009757078252732754,
0.018115714192390442,
-0.0649498850107193,
-0.03338158503174782,
-0.026041749864816666,
0.04358893632888794,
0.05066283419728279,
-0.02709338627755642,
-0.013162389397621155,
-0.028498241677880287,
-0... | 0.209946 |
sleep 30; rm -f /tmp/healthy; sleep 600" ``` For the first 30 seconds of the container's life, there is a `/tmp/healthy` file. So during the first 30 seconds, the command `cat /tmp/healthy` returns a success code. After 30 seconds, `cat /tmp/healthy` returns a failure code. Create the Pod: ```shell kubectl apply -f htt... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md | main | kubernetes | [
0.04736426845192909,
0.008737499825656414,
-0.003918001893907785,
0.033070310950279236,
0.03949034586548805,
-0.05781498923897743,
-0.057366497814655304,
0.0027048883493989706,
0.0706900805234909,
0.06748884916305542,
0.015229575335979462,
-0.07744073122739792,
-0.03506510332226753,
-0.007... | 0.173006 |
w.Write([]byte("ok")) } }) ``` The kubelet starts performing health checks 3 seconds after the container starts. So the first couple of health checks will succeed. But after 10 seconds, the health checks will fail, and the kubelet will kill and restart the container. To try the HTTP liveness check, create a Pod: ```she... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md | main | kubernetes | [
-0.003085022559389472,
0.0576612763106823,
0.004189008381217718,
0.01600504107773304,
-0.027322756126523018,
-0.06515342742204666,
-0.03878919035196304,
-0.04485364630818367,
0.06438711285591125,
0.046661313623189926,
-0.004522398114204407,
-0.02873859368264675,
-0.03877425193786621,
-0.01... | 0.119044 |
HTTP and TCP probes. To try the gRPC liveness check, create a Pod using the command below. In the example below, the etcd pod is configured to use gRPC liveness probe. ```shell kubectl apply -f https://k8s.io/examples/pods/probe/grpc-liveness.yaml ``` After 15 seconds, view Pod events to verify that the liveness check ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md | main | kubernetes | [
0.0339234322309494,
0.006857911124825478,
0.04498111084103584,
-0.01019654143601656,
0.013042989186942577,
-0.06895745545625687,
-0.02910454384982586,
-0.07700415700674057,
0.07551855593919754,
0.05988666042685509,
0.004149440210312605,
-0.05941327288746834,
-0.05087573826313019,
0.0259591... | 0.085552 |
liveness probes can be used in parallel for the same container. Using both can ensure that traffic does not reach a container that is not ready for it, and that containers are restarted when they fail. ## Configure Probes [Probes](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#probe-v1-core) have a n... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md | main | kubernetes | [
-0.013156910426914692,
-0.0013846078654751182,
0.015746986493468285,
0.036995384842157364,
0.03749040514230728,
-0.029972214251756668,
-0.05141410231590271,
-0.07112125307321548,
0.08281346410512924,
0.041417237371206284,
-0.012201281264424324,
-0.03131909295916557,
-0.016489669680595398,
... | 0.110144 |
to the specified port and path to perform the check. The kubelet sends the probe to the Pod's IP address, unless the address is overridden by the optional `host` field in `httpGet`. If `scheme` field is set to `HTTPS`, the kubelet sends an HTTPS request skipping the certificate verification. In most scenarios, you do n... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md | main | kubernetes | [
0.07610346376895905,
0.07158717513084412,
0.02529260516166687,
-0.007636332418769598,
-0.02999459207057953,
-0.06872271746397018,
-0.01505250670015812,
-0.08423244953155518,
0.08280408382415771,
0.006370294373482466,
-0.05477355793118477,
-0.10242388397455215,
-0.00710268085822463,
-0.0002... | 0.077194 |
probe connection at the node, not in the Pod, which means that you can not use a service name in the `host` parameter since the kubelet is unable to resolve it. ### Probe-level `terminationGracePeriodSeconds` {{< feature-state for\_k8s\_version="v1.28" state="stable" >}} In 1.25 and above, users can specify a probe-lev... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md | main | kubernetes | [
0.013805187307298183,
0.04576583579182625,
0.09868422895669937,
-0.004376131575554609,
-0.07348411530256271,
-0.02832402102649212,
-0.012084449641406536,
-0.04474085941910744,
0.08179906010627747,
0.03662951663136482,
-0.047463905066251755,
-0.06982141733169556,
-0.012985543347895145,
0.01... | 0.147133 |
What's Kompose? It's a conversion tool for all things compose (namely Docker Compose) to container orchestrators (Kubernetes or OpenShift). More information can be found on the Kompose website at [https://kompose.io/](https://kompose.io/). ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/translate-compose-kubernetes.md | main | kubernetes | [
-0.001975761028006673,
-0.016472401097416878,
0.02599806897342205,
-0.010625426657497883,
0.04556363448500633,
0.006571991369128227,
-0.050293825566768646,
-0.02954365313053131,
0.006385307293385267,
0.044182855635881424,
-0.05527951940894127,
-0.02509915456175804,
-0.019280683249235153,
-... | 0.11509 |
Kompose supports conversion of V1, V2, and V3 Docker Compose files into Kubernetes and OpenShift objects. ### Kubernetes `kompose convert` example ```shell kompose --file docker-voting.yml convert ``` ```none WARN Unsupported key networks - ignoring WARN Unsupported key build - ignoring INFO Kubernetes file "worker-svc... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/translate-compose-kubernetes.md | main | kubernetes | [
0.0462014339864254,
-0.015614880248904228,
-0.05918947234749794,
-0.009419696405529976,
0.032311975955963135,
-0.0033186026848852634,
-0.03268924355506897,
-0.022642776370048523,
0.04714534804224968,
0.04848678782582283,
-0.042408011853694916,
-0.06800916790962219,
-0.034054946154356,
-0.0... | 0.081256 |
Replication Controller objects. If you want to specify replicas (default is 1), use `--replicas` flag: `kompose convert --replication-controller --replicas 3`. ```shell kompose convert --daemon-set INFO Kubernetes file "redis-svc.yaml" created INFO Kubernetes file "web-svc.yaml" created INFO Kubernetes file "redis-daem... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/translate-compose-kubernetes.md | main | kubernetes | [
-0.001965773291885853,
-0.05431074649095535,
-0.07287628203630447,
-0.023290401324629784,
-0.010047100484371185,
0.004282018169760704,
-0.007693372201174498,
-0.008242976851761341,
0.0937725380063057,
0.059950198978185654,
0.008328277617692947,
-0.06758026033639908,
0.012803406454622746,
-... | 0.080343 |
doesn't allow `\_` in object name. Please note that changing service name might break some `docker-compose` files. ## Docker Compose Versions Kompose supports Docker Compose versions: 1, 2 and 3. We have limited support on versions 2.1 and 3.2 due to their experimental nature. A full list on compatibility between all t... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/translate-compose-kubernetes.md | main | kubernetes | [
-0.016458723694086075,
0.01221406552940607,
0.0750119611620903,
-0.028258733451366425,
-0.05583081766963005,
0.0008128057233989239,
0.01678517833352089,
-0.07331439852714539,
0.0867181122303009,
0.032056767493486404,
-0.09928211569786072,
-0.0959630012512207,
-0.0007177393999882042,
0.0251... | 0.02591 |
Namespaces can be labeled to enforce the [Pod Security Standards](/docs/concepts/security/pod-security-standards). The three policies [privileged](/docs/concepts/security/pod-security-standards/#privileged), [baseline](/docs/concepts/security/pod-security-standards/#baseline) and [restricted](/docs/concepts/security/po... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/enforce-standards-namespace-labels.md | main | kubernetes | [
-0.004953627474606037,
-0.015507819131016731,
0.02312861569225788,
-0.03133430331945419,
0.03880753740668297,
0.0057591223157942295,
0.06516904383897781,
-0.038381606340408325,
0.04957190901041031,
0.03483482822775841,
0.022643832489848137,
-0.01819141022861004,
0.024350076913833618,
0.024... | 0.164302 |
This page shows how to use an Init Container to initialize a Pod before an application Container runs. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## Create a Pod that has an Init Container In this exercise you create a Pod that has one application Container and o... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-pod-initialization.md | main | kubernetes | [
-0.02558209002017975,
0.031516656279563904,
0.008052719756960869,
0.012500561773777008,
0.01609514281153679,
-0.06476446986198425,
-0.0017190264770761132,
0.00042704344377852976,
0.0020399638451635838,
0.04089644178748131,
-0.020729387179017067,
0.03763572499155998,
-0.02886260487139225,
0... | 0.109696 |
{{< feature-state state="stable" >}} This page shows how to assign extended resources to a Container. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} Before you do this exercise, do the exercise in [Advertise Extended Resources for a Node](/docs/tasks/administer-clust... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/extended-resource.md | main | kubernetes | [
0.01359444111585617,
0.028155768290162086,
0.06123735383152962,
0.0611487478017807,
0.05352679267525673,
-0.017370078712701797,
-0.006002503447234631,
-0.010081132873892784,
-0.07195920497179031,
0.02690443955361843,
-0.03502850979566574,
-0.019731959328055382,
0.021798523142933846,
0.0172... | 0.118263 |
\*Static Pods\* are managed directly by the kubelet daemon on a specific node, without the {{< glossary\_tooltip text="API server" term\_id="kube-apiserver" >}} observing them. Unlike Pods that are managed by the control plane (for example, a {{< glossary\_tooltip text="Deployment" term\_id="deployment" >}}); instead, ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/static-pod.md | main | kubernetes | [
-0.034174129366874695,
-0.009465890005230904,
0.10686855018138885,
0.01886138878762722,
-0.05870999023318291,
-0.03536077216267586,
0.02869560569524765,
-0.06880362331867218,
0.10641787201166153,
0.021088624373078346,
0.0015209696721285582,
-0.09450656175613403,
0.014825128018856049,
-0.05... | 0.126864 |
a `staticPodPath` value in the [kubelet configuration file](/docs/reference/config-api/kubelet-config.v1beta1/). See [Set Kubelet Parameters Via A Configuration File](/docs/tasks/administer-cluster/kubelet-config-file/) for more information. An alternative and deprecated method is to configure the kubelet on that node ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/static-pod.md | main | kubernetes | [
0.0743376761674881,
-0.03389113396406174,
0.05295842885971069,
0.00939199049025774,
-0.02469683438539505,
0.01303782593458891,
-0.056560222059488297,
0.011762565933167934,
0.05718250945210457,
-0.010521701537072659,
-0.030569814145565033,
-0.09212680160999298,
-0.03757812827825546,
0.00149... | 0.189927 |
is running crictl stop 129fd7d382018 # replace with the ID of your container sleep 20 crictl ps ``` ```console CONTAINER IMAGE CREATED STATE NAME ATTEMPT POD ID 89db4553e1eeb docker.io/library/nginx@sha256:... 19 seconds ago Running web 1 34533c6729106 ``` Once you identify the right container, you can get the logs for... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/static-pod.md | main | kubernetes | [
-0.003898550057783723,
0.0694340169429779,
0.024095652624964714,
-0.013330567628145218,
0.09653118997812271,
-0.09701202809810638,
0.012032554484903812,
-0.04257149249315262,
0.058900441974401474,
0.05353914201259613,
-0.0604611337184906,
-0.0969490259885788,
0.010232783854007721,
0.033898... | 0.034488 |
Kubernetes provides a built-in [admission controller](/docs/reference/access-authn-authz/admission-controllers/#podsecurity) to enforce the [Pod Security Standards](/docs/concepts/security/pod-security-standards). You can configure this admission controller to set cluster-wide defaults and [exemptions](/docs/concepts/s... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/enforce-standards-admission-controller.md | main | kubernetes | [
0.07713057845830917,
0.002093659248203039,
0.03999757021665573,
-0.007982837967574596,
0.03139510005712509,
0.053498461842536926,
0.03657924011349678,
-0.01589568331837654,
0.02834208495914936,
0.06899219751358032,
0.013864140957593918,
-0.008383373729884624,
0.009630410932004452,
0.035523... | 0.129642 |
A security context defines privilege and access control settings for a Pod or Container. Security context settings include, but are not limited to: \* Discretionary Access Control: Permission to access an object, like a file, is based on [user ID (UID) and group ID (GID)](https://wiki.archlinux.org/index.php/users\_and... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/security-context.md | main | kubernetes | [
-0.002344082808122039,
0.045409902930259705,
-0.11732993274927139,
-0.02909315936267376,
0.05721714720129967,
-0.05232495814561844,
0.09381529688835144,
0.08118682354688644,
0.010546275414526463,
-0.028120994567871094,
0.033491622656583786,
-0.02774740569293499,
0.02036307565867901,
0.0032... | 0.258924 |
group ID 2000, which is the value of `fsGroup`. ```none -rw-r--r-- 1 1000 2000 6 Jun 6 20:08 testfile ``` Run the following command: ```shell id ``` The output is similar to this: ```none uid=1000 gid=3000 groups=2000,3000,4000 ``` From the output, you can see that `gid` is 3000 which is same as the `runAsGroup` field.... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/security-context.md | main | kubernetes | [
-0.0037775905802845955,
-0.030979037284851074,
-0.06435105949640274,
0.019567593932151794,
0.017102548852562904,
-0.046329136937856674,
-0.003031655214726925,
-0.024408550933003426,
0.07134882360696793,
-0.007083732169121504,
0.05417197197675705,
0.0037914372514933348,
0.004010553006082773,
... | 0.135834 |
process identity: ```shell kubectl exec -it security-context-demo -- id ``` The output is similar to this: ```none uid=1000 gid=3000 groups=3000,4000 ``` See the Pod's status: ```shell kubectl get pod security-context-demo -o yaml ``` You can see that the `status.containerStatuses[].user.linux` field exposes the proces... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/security-context.md | main | kubernetes | [
-0.011463403701782227,
0.036452628672122955,
-0.06051326170563698,
-0.039274588227272034,
0.011212403886020184,
-0.06643770635128021,
0.10861965268850327,
0.02037079818546772,
0.09907769411802292,
0.037128251045942307,
0.0040909042581915855,
-0.08271482586860657,
0.0050424025394022465,
-0.... | 0.239868 |
of Kubernetes. In this case, since Kubernetes doesn't perform any ownership and permission change, `fsGroupChangePolicy` does not take effect, and as specified by CSI, the driver is expected to mount the volume with the provided `fsGroup`, resulting in a volume that is readable/writable by the `fsGroup`. ## Set the sec... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/security-context.md | main | kubernetes | [
0.052037641406059265,
0.02342909947037697,
-0.004347550682723522,
-0.004149161279201508,
0.0282874945551157,
-0.03633807972073555,
0.026804303750395775,
0.03763293847441673,
0.066098652780056,
0.02061161957681179,
0.008006996475160122,
-0.03096943162381649,
0.017201688140630722,
0.02013361... | 0.120209 |
sh ``` In your shell, view the capabilities for process 1: ```shell cd /proc/1 cat status ``` The output shows capabilities bitmap for the process: ``` ... CapPrm: 00000000aa0435fb CapEff: 00000000aa0435fb ... ``` Compare the capabilities of the two Containers: ``` 00000000a80425fb 00000000aa0435fb ``` In the capabilit... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/security-context.md | main | kubernetes | [
0.08174485713243484,
0.03990407660603523,
-0.06592991203069687,
-0.051496993750333786,
0.038982927799224854,
-0.06558395177125931,
0.009879423305392265,
0.03991306945681572,
-0.05760858580470085,
-0.014500284567475319,
0.02164709009230137,
-0.07294236868619919,
-0.003530586836859584,
0.005... | 0.086581 |
level: ```yaml ... securityContext: seLinuxOptions: level: "s0:c123,c456" ``` {{< note >}} To assign SELinux labels, the SELinux security module must be loaded on the host operating system. On Windows and Linux worker nodes without SELinux support, this field and any SELinux feature gates described below have no effect... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/security-context.md | main | kubernetes | [
0.03630417212843895,
-0.011716936714947224,
0.017288073897361755,
0.011060631833970547,
0.04337485879659653,
-0.014751151204109192,
-0.027031924575567245,
0.0293823704123497,
0.03289605677127838,
-0.053733643144369125,
-0.015695882961153984,
0.007730590645223856,
0.008658445440232754,
0.00... | 0.146201 |
a new controller called `SELinuxWarningController` has been introduced in kube-controller-manager. It is disabled by default and can be enabled by either setting the `--controllers=\*,selinux-warning-controller` [command line flag](/docs/reference/command-line-tools-reference/kube-controller-manager/), or by setting `g... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/security-context.md | main | kubernetes | [
0.01219301950186491,
-0.03937426209449768,
-0.011224196292459965,
0.009086452424526215,
0.04722129553556442,
-0.01805032603442669,
0.008941061794757843,
0.02706453949213028,
0.07357242703437805,
-0.04047388583421707,
0.049863316118717194,
-0.04940849915146828,
0.009385669603943825,
-0.0462... | 0.210629 |
```yaml ... securityContext: procMount: Unmasked ``` {{< note >}} Setting `procMount` to Unmasked requires the `spec.hostUsers` value in the pod spec to be `false`. In other words: a container that wishes to have an Unmasked `/proc` or unmasked `/sys` must also be in a [user namespace](/docs/concepts/workloads/pods/use... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/security-context.md | main | kubernetes | [
0.014590120874345303,
0.020522484555840492,
0.0059829941019415855,
-0.007229677867144346,
0.047310877591371536,
-0.014800054021179676,
0.060596223920583725,
0.01268753781914711,
0.05876404419541359,
0.05254971235990524,
0.04261646419763565,
-0.03376559540629387,
0.014117161743342876,
0.024... | 0.15191 |
This page shows how to assign a Kubernetes Pod to a particular node in a Kubernetes cluster. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## Add a label to a node 1. List the {{< glossary\_tooltip term\_id="node" text="nodes" >}} in your cluster, along with their l... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-pods-nodes.md | main | kubernetes | [
0.014747001230716705,
0.022764001041650772,
0.03204489126801491,
-0.003439858788624406,
-0.020049329847097397,
0.03853003680706024,
0.07212235033512115,
-0.07537488639354706,
0.02029726468026638,
0.027053017169237137,
-0.004854785744100809,
-0.13578520715236664,
0.018383057788014412,
-0.04... | 0.09019 |
{{< feature-state feature\_gate\_name="InPlacePodLevelResourcesVerticalScaling" >}} This page explains how to change the CPU and memory resources set at the Pod level without recreating the Pod. The In-place Pod Resize feature allows modifying resource allocations for a running Pod, avoiding application disruption. The... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/resize-pod-resources.md | main | kubernetes | [
0.060592591762542725,
0.06032915413379669,
-0.002244088565930724,
0.09842928498983383,
0.017291678115725517,
-0.05267347767949104,
-0.0017111914930865169,
0.04307490214705467,
-0.060604553669691086,
0.030374830588698387,
-0.04357121139764786,
0.04247036203742027,
-0.05058160051703453,
-0.0... | 0.170631 |
the Pod-level limit, enabling resource sharing across containers within the Pod. ## Example: Resizing Pod-Level Resources First, create a Pod designed for in-place CPU resize and restart-required memory resize. {{% code\_sample file="pods/resource/pod-level-resize.yaml" %}} Create the pod: ```shell kubectl create -f po... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/resize-pod-resources.md | main | kubernetes | [
0.0516415610909462,
0.019698644056916237,
-0.002592402743175626,
0.028970694169402122,
-0.03120020218193531,
-0.06403800845146179,
-0.027354706078767776,
0.03751630708575249,
0.00622031232342124,
0.06415550410747528,
-0.031094837933778763,
-0.011476538144052029,
-0.020664656534790993,
-0.0... | 0.149857 |
{{< feature-state for\_k8s\_version="v1.18" state="stable" >}} This page shows how to use the `runAsUserName` setting for Pods and containers that will run on Windows nodes. This is roughly equivalent of the Linux-specific `runAsUser` setting, allowing you to run applications in a container as a different username than... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-runasusername.md | main | kubernetes | [
0.03469531983137131,
0.02338551916182041,
0.026843544095754623,
0.026336174458265305,
-0.07620460540056229,
0.0380978025496006,
-0.003990557044744492,
0.016145111992955208,
0.008039439097046852,
0.04307965561747551,
-0.1002780944108963,
-0.12925072014331818,
0.007884131744503975,
0.0304007... | 0.145083 |
dots or spaces, and it cannot contain the following characters: `" / \ [ ] : ; | = , + \* ? < > @`. Examples of acceptable values for the `runAsUserName` field: `ContainerAdministrator`, `ContainerUser`, `NT AUTHORITY\NETWORK SERVICE`, `NT AUTHORITY\LOCAL SERVICE`. For more information about these limtations, check [he... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/configure-runasusername.md | main | kubernetes | [
-0.000483610579976812,
0.0012656508479267359,
-0.0032424370292574167,
0.008239738643169403,
-0.04332926869392395,
0.01851116679608822,
0.13768130540847778,
-0.028808843344449997,
0.022735679522156715,
0.03246872499585152,
0.013265113346278667,
-0.10111864656209946,
0.043772391974925995,
-0... | 0.108631 |
This page shows how to configure process namespace sharing for a pod. When process namespace sharing is enabled, processes in a container are visible to all other containers in the same pod. You can use this feature to configure cooperating containers, such as a log handler sidecar container, or to troubleshoot contain... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/share-process-namespace.md | main | kubernetes | [
0.009778800420463085,
-0.05755845829844475,
-0.0020120670087635517,
0.02969224937260151,
-0.014279750175774097,
-0.022353975102305412,
-0.02651161327958107,
-0.025929763913154602,
-0.003858113894239068,
0.05420105531811714,
-0.05762634798884392,
-0.0278047863394022,
-0.021102184429764748,
... | 0.142009 |
{{< feature-state feature\_gate\_name="PodLevelResources" >}} This page shows how to specify CPU and memory resources for a Pod at pod-level in addition to container-level resource specifications. A Kubernetes node allocates resources to a pod based on the pod's resource requests. These requests can be defined at the p... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-pod-level-resources.md | main | kubernetes | [
0.029646901413798332,
0.03228505700826645,
0.0068100024946033955,
0.05091310665011406,
0.006209834478795528,
-0.04153205454349518,
0.0076739792712032795,
0.0027757028583437204,
0.03309616819024086,
0.03397802636027336,
-0.04039217531681061,
-0.03088372014462948,
-0.04408060014247894,
0.009... | 0.180145 |
about 162,900,000 bytes of memory, which is about 150 MiB. This is greater than the Pod's 100 MiB request, but within the Pod's 200 MiB limit. ``` NAME CPU(cores) MEMORY(bytes) memory-demo 162856960 ``` ## Create a pod with CPU requests and limits at pod-level To specify a CPU request for a Pod, include the `resources.... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-pod-level-resources.md | main | kubernetes | [
0.08013270795345306,
0.015430024825036526,
0.009901214390993118,
0.05305836722254753,
-0.055014099925756454,
-0.07236282527446747,
-0.02540024369955063,
0.025288444012403488,
0.02785217948257923,
0.049137942492961884,
-0.038240984082221985,
-0.02563261054456234,
-0.024056121706962585,
-0.0... | 0.170632 |
resources: limits: cpu: 500m memory: 100Mi requests: cpu: 500m memory: 50Mi ... - name: pod-resources-demo-ctr-2 resources: {} ... resources: limits: cpu: "1" memory: 200Mi requests: cpu: "1" memory: 100Mi ... ``` Since pod-level requests and limits are specified, the request guarantees for both containers in the pod w... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-pod-level-resources.md | main | kubernetes | [
0.08143585175275803,
0.02843165211379528,
-0.0050352877005934715,
0.009105293080210686,
-0.038090307265520096,
-0.07831504940986633,
-0.0314437672495842,
0.0014645898481830955,
0.055059969425201416,
0.04162442311644554,
-0.043453071266412735,
-0.05458083376288414,
-0.011066371574997902,
-0... | 0.153995 |
{{< feature-state feature\_gate\_name="DynamicResourceAllocation" >}} This page shows you how to configure \_dynamic resource allocation (DRA)\_ in a Kubernetes cluster by enabling API groups and configuring classes of devices. These instructions are for cluster administrators. ## About DRA {#about-dra} {{< glossary\_d... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-resources/set-up-dra-cluster.md | main | kubernetes | [
-0.06388653069734573,
0.019401829689741135,
0.05752440169453621,
0.018308693543076515,
-0.09521273523569107,
-0.010610740631818771,
0.06109265610575676,
-0.04136587306857109,
0.048828672617673874,
0.014929140917956829,
-0.049257032573223114,
-0.10468550771474838,
-0.03739374503493309,
-0.0... | 0.06745 |
DeviceClasses during driver installation. The ResourceSlices that your driver publishes contain information about the devices that the driver manages, such as capacity, metadata, and attributes. You can use {{< glossary\_tooltip term\_id="cel" >}} to filter for properties in your DeviceClasses, which can make finding d... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-resources/set-up-dra-cluster.md | main | kubernetes | [
0.027419578284025192,
0.035426732152700424,
0.023255225270986557,
0.02860262803733349,
0.013411848805844784,
-0.04742431640625,
0.03232375532388687,
-0.020863186568021774,
0.04727626591920853,
-0.04776982218027115,
-0.015251271426677704,
-0.11729562282562256,
-0.01451694592833519,
-0.02158... | 0.127017 |
{{< feature-state feature\_gate\_name="DynamicResourceAllocation" >}} This page shows you how to allocate devices to your Pods by using \_dynamic resource allocation (DRA)\_. These instructions are for workload operators. Before reading this page, familiarize yourself with how DRA works and with DRA terminology like {{... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-resources/allocate-devices-dra.md | main | kubernetes | [
-0.02262764237821102,
0.022683318704366684,
0.08692771941423416,
0.01390944141894579,
-0.044874802231788635,
-0.03597693517804146,
0.07480800896883011,
-0.02067461796104908,
0.06787221878767014,
0.03464052081108093,
-0.019209638237953186,
-0.052580785006284714,
-0.010172720067203045,
-0.00... | 0.135411 |
`64Gi` of capacity. To create the ResourceClaim, run the following command: ```shell kubectl apply -f https://k8s.io/examples/dra/resourceclaim.yaml ``` {{% /tab %}} {{< /tabs >}} ## Request devices in workloads using DRA {#request-devices-workloads} To request device allocation, specify a ResourceClaim or a ResourceCl... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/configure-pod-container/assign-resources/allocate-devices-dra.md | main | kubernetes | [
-0.039584431797266006,
0.04470536857843399,
-0.004720737691968679,
0.00195035757496953,
-0.018948111683130264,
-0.048989005386829376,
0.008754847571253777,
-0.010892830789089203,
0.05429718270897865,
0.02629469335079193,
-0.0616406686604023,
-0.09453501552343369,
0.0098918741568923,
0.0334... | 0.146363 |
{{< feature-state feature\_gate\_name="HugePages" >}} Kubernetes supports the allocation and consumption of pre-allocated huge pages by applications in a Pod. This page describes how users can consume huge pages. ## {{% heading "prerequisites" %}} Kubernetes nodes must [pre-allocate huge pages](https://www.kernel.org/d... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/manage-hugepages/scheduling-hugepages.md | main | kubernetes | [
0.026992961764335632,
0.041662175208330154,
0.02692723274230957,
0.048236943781375885,
0.01710578426718712,
-0.017869118601083755,
-0.04160958528518677,
-0.015302550047636032,
0.012243034318089485,
0.09880835562944412,
-0.031203769147396088,
0.037225328385829926,
-0.0028219991363584995,
-0... | 0.179587 |
This page shows how to change the access mode on an existing PersistentVolume to use `ReadWriteOncePod`. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} {{< note >}} The `ReadWriteOncePod` access mode graduated to stable in the Kubernetes v1.29 release. If you are run... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/change-pv-access-mode-readwriteoncepod.md | main | kubernetes | [
0.005634520202875137,
-0.019108599051833153,
0.07742004841566086,
0.0020438169594854116,
-0.07468494772911072,
0.027951689437031746,
-0.007431414443999529,
-0.055605269968509674,
0.03673810884356499,
0.07078031450510025,
-0.02825956605374813,
0.024517176672816277,
0.0024063389282673597,
-0... | 0.013943 |
be combined with other access modes. Make sure `ReadWriteOncePod` is the only access mode on the PersistentVolume when updating, otherwise the request will fail. {{< /note >}} Next you need to modify your PersistentVolumeClaim to set `ReadWriteOncePod` as the only access mode. You should also set the PersistentVolumeCl... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/change-pv-access-mode-readwriteoncepod.md | main | kubernetes | [
0.03173369541764259,
-0.047158244997262955,
0.03519802540540695,
0.014933946542441845,
-0.08152038604021072,
-0.013926881365478039,
-0.06925241649150848,
0.011271732859313488,
0.03303635120391846,
0.0667533427476883,
0.019230708479881287,
-0.013682199642062187,
0.012286565266549587,
0.0271... | 0.006467 |
This page shows how to safely drain a {{< glossary\_tooltip text="node" term\_id="node" >}}, optionally respecting the PodDisruptionBudget you have defined. ## {{% heading "prerequisites" %}} This task assumes that you have met the following prerequisites: 1. You do not require your applications to be highly available ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/safely-drain-node.md | main | kubernetes | [
-0.03700926899909973,
0.03888896480202675,
0.0952935665845871,
0.0007174903876148164,
0.010125056840479374,
-0.023993490263819695,
0.00989153329282999,
-0.023767225444316864,
0.006767600309103727,
0.006265719421207905,
-0.025144381448626518,
-0.013748843222856522,
-0.030668608844280243,
-0... | 0.090159 |
Kubernetes that it can resume scheduling new pods onto the node. ## Draining multiple nodes in parallel The `kubectl drain` command should only be issued to a single node at a time. However, you can run multiple `kubectl drain` commands for different nodes in parallel, in different terminals or in the background. Multi... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/safely-drain-node.md | main | kubernetes | [
0.013875209726393223,
-0.022848475724458694,
0.02590649388730526,
-0.0035421019420027733,
-0.05589510127902031,
-0.03036987967789173,
-0.05827062204480171,
-0.06382174789905548,
0.07632430642843246,
0.05002046376466751,
-0.08387219905853271,
0.007141884882003069,
0.013394410721957684,
-0.0... | 0.095727 |
This page guides you through configuring {{< glossary\_tooltip text="Node" term\_id="node" >}} overprovisioning in your Kubernetes cluster. Node overprovisioning is a strategy that proactively reserves a portion of your cluster's compute resources. This reservation helps reduce the time required to schedule new pods du... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/node-overprovisioning.md | main | kubernetes | [
-0.0073205893859267235,
-0.02102709375321865,
0.07515932619571686,
0.05021394416689873,
-0.03895801678299904,
0.001900448463857174,
0.012485501356422901,
-0.035820528864860535,
-0.0007097938214428723,
0.07406215369701385,
-0.04713578149676323,
-0.0774417370557785,
-0.030532103031873703,
-0... | 0.094656 |
```shell kubectl get deployment capacity-reservation ``` The output should reflect the updated number of replicas: ```none NAME READY UP-TO-DATE AVAILABLE AGE capacity-reservation 5/5 5 5 2m ``` {{< note >}} Some autoscalers, notably [Karpenter](/docs/concepts/cluster-administration/cluster-autoscaling/#autoscaler-karp... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/node-overprovisioning.md | main | kubernetes | [
0.07260944694280624,
0.022571420297026634,
0.027711957693099976,
0.06488518416881561,
-0.05208872631192207,
-0.022984372451901436,
-0.03043198399245739,
0.016237551346421242,
-0.01581748202443123,
0.07069946825504303,
-0.024546083062887192,
-0.08631397783756256,
-0.022142892703413963,
-0.0... | 0.134258 |
## {{% heading "prerequisites" %}} Some steps in this page use the `jq` tool. If you don't have `jq`, you can install it via your operating system's software sources, or fetch it from [https://jqlang.github.io/jq/](https://jqlang.github.io/jq/). Some steps also involve installing `curl`, which can be installed via your... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubelet-config-file.md | main | kubernetes | [
-0.0004995845374651253,
0.05457393452525139,
0.02475721947848797,
-0.013412754982709885,
-0.09681305289268494,
0.033136628568172455,
-0.032764460891485214,
0.018085584044456482,
0.014819969423115253,
-0.06526404619216919,
-0.020247962325811386,
-0.10131677985191345,
0.045660048723220825,
-... | 0.094413 |
{#kubelet-conf-d} You can specify a drop-in configuration directory for the kubelet. By default, the kubelet does not look for drop-in configuration files anywhere - you must specify a path. For example: `--config-dir=/etc/kubernetes/kubelet.conf.d` For Kubernetes v1.28 to v1.29, you can only specify `--config-dir` if ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubelet-config-file.md | main | kubernetes | [
0.0435338020324707,
0.007211821153759956,
0.04065227136015892,
-0.03274783119559288,
-0.021359959617257118,
-0.009372851811349392,
0.0373234860599041,
0.0006044355686753988,
0.06488166004419327,
-0.04096955806016922,
0.01797237992286682,
-0.0807095468044281,
-0.012241131626069546,
-0.02534... | 0.075123 |
"imagefs.available": "15%", "memory.available": "100Mi", "nodefs.available": "10%", "nodefs.inodesFree": "5%", "imagefs.inodesFree": "5%" }, "evictionPressureTransitionPeriod": "1m0s", "mergeDefaultEvictionSettings": false, "enableControllerAttachDetach": true, "makeIPTablesUtilChains": true, "iptablesMasqueradeBit": 1... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubelet-config-file.md | main | kubernetes | [
0.07927321642637253,
-0.013011887669563293,
-0.03385213389992714,
-0.0008962014107964933,
0.09043107181787491,
-0.028419997543096542,
-0.012094243429601192,
0.05366130545735359,
0.004017859697341919,
0.07991576194763184,
0.09077825397253036,
-0.030392447486519814,
0.024113653227686882,
-0.... | 0.056335 |
This page shows how to enable and configure autoscaling of the DNS service in your Kubernetes cluster. ## {{% heading "prerequisites" %}} \* {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} \* This guide assumes your nodes use the AMD64 or Intel 64 CPU architecture. \* Make sure [Kubernetes DNS](/docs/c... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/dns-horizontal-autoscaling.md | main | kubernetes | [
-0.018195711076259613,
-0.03942080959677696,
0.06661593168973923,
-0.007392326835542917,
-0.132334902882576,
-0.003973320126533508,
-0.05320249870419502,
-0.04914045333862305,
0.03852468729019165,
0.04516023024916649,
-0.054062504321336746,
-0.07399250566959381,
-0.06716587394475937,
-0.04... | 0.09985 |
is: deployment.apps/kube-dns-autoscaler scaled Verify that the replica count is zero: ```shell kubectl get rs --namespace=kube-system ``` The output displays 0 in the DESIRED and CURRENT columns: NAME DESIRED CURRENT READY AGE ... kube-dns-autoscaler-6b59789fc8 0 0 0 ... ... ### Option 2: Delete the kube-dns-autoscaler... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/dns-horizontal-autoscaling.md | main | kubernetes | [
-0.029688317328691483,
-0.01801496371626854,
0.020166052505373955,
-0.028703123331069946,
-0.0867164134979248,
-0.026630133390426636,
-0.042387865483760834,
-0.04981471225619316,
0.05842976272106171,
0.05538933351635933,
0.014175176620483398,
-0.09062845259904861,
-0.024519087746739388,
-0... | 0.079195 |
This page shows how to configure a Key Management Service (KMS) provider and plugin to enable secret data encryption. In Kubernetes {{< skew currentVersion >}} there are two versions of KMS at-rest encryption. You should use KMS v2 if feasible because KMS v1 is deprecated (since Kubernetes v1.28) and disabled by defaul... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kms-provider.md | main | kubernetes | [
0.021926460787653923,
0.02503839135169983,
0.014831183478236198,
-0.010852727107703686,
-0.009937912225723267,
0.04998379200696945,
0.02064325101673603,
-0.02990398183465004,
0.08423309773206711,
0.09467566013336182,
-0.015499225817620754,
0.010499399155378342,
0.041668374091386795,
-0.037... | 0.054546 |
the clear. When cached, DEKs can be used without another call to the KMS; whereas DEKs that are not cached require a call to the KMS to unwrap. \* `timeout`: How long should `kube-apiserver` wait for kms-plugin to respond before returning an error (default is 3 seconds). ### KMS v2 {#configuring-the-kms-provider-kms-v2... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kms-provider.md | main | kubernetes | [
-0.03451186418533325,
0.05814618617296219,
0.0035027924459427595,
-0.03205819055438042,
-0.007556063588708639,
-0.07830064743757248,
-0.0036482196301221848,
-0.022263651713728905,
0.058942653238773346,
0.07809300720691681,
0.021089233458042145,
-0.014771738089621067,
-0.015006503090262413,
... | 0.119271 |
socket as they do not have concept of ACL (unlike traditional file based sockets). However, they are subject to Linux networking namespace, so will only be accessible to containers within the same pod unless host networking is used. ##### KMS v2 {#developing-a-kms-plugin-gRPC-server-notes-kms-v2} \* KMS plugin version:... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kms-provider.md | main | kubernetes | [
-0.043576862663030624,
0.013166221790015697,
-0.05716753378510475,
-0.02789844386279583,
-0.06504599750041962,
-0.007542508188635111,
0.007100374903529882,
-0.012036382220685482,
0.05340157449245453,
0.04881627485156059,
0.01976848393678665,
-0.002757358830422163,
-0.002468489808961749,
-0... | 0.161587 |
`EncryptRequest`. Furthermore, plugins must ensure that the `key\_id` is stable and does not flip-flop between values (i.e. during a remote KEK rotation). Plugins must not re-use `key\_id`s, even in situations where a previously used remote KEK has been reinstated. For example, if a plugin was using `key\_id=A`, switch... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kms-provider.md | main | kubernetes | [
-0.11847496032714844,
0.039466191083192825,
-0.03248137980699539,
0.02239769883453846,
-0.04517524316906929,
-0.06129135936498642,
-0.05770878121256828,
-0.02147376537322998,
0.07341642677783966,
0.08022104203701019,
0.01946130208671093,
0.0052884407341480255,
0.05648462846875191,
-0.01076... | 0.086802 |
v1 {#encrypting-your-data-with-the-kms-provider-kms-v1} ```yaml apiVersion: apiserver.config.k8s.io/v1 kind: EncryptionConfiguration resources: - resources: - secrets - configmaps - pandas.awesome.bears.example providers: - kms: name: myKmsPluginFoo endpoint: unix:///tmp/socketfile-foo.sock cachesize: 100 timeout: 3s -... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kms-provider.md | main | kubernetes | [
-0.029723402112722397,
0.028920084238052368,
-0.016863973811268806,
-0.022335493937134743,
0.04628898203372955,
-0.06495308876037598,
-0.01043159794062376,
-0.025793064385652542,
0.027796287089586258,
0.04281486198306084,
0.03232447803020477,
-0.02078009769320488,
0.0016908934339880943,
-0... | 0.063556 |
to subdivide the secrets by namespace or script an update. ```shell kubectl get secrets --all-namespaces -o json | kubectl replace -f - ``` ## Switching from a local encryption provider to the KMS provider To switch from a local encryption provider to the `kms` provider and re-encrypt all of the secrets: 1. Add the `km... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kms-provider.md | main | kubernetes | [
-0.04111883044242859,
0.029601486399769783,
0.03887241333723068,
-0.004639679566025734,
-0.026870273053646088,
-0.005249434616416693,
-0.04167395457625389,
-0.02355552650988102,
0.06867591291666031,
0.05722230300307274,
-0.03122583217918873,
-0.06555140763521194,
0.03157425299286842,
-0.02... | 0.038301 |
This page shows how to configure quotas for API objects, including PersistentVolumeClaims and Services. A quota restricts the number of objects, of a particular type, that can be created in a namespace. You specify quotas in a [ResourceQuota](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#resourcequo... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/quota-api-object.md | main | kubernetes | [
-0.01216197945177555,
0.003709649434313178,
-0.012143485248088837,
0.002086938126012683,
-0.07577414810657501,
0.002258522203192115,
0.006130082067102194,
-0.006057923659682274,
0.08097387850284576,
0.06534316390752792,
-0.07555694878101349,
-0.12330475449562073,
0.05067303031682968,
-0.00... | 0.099301 |
This page shows you how to specify the type of [cascading deletion](/docs/concepts/architecture/garbage-collection/#cascading-deletion) to use in your cluster during {{}}. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} You also need to [create a sample Deployment](/docs/tasks/run-applicat... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/use-cascading-deletion.md | main | kubernetes | [
0.004668952897191048,
-0.025255203247070312,
0.07595294713973999,
-0.022679753601551056,
-0.027321306988596916,
-0.044652339071035385,
-0.03138161078095436,
-0.08823145180940628,
0.03594589605927467,
0.0372893251478672,
-0.025515589863061905,
-0.04858008772134781,
0.03281791880726814,
0.02... | 0.106094 |
Kubernetes [finalizers](/docs/concepts/overview/working-with-objects/finalizers/). \* Learn about [garbage collection](/docs/concepts/architecture/garbage-collection/). | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/use-cascading-deletion.md | main | kubernetes | [
0.016998711973428726,
0.0362696498632431,
0.05248395353555679,
-0.05714127793908119,
0.00242994143627584,
-0.02763110026717186,
0.0139376325532794,
0.013128796592354774,
0.06230993568897247,
0.03755825757980347,
-0.010332238860428333,
0.003585194004699588,
-0.06838242709636688,
-0.01670099... | 0.242339 |
This document helps you get started using the Kubernetes [NetworkPolicy API](/docs/concepts/services-networking/network-policies/) to declare network policies that govern how pods communicate with each other. {{% thirdparty-content %}} ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< ve... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/declare-network-policy.md | main | kubernetes | [
0.012318824417889118,
-0.0428912527859211,
0.019378816708922386,
-0.04393291473388672,
-0.04524053633213043,
-0.006006781943142414,
-0.04367824271321297,
-0.028694545850157738,
-0.017440520226955414,
0.045881375670433044,
-0.02282826602458954,
-0.03882146254181862,
-0.036995965987443924,
-... | 0.189702 |
This page shows how to specify extended resources for a Node. Extended resources allow cluster administrators to advertise node-level resources that would otherwise be unknown to Kubernetes. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## Get the names of your Node... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/extended-resource-node.md | main | kubernetes | [
-0.026060964912176132,
0.042433127760887146,
0.06604042649269104,
0.03719605877995491,
0.0075471061281859875,
-0.00389226246625185,
-0.004902060609310865,
-0.03455876559019089,
-0.019361289218068123,
0.06733164191246033,
-0.04629860818386078,
-0.06308995932340622,
0.06432943791151047,
-0.0... | 0.108057 |
you would advertise 800Gi resources of type example.com/special-storage. ```yaml Capacity: ... example.com/special-storage: 800Gi ``` Then a Container could request any number of bytes of special storage, up to 800Gi. ## Clean up Here is a PATCH request that removes the dongle advertisement from a Node. ``` PATCH /api/... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/extended-resource-node.md | main | kubernetes | [
-0.02377893030643463,
0.0971037968993187,
0.019917720928788185,
0.024133268743753433,
-0.03388394042849541,
-0.025756772607564926,
-0.012477470561861992,
0.013019758276641369,
0.016081811860203743,
0.10036438703536987,
-0.06065256521105766,
-0.02188844420015812,
0.030183129012584686,
-0.03... | 0.070395 |
Kubernetes nodes can be scheduled to `Capacity`. Pods can consume all the available capacity on a node by default. This is an issue because nodes typically run quite a few system daemons that power the OS and Kubernetes itself. Unless resources are set aside for these system daemons, pods and system daemons compete for... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/reserve-compute-resources.md | main | kubernetes | [
0.05625496432185173,
0.01957990974187851,
0.01530461199581623,
0.043568577617406845,
-0.02374107949435711,
-0.0005097153480164707,
-0.05020895227789879,
-0.015688743442296982,
0.0637318342924118,
0.05978244170546532,
-0.0822245255112648,
-0.009731565602123737,
-0.002165831858292222,
-0.035... | 0.130208 |
cgroup is specified. With `systemd` cgroup driver, you should follow a specific pattern for the name of the cgroup you define: the name should be the value you set for `kubeReservedCgroup`, with `.slice` appended. ### System Reserved - \*\*KubeletConfiguration Setting\*\*: `systemReserved: {}`. Example value `{cpu: 100... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/reserve-compute-resources.md | main | kubernetes | [
0.0009175231098197401,
0.012694241479039192,
-0.04146772623062134,
-0.017086796462535858,
-0.07355129718780518,
0.028979146853089333,
0.035895347595214844,
0.06154990941286087,
0.04232616722583771,
0.006793726235628128,
0.004986824467778206,
-0.1147303432226181,
-0.02231922373175621,
-0.03... | 0.137096 |
`capacity` for pods. `kubelet` enforce 'Allocatable' across pods by default. Enforcement is performed by evicting pods whenever the overall usage across all pods exceeds 'Allocatable'. More details on eviction policy can be found on the [node pressure eviction](/docs/concepts/scheduling-eviction/node-pressure-eviction/... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/reserve-compute-resources.md | main | kubernetes | [
-0.022651541978120804,
0.011348598636686802,
0.027051229029893875,
0.021595943719148636,
-0.024858267977833748,
-0.006180663593113422,
-0.016484782099723816,
-0.032360952347517014,
0.030062884092330933,
0.030276305973529816,
-0.010770664550364017,
-0.05923140048980713,
0.02726675011217594,
... | 0.160437 |
This page describes the CoreDNS upgrade process and how to install CoreDNS instead of kube-dns. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## About CoreDNS [CoreDNS](https://coredns.io) is a flexible, extensible DNS server that can serve as the Kubernetes cluster... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/coredns.md | main | kubernetes | [
-0.06017486751079559,
-0.08634030818939209,
0.05818427726626396,
-0.0777784213423729,
-0.10015828162431717,
0.012550505809485912,
-0.0797208920121193,
-0.02503196708858013,
0.03556455299258232,
0.062168680131435394,
-0.043797560036182404,
-0.10944449156522751,
-0.018907900899648666,
-0.042... | 0.109195 |
This page shows how to enable or disable feature gates to control specific Kubernetes features in your cluster. Enabling feature gates allows you to test and use Alpha or Beta features before they become generally available. {{< note >}} For some stable (GA) gates, you can also disable them, usually for one minor relea... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/configure-feature-gates.md | main | kubernetes | [
0.05530380830168724,
-0.038721486926078796,
0.013681250624358654,
0.04167451709508896,
-0.02228185534477234,
0.025714967399835587,
-0.02022853121161461,
-0.10036426037549973,
-0.03272968903183937,
0.06119609251618385,
-0.04049244150519371,
-0.033696673810482025,
-0.053110986948013306,
0.01... | 0.094321 |
manifests View the feature gates configured in the static pod manifest: ```shell kubectl -n kube-system get pod kube-apiserver- -o yaml | grep feature-gates ``` ### Check kubelet configuration Use the kubelet's configz endpoint: ```shell kubectl proxy --port=8001 & curl -sSL "http://localhost:8001/api/v1/nodes//proxy/c... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/configure-feature-gates.md | main | kubernetes | [
0.051136553287506104,
-0.03332844004034996,
0.031026532873511314,
-0.00379749177955091,
-0.04008391126990318,
-0.040948137640953064,
-0.06679906696081161,
-0.03316764906048775,
0.035373661667108536,
0.008670961484313011,
-0.02716626226902008,
-0.0728052631020546,
-0.04601563885807991,
-0.0... | 0.138086 |
All of the APIs in Kubernetes that let you write persistent API resource data support at-rest encryption. For example, you can enable at-rest encryption for {{< glossary\_tooltip text="Secrets" term\_id="secret" >}}. This at-rest encryption is additional to any system-level encryption for the etcd cluster or for the fi... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/encrypt-data.md | main | kubernetes | [
-0.04791028052568436,
0.07255518436431885,
0.023015271872282028,
-0.012593831866979599,
-0.015703223645687103,
-0.007530693430453539,
0.011829034425318241,
-0.05073567479848862,
0.1194869875907898,
0.03007875569164753,
-0.046088483184576035,
-0.06725169718265533,
0.02810000441968441,
-0.01... | 0.002034 |
{} # do not encrypt Events even though \*.\* is specified below - resources: - '\*.apps' # wildcard match requires Kubernetes 1.27 or later providers: - aescbc: keys: - name: key2 secret: c2VjcmV0IGlzIHNlY3VyZSwgb3IgaXMgaXQ/Cg== - resources: - '\*.\*' # wildcard match requires Kubernetes 1.27 or later providers: - aesc... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/encrypt-data.md | main | kubernetes | [
-0.01176865492016077,
0.04864560067653656,
0.051459524780511856,
0.015543930232524872,
0.03956313803792,
0.011233649216592312,
0.08381239324808121,
-0.0632200613617897,
0.12043198943138123,
0.008540702983736992,
-0.05455300211906433,
-0.12112828344106674,
0.01927381195127964,
0.00777158699... | 0.087428 |
because of trailing "." - events providers: - identity: {} # and then other entries in resources ``` Ensure that the exemption is listed \_before\_ the wildcard '`\*.\*`' item in the resources array to give it precedence. For more detailed information about the `EncryptionConfiguration` struct, please refer to the [enc... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/encrypt-data.md | main | kubernetes | [
-0.03414032608270645,
0.08134514093399048,
0.06739308685064316,
-0.0028823385946452618,
0.0524752214550972,
0.028775718063116074,
0.022080576047301292,
-0.06603638082742691,
0.09121482819318771,
0.001741105574183166,
-0.0012804423458874226,
-0.012705747969448566,
0.03850730136036873,
0.027... | -0.033405 |
`identity` provider is the default if you do not specify otherwise. \*\*The `identity` provider does not encrypt stored data and provides \_no\_ additional confidentiality protection.\*\* ### Key storage #### Local key storage Encrypting secret data with a locally managed key protects against an etcd compromise, but it... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/encrypt-data.md | main | kubernetes | [
-0.041786935180425644,
0.09812814742326736,
0.0766577273607254,
-0.008912939578294754,
0.02419225312769413,
0.01593632809817791,
0.05400737747550011,
-0.028195397928357124,
0.12238197773694992,
0.049158576875925064,
-0.0063478099182248116,
-0.008721929974853992,
0.0798204094171524,
-0.0473... | 0.093134 |
can use this command: ```shell head -c 32 /dev/urandom | base64 ``` {{% /tab %}} {{% tab name="Windows" %}} Generate a 32-byte random key and base64 encode it. You can use this command: ```powershell # Do not run this in a session where you have set a random number # generator seed. [Convert]::ToBase64String((1..32|%{[... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/encrypt-data.md | main | kubernetes | [
0.04527755454182625,
0.04870530590415001,
-0.12910379469394684,
0.03481572866439819,
-0.019408369436860085,
0.02329397201538086,
0.023333212360739708,
-0.033860448747873306,
0.013056900352239609,
0.08910577744245529,
-0.06004316732287407,
-0.020869038999080658,
0.07010546326637268,
-0.0271... | -0.046451 |
turn to each API server. {{< caution >}} For cluster configurations with two or more control plane nodes, the encryption configuration should be identical across each control plane node. If there is a difference in the encryption provider configuration between control plane nodes, this difference may mean that the kube... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/encrypt-data.md | main | kubernetes | [
0.009716770611703396,
0.021729199215769768,
0.025293009355664253,
-0.015376443974673748,
0.004424688406288624,
0.0020756220910698175,
-0.06428360193967819,
-0.05513157695531845,
0.07736138999462128,
0.029489055275917053,
-0.04171700403094292,
-0.040611349046230316,
0.04629385471343994,
-0.... | -0.002161 |
objects that are already stored. For this example, you have configured your cluster so that Secrets are encrypted on write. Performing a replace operation for each Secret will encrypt that content at rest, where the objects are unchanged. You can make this change across all Secrets in your cluster: ```shell # Run this ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/encrypt-data.md | main | kubernetes | [
-0.0029008579440414906,
0.04158787429332733,
0.009816206060349941,
0.07047426700592041,
-0.03152789920568466,
-0.04079536348581314,
-0.08252287656068802,
-0.06592059135437012,
0.10513456165790558,
0.03572942689061165,
-0.03466828167438507,
-0.04305550083518028,
0.02208658494055271,
-0.0615... | 0.095173 |
the configuration. ## Decrypt all data {#decrypting-all-data} This example shows how to stop encrypting the Secret API at rest. If you are encrypting other API kinds, adjust the steps to match. To disable encryption at rest, place the `identity` provider as the first entry in your encryption configuration file: ```yaml... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/encrypt-data.md | main | kubernetes | [
-0.007554684765636921,
0.08574491739273071,
0.0345168299973011,
-0.012160468846559525,
-0.005146331619471312,
-0.023987626656889915,
-0.05493622273206711,
-0.03446631133556366,
0.09267525374889374,
0.053958866745233536,
-0.03336154669523239,
-0.04849806800484657,
-0.00855474453419447,
-0.0... | 0.006339 |
This page shows how to view, work in, and delete {{< glossary\_tooltip text="namespaces" term\_id="namespace" >}}. The page also shows how to use Kubernetes namespaces to subdivide your cluster. ## {{% heading "prerequisites" %}} \* Have an [existing Kubernetes cluster](/docs/setup/). \* You have a basic understanding ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/namespaces.md | main | kubernetes | [
-0.023872433230280876,
-0.0396500863134861,
0.05466427654027939,
0.010206317529082298,
-0.02791980840265751,
-0.00014727334200870246,
0.050903573632240295,
-0.09120292961597443,
0.05065402388572693,
0.04822442680597305,
0.004747828934341669,
-0.09290482103824615,
0.0036596409045159817,
-0.... | 0.087968 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.