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 |
|---|---|---|---|---|---|
a version to upgrade to, and run the appropriate command. For example: ```shell # replace x with the patch version you picked for this upgrade sudo kubeadm upgrade apply v{{< skew currentVersion >}}.x ``` Once the command finishes you should see: ``` [upgrade/successful] SUCCESS! Your cluster was upgraded to "v{{< skew... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md | main | kubernetes | [
0.0465087890625,
-0.0970548540353775,
0.03435163199901581,
-0.04246532544493675,
-0.033599913120269775,
0.035893604159355164,
-0.051958587020635605,
-0.06244421750307083,
0.010922430083155632,
0.07844824343919754,
0.043404266238212585,
-0.08039648830890656,
-0.02742421068251133,
-0.0963852... | 0.038717 |
node kubectl uncordon ``` ## Upgrade worker nodes The upgrade procedure on worker nodes should be executed one node at a time or few nodes at a time, without compromising the minimum required capacity for running your workloads. The following pages show how to upgrade Linux and Windows worker nodes: \* [Upgrade Linux n... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md | main | kubernetes | [
0.017339246347546577,
0.006370896939188242,
-0.035223886370658875,
0.008157902397215366,
0.0058418987318873405,
-0.04043405503034592,
-0.0568680502474308,
-0.07244887948036194,
-0.009385152719914913,
0.0779670849442482,
-0.0036443634890019894,
-0.07951579242944717,
-0.015495628118515015,
-... | 0.155513 |
{{< feature-state for\_k8s\_version="v1.18" state="beta" >}} This page explains how to upgrade a Windows node created with kubeadm. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs-node-upgrade.md" >}} {{< version-check >}} \* Familiarize yourself with [the process for upgrading the rest of your ku... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes.md | main | kubernetes | [
0.044049810618162155,
-0.007262672297656536,
0.046963226050138474,
0.016223646700382233,
-0.022104645147919655,
0.06010722741484642,
-0.040584128350019455,
-0.07914825528860092,
-0.04309512674808502,
0.10002948343753815,
-0.04550323635339737,
-0.08910734206438065,
-0.02288919873535633,
-0.... | 0.062731 |
This page explains how to configure the kubelet's cgroup driver to match the container runtime cgroup driver for kubeadm clusters. ## {{% heading "prerequisites" %}} You should be familiar with the Kubernetes [container runtime requirements](/docs/setup/production-environment/container-runtimes). ## Configuring the con... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md | main | kubernetes | [
0.009827880188822746,
0.01052035391330719,
0.011782938614487648,
-0.032304517924785614,
-0.08710639923810959,
0.03107900172472,
-0.06012469530105591,
0.007795748766511679,
0.047387197613716125,
-0.06613321602344513,
-0.04281741753220558,
-0.11372935771942139,
-0.00003124705472146161,
-0.05... | 0.131517 |
nodes For each node in the cluster: - [Drain the node](/docs/tasks/administer-cluster/safely-drain-node) using `kubectl drain --ignore-daemonsets` - Stop the kubelet using `systemctl stop kubelet` - Stop the container runtime - Modify the container runtime cgroup driver to `systemd` - Set `cgroupDriver: systemd` in `/v... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md | main | kubernetes | [
-0.010947735980153084,
0.06734979152679443,
0.011788723058998585,
0.029795590788125992,
-0.04970702528953552,
-0.02800317294895649,
-0.050425637513399124,
-0.02278088964521885,
0.04764191061258316,
-0.013087895698845387,
-0.054509710520505905,
-0.06377141177654266,
-0.022352345287799835,
-... | 0.17493 |
kubeadm does not support automated ways of reconfiguring components that were deployed on managed nodes. One way of automating this would be by using a custom [operator](/docs/concepts/extend-kubernetes/operator/). To modify the components configuration you must manually edit associated cluster objects and files on dis... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-reconfigure.md | main | kubernetes | [
0.0852709412574768,
-0.056524522602558136,
0.01648522913455963,
0.02597559429705143,
-0.052943937480449677,
0.038017526268959045,
-0.02369113825261593,
-0.03091247007250786,
-0.02592049539089203,
0.0810299664735794,
-0.023725664243102074,
-0.07430778443813324,
0.031461846083402634,
-0.0410... | 0.064589 |
a Kubernetes control plane component (`apiserver`, `controller-manager` or `scheduler`). {{< note >}} Updating a file in `/etc/kubernetes/manifests` will tell the kubelet to restart the static Pod for the corresponding component. Try doing these changes one node at a time to leave the cluster without downtime. {{< /not... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-reconfigure.md | main | kubernetes | [
0.06314665079116821,
-0.0017420552903786302,
0.04457804933190346,
0.041027650237083435,
-0.03140744939446449,
0.017323117703199387,
-0.08392556756734848,
-0.02935751900076866,
0.041687775403261185,
0.03147151321172714,
-0.04130155220627785,
-0.05772263929247856,
-0.01981782354414463,
-0.05... | 0.107615 |
can use: ```shell kubectl edit no ``` During `kubeadm upgrade` the contents of such a Node might get overwritten. If you would like to persist your modifications to the Node object after upgrade, you can prepare a [kubectl patch](/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch/) and apply it to th... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-reconfigure.md | main | kubernetes | [
0.03198392316699028,
-0.026676708832383156,
-0.01111867930740118,
0.04779328405857086,
0.00001076328680937877,
0.05774702876806259,
-0.02758907899260521,
-0.038791704922914505,
0.013522767461836338,
0.09235159307718277,
0.01807302050292492,
-0.009489769116044044,
-0.0130279790610075,
-0.12... | 0.102706 |
{{< feature-state for\_k8s\_version="v1.15" state="stable" >}} Client certificates generated by [kubeadm](/docs/reference/setup-tools/kubeadm/) expire after 1 year. This page explains how to manage certificate renewals with kubeadm. It also covers other tasks related to kubeadm certificate management. The Kubernetes pr... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md | main | kubernetes | [
0.004497040528804064,
0.055061377584934235,
0.05998627468943596,
-0.015507638454437256,
-0.047687284648418427,
0.010192694142460823,
-0.047294098883867264,
0.019185176119208336,
-0.003127078525722027,
-0.005042749457061291,
-0.0053306990303099155,
-0.04195231571793556,
0.057500630617141724,
... | 0.050725 |
These CSR files will include all the specification for credentials that components deployed by kubeadm require. ### Automated preparation of component credentials by using kubeadm phases Alternatively, it is possible to use kubeadm phase commands to automate this process. - Go to a host that you want to prepare as a ku... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md | main | kubernetes | [
-0.02068728767335415,
-0.006064335349947214,
-0.05124763771891594,
0.000757189525756985,
-0.06295233964920044,
0.0037015664856880903,
-0.011507345363497734,
0.03108329139649868,
0.041176728904247284,
0.016480974853038788,
-0.017425833269953728,
-0.1647884100675583,
0.08857221156358719,
-0.... | 0.046774 |
rotation fails](/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/#kubelet-client-cert). {{< note >}} On nodes created with `kubeadm init` from versions prior to kubeadm version 1.17, there is a [bug](https://github.com/kubernetes/kubeadm/issues/1753) where you manually have to modify the content... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md | main | kubernetes | [
-0.004799812100827694,
0.03997993469238281,
0.03508177399635315,
-0.06673391908407211,
-0.06690595299005508,
-0.01703980192542076,
-0.07141520828008652,
-0.010973739437758923,
0.08262548595666885,
-0.0014929105527698994,
0.05858936905860901,
-0.03477737680077553,
0.07142247259616852,
-0.06... | -0.049464 |
{{< /caution >}} ### Set up a signer The Kubernetes Certificate Authority does not work out of the box. You can configure an external signer such as [cert-manager](https://cert-manager.io/docs/configuration/ca/), or you can use the built-in signer. The built-in signer is part of [`kube-controller-manager`](/docs/refere... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md | main | kubernetes | [
0.0348486453294754,
-0.014234725385904312,
0.00597592256963253,
0.010346608236432076,
0.0052667465060949326,
0.00673303846269846,
-0.025347605347633362,
0.00946691632270813,
0.06669070571660995,
0.03595405071973801,
0.010730903595685959,
-0.11482971906661987,
0.06867804378271103,
0.0540069... | 0.051253 |
[Certificate Rotation](/docs/reference/access-authn-authz/kubelet-tls-bootstrapping/#certificate-rotation). If you are looking for a solution for automatic approval of these CSRs it is recommended that you contact your cloud provider and ask if they have a CSR signer that verifies the node identity with an out of band ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md | main | kubernetes | [
-0.0950239971280098,
0.03248171880841255,
-0.06121159344911575,
-0.05412464961409569,
-0.05055856704711914,
0.014600214548408985,
0.015592854470014572,
-0.01693476177752018,
0.10886795073747635,
-0.02060306817293167,
0.03190621733665466,
-0.060056641697883606,
0.09171902388334274,
-0.04669... | 0.023286 |
be overridden with the flags `--cert-dir` and `--kubeconfig-dir`, respectively. To pass custom options to `kubeadm certs generate-csr` use the `--config` flag, which accepts a [kubeadm configuration](/docs/reference/config-api/kubeadm-config.v1beta4/) file, similarly to commands such as `kubeadm init`. Any specificatio... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md | main | kubernetes | [
0.010497817769646645,
0.04034264385700226,
-0.05125594884157181,
-0.004733989480882883,
-0.03889016434550285,
0.004899572115391493,
-0.03411144018173218,
0.033470675349235535,
0.0357322171330452,
-0.027193836867809296,
0.01819082349538803,
-0.13182097673416138,
0.04739750921726227,
-0.0314... | 0.003359 |
a pre-populated `kubelet.conf` is needed. {{< /note >}} #### Control plane nodes Execute the following command on primary (`kubeadm init`) and secondary (`kubeadm join --control-plane`) control plane nodes to generate all CSR files: ```shell sudo kubeadm certs generate-csr ``` If external etcd is to be used, follow the... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md | main | kubernetes | [
-0.04575666785240173,
0.028988415375351906,
0.000016046318705775775,
-0.0205337256193161,
0.0011282414197921753,
-0.014756663702428341,
-0.10238634049892426,
-0.04104888439178467,
0.02680046111345291,
-0.03205224871635437,
0.026209719479084015,
-0.10150035470724106,
0.04024377092719078,
-0... | 0.04737 |
following script in the `/etc/kubernetes` directory, navigate to the directory and execute the script. ```bash #!/bin/bash # Cleanup CSR files rm -f ./\*.csr ./pki/\*.csr ./pki/etcd/\*.csr # Clean all CSR files # Cleanup CRT files that were already embedded in kubeconfig files rm -f ./\*.crt ``` Optionally, move `.srl`... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md | main | kubernetes | [
-0.012107017450034618,
0.03568530082702637,
0.017166564241051674,
0.013709512539207935,
0.026610272005200386,
-0.036831822246313095,
-0.031058572232723236,
-0.04256962612271309,
0.08770085126161575,
0.0143421096727252,
0.023794611915946007,
-0.08977795392274857,
0.0788947269320488,
0.00506... | 0.035402 |
This page shows how to create an external load balancer. When creating a {{< glossary\_tooltip text="Service" term\_id="service" >}}, you have the option of automatically creating a cloud load balancer. This provides an externally-accessible IP address that sends traffic to the correct port on your cluster nodes, \_pro... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md | main | kubernetes | [
-0.0852314904332161,
-0.06042586266994476,
-0.0021438212133944035,
-0.012045674957334995,
-0.06957646459341049,
-0.017205961048603058,
0.05727032572031021,
-0.017024071887135506,
0.03645166754722595,
0.08608537912368774,
-0.034666240215301514,
-0.061603762209415436,
0.03103782795369625,
-0... | 0.170655 |
activates this feature. For example: ```yaml apiVersion: v1 kind: Service metadata: name: example-service spec: selector: app: example ports: - port: 8765 targetPort: 9376 externalTrafficPolicy: Local type: LoadBalancer ``` ### Caveats and limitations when preserving source IPs Load balancing services from some cloud p... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md | main | kubernetes | [
-0.020428035408258438,
-0.029899239540100098,
0.023836607113480568,
0.009307853877544403,
0.01257465872913599,
-0.08100450038909912,
0.015321719460189342,
-0.00710378447547555,
0.0702524483203888,
0.043036144226789474,
-0.03984316438436508,
-0.0532214492559433,
0.014224505051970482,
-0.028... | 0.1953 |
This page shows how to use `kubectl port-forward` to connect to a MongoDB server running in a Kubernetes cluster. This type of connection can be useful for database debugging. ## {{% heading "prerequisites" %}} \* {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} \* Install [MongoDB Shell](https://www.mo... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md | main | kubernetes | [
0.04589568078517914,
0.00047185277799144387,
-0.012243821285665035,
0.021003976464271545,
-0.06726910173892975,
0.007699998095631599,
-0.06790293008089066,
-0.019276440143585205,
0.03594040870666504,
0.12071114033460617,
-0.032240379601716995,
-0.05895664170384407,
-0.029577476903796196,
-... | 0.117189 |
Forwarding from [::1]:63753 -> 27017 ``` ## Discussion Connections made to local port 28015 are forwarded to port 27017 of the Pod that is running the MongoDB server. With this connection in place, you can use your local workstation to debug the database that is running in the Pod. {{< note >}} `kubectl port-forward` i... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md | main | kubernetes | [
0.05673130974173546,
0.04236554726958275,
0.028677191585302353,
-0.02846885286271572,
-0.0066584572196006775,
-0.006720598321408033,
-0.05581345781683922,
-0.03706131875514984,
0.019658328965306282,
0.08663211017847061,
-0.0695873349905014,
-0.03376343473792076,
-0.04148377478122711,
-0.02... | 0.138974 |
This page shows how to create a Kubernetes Service object that external clients can use to access an application running in a cluster. The Service provides load balancing for an application that has two running instances. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} ## {{% heading "obje... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/service-access-application-cluster.md | main | kubernetes | [
-0.019735239446163177,
-0.030292421579360962,
0.01929713599383831,
-0.027023298665881157,
-0.09484335035085678,
-0.036488402634859085,
-0.013884957879781723,
0.03529426082968712,
0.032934773713350296,
0.05576366186141968,
-0.06951726227998734,
-0.07013815641403198,
0.02761467918753624,
-0.... | 0.154624 |
World application, enter this command: kubectl delete deployment hello-world ## {{% heading "whatsnext" %}} Follow the [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/) tutorial. | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/service-access-application-cluster.md | main | kubernetes | [
0.056713808327913284,
0.03549071401357651,
0.035125844180583954,
-0.0850253775715828,
-0.05167779326438904,
-0.03986255079507828,
-0.014122544787824154,
-0.06238406151533127,
0.08885268121957779,
0.04891887307167053,
-0.031373098492622375,
-0.06943920254707336,
0.011135412380099297,
0.0173... | 0.123236 |
{{% pageinfo color="primary" %}} \*\*Kubernetes Dashboard is deprecated and unmaintained.\*\* The Kubernetes Dashboard project has been archived and is no longer actively maintained. For new installations, consider using [Headlamp](https://headlamp.dev/). {{% /pageinfo %}} {{< note >}} For in-cluster deployments simila... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/web-ui-dashboard.md | main | kubernetes | [
0.004773784428834915,
0.026856552809476852,
0.011693146079778671,
-0.03330344706773758,
0.04288731887936592,
0.026027293875813484,
-0.009542363695800304,
0.001791075337678194,
0.020085331052541733,
0.03971399739384651,
-0.028277942910790443,
-0.03539552912116051,
0.009642273187637329,
-0.0... | 0.189687 |
It must start with a lowercase character, and end with a lowercase character or a number, and contain only lowercase letters, numbers and dashes (-). It is limited to 24 characters. Leading and trailing spaces are ignored. - \*\*Container image\*\* (mandatory): The URL of a public Docker [container image](/docs/concept... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/web-ui-dashboard.md | main | kubernetes | [
0.0059930672869086266,
-0.015094082802534103,
0.05833917111158371,
-0.06724193692207336,
-0.03603840619325638,
-0.0012559377355501056,
0.013026559725403786,
0.0431089885532856,
-0.011985009536147118,
0.022137073799967766,
0.004151434171944857,
-0.08332882076501846,
0.07649517059326172,
0.0... | 0.080601 |
no secret is applied. - \*\*CPU requirement (cores)\*\* and \*\*Memory requirement (MiB)\*\*: You can specify the minimum [resource limits](/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/) for the container. By default, Pods run with unbounded CPU and memory limits. - \*\*Run command\*\* and \... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/web-ui-dashboard.md | main | kubernetes | [
0.01912510395050049,
0.0375608392059803,
0.003371411468833685,
0.03403171896934509,
-0.035917289555072784,
-0.052439991384744644,
-0.003273362759500742,
0.03305742144584656,
0.01682431995868683,
0.04438458010554314,
-0.04240155220031738,
-0.055482055991888046,
0.009658804163336754,
-0.0453... | 0.160233 |
information, see the [Kubernetes Dashboard project page](https://github.com/kubernetes/dashboard). | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/web-ui-dashboard.md | main | kubernetes | [
0.039249781519174576,
-0.03987174481153488,
-0.017442816868424416,
-0.02464650571346283,
0.005782093852758408,
0.005293004214763641,
-0.04593728855252266,
0.017118647694587708,
0.009493492543697357,
0.04696252569556236,
-0.03796045854687691,
-0.03862104192376137,
0.005482643377035856,
-0.0... | 0.222343 |
This page shows how to use kubectl to list all of the Container images for Pods running in a cluster. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} In this exercise you will use kubectl to fetch all of the Pods running in a cluster, and format the output to pull out... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/list-all-running-container-images.md | main | kubernetes | [
0.0721665620803833,
0.05248848348855972,
0.04806385561823845,
0.029785871505737305,
0.048204608261585236,
-0.010580992326140404,
0.0015779644018039107,
0.011350600980222225,
-0.027262883260846138,
0.011286734603345394,
-0.0010211964836344123,
-0.08380141854286194,
0.03338054567575455,
-0.0... | 0.09176 |
This task shows how to create a \_frontend\_ and a \_backend\_ microservice. The backend microservice is a hello greeter. The frontend exposes the backend using nginx and a Kubernetes {{< glossary\_tooltip term\_id="service" >}} object. ## {{% heading "objectives" %}} \* Create and run a sample `hello` backend microser... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md | main | kubernetes | [
-0.09898264706134796,
-0.031365953385829926,
0.017072435468435287,
-0.02581537701189518,
-0.08268455415964127,
-0.03611182048916817,
0.03833948075771332,
-0.0405791774392128,
0.034547969698905945,
0.06337469816207886,
-0.04952728748321533,
-0.10332263261079788,
0.02303318865597248,
-0.0064... | 0.131311 |
frontend services, is that the configuration for the frontend Service has `type: LoadBalancer`, which means that the Service uses a load balancer provisioned by your cloud provider and will be accessible from outside the cluster. {{% code\_sample file="service/access/frontend-service.yaml" %}} {{% code\_sample file="se... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md | main | kubernetes | [
-0.04378124698996544,
0.03635937348008156,
0.0006854239036329091,
-0.025999095290899277,
-0.028315825387835503,
-0.030333638191223145,
-0.008700333535671234,
-0.015988973900675774,
0.059211600571870804,
0.023218005895614624,
-0.0742916464805603,
-0.027717377990484238,
0.02781887724995613,
... | 0.07645 |
This page shows how to connect to services running on the Kubernetes cluster. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## Accessing services running on the cluster In Kubernetes, [nodes](/docs/concepts/architecture/nodes/), [pods](/docs/concepts/workloads/pods/... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/access-cluster-services.md | main | kubernetes | [
0.022474851459264755,
-0.01035782415419817,
0.019862636923789978,
-0.023784715682268143,
-0.021664507687091827,
0.0399867407977581,
-0.05602843314409256,
-0.0053468672558665276,
0.05263948068022728,
0.07312678545713425,
-0.05010495334863663,
0.00975237600505352,
0.002745402744039893,
-0.04... | 0.162259 |
a name for your port, you don't have to specify \*port\_name\* in the URL. You can also use the port number in place of the \*port\_name\* for both named and unnamed ports. By default, the API server proxies to your service using HTTP. To use HTTPS, prefix the service name with `https:`: `http:///api/v1/namespaces//ser... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/access-cluster-services.md | main | kubernetes | [
-0.041942745447158813,
0.05675996094942093,
-0.006883196532726288,
-0.03883058950304985,
-0.06978639215230942,
-0.03425212576985359,
-0.0559895783662796,
0.006013060454279184,
0.049993883818387985,
0.04320194572210312,
-0.06997759640216827,
-0.03997260704636574,
0.012390468269586563,
0.072... | 0.036747 |
This topic discusses multiple ways to interact with clusters. ## Accessing for the first time with kubectl When accessing the Kubernetes API for the first time, we suggest using the Kubernetes CLI, `kubectl`. To access a cluster, you need to know the location of the cluster and have credentials to access it. Typically,... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/access-cluster.md | main | kubernetes | [
0.030877860262989998,
-0.012461426667869091,
-0.03461473435163498,
-0.005586626939475536,
-0.055452752858400345,
0.05028141662478447,
-0.05559332296252251,
-0.00003231572190998122,
0.09144831448793411,
0.022732211276888847,
-0.05335414409637451,
-0.06477604061365128,
0.00386493350379169,
-... | 0.157077 |
it may take special configuration to get your http client to use root certificate. On some clusters, the apiserver does not require authentication; it may serve on localhost, or be protected by a firewall. There is not a standard for this. [Controlling Access to the API](/docs/concepts/security/controlling-access) desc... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/access-cluster.md | main | kubernetes | [
-0.006330898497253656,
0.02629707008600235,
-0.005821404978632927,
-0.054637882858514786,
-0.06613050401210785,
-0.021692801266908646,
-0.07538772374391556,
0.025228435173630714,
0.07128393650054932,
-0.0042145755141973495,
-0.01631215028464794,
-0.01507913414388895,
0.02223495952785015,
0... | 0.041408 |
services: - are provided by some cloud providers (e.g. AWS ELB, Google Cloud Load Balancer) - are created automatically when the Kubernetes service has type `LoadBalancer` - use UDP/TCP only - implementation varies by cloud provider. Kubernetes users will typically not need to worry about anything other than the first ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/access-cluster.md | main | kubernetes | [
-0.019761832430958748,
-0.0715121254324913,
0.034681688994169235,
-0.031121984124183655,
-0.02519347332417965,
0.023925913497805595,
0.05384431779384613,
-0.04711209610104561,
0.11101280152797699,
0.01908155344426632,
-0.0091880327090621,
0.0010055971797555685,
-0.007094926666468382,
-0.02... | 0.241297 |
This page shows how to configure access to multiple clusters by using configuration files. After your clusters, users, and contexts are defined in one or more configuration files, you can quickly switch between clusters by using the `kubectl config use-context` command. {{< note >}} A file that is used to configure acc... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md | main | kubernetes | [
-0.004840725567191839,
-0.015147675760090351,
-0.03943011537194252,
-0.003737852443009615,
0.02181749790906906,
-0.009698127396404743,
0.07166025042533875,
-0.03862609341740608,
0.01607828587293625,
-0.012703685089945793,
0.02527112141251564,
-0.08606290072202682,
0.07895815372467041,
-0.0... | 0.141155 |
name: test contexts: - context: cluster: development namespace: frontend user: developer name: dev-frontend - context: cluster: development namespace: storage user: developer name: dev-storage - context: cluster: test namespace: default user: experimenter name: exp-test current-context: "" kind: Config preferences: {} ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md | main | kubernetes | [
-0.016939135268330574,
0.031370703130960464,
-0.06871897727251053,
0.0062030889093875885,
-0.05735732987523079,
-0.006971574854105711,
0.043604061007499695,
0.025236720219254494,
0.07727479934692383,
0.03605729341506958,
-0.0023195152170956135,
-0.10381801426410675,
0.08935513347387314,
0.... | 0.036081 |
`KUBECONFIG` environment variable, familiarize yourself with the configuration files in the list. Temporarily append two paths to your `KUBECONFIG` environment variable. For example: ### Linux ```shell export KUBECONFIG="${KUBECONFIG}:config-demo:config-demo-2" ``` ### Windows PowerShell ```powershell $Env:KUBECONFIG=(... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md | main | kubernetes | [
0.06835731118917465,
-0.019264740869402885,
-0.01598469913005829,
0.03902274742722511,
-0.00964584294706583,
-0.002058347687125206,
-0.011429042555391788,
-0.016445236280560493,
0.02650630474090576,
0.03875833749771118,
-0.0030116147827357054,
-0.10068061202764511,
-0.00598558597266674,
-0... | 0.076536 |
This page shows how to use a Volume to communicate between two Containers running in the same Pod. See also how to allow processes to communicate by [sharing process namespace](/docs/tasks/configure-pod-container/share-process-namespace/) between containers. ## {{% heading "prerequisites" %}} {{< include "task-tutorial... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md | main | kubernetes | [
-0.006951368413865566,
-0.023485226556658745,
0.001213554758578539,
-0.017181145027279854,
-0.04399312660098076,
-0.07805095613002777,
-0.0363740473985672,
0.003224477870389819,
-0.0009414332453161478,
0.01774260215461254,
-0.06764502823352814,
0.00026906642597168684,
0.0026960386894643307,
... | 0.121125 |
This page shows how to enable and configure certificate rotation for the kubelet. {{< feature-state for\_k8s\_version="v1.19" state="stable" >}} ## {{% heading "prerequisites" %}} \* Kubernetes version 1.8.0 or later is required ## Overview The kubelet uses certificates for authenticating to the Kubernetes API. By defa... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/tls/certificate-rotation.md | main | kubernetes | [
-0.03992094472050667,
0.05004007741808891,
0.04808301851153374,
-0.012843839824199677,
-0.09228848665952682,
0.015895215794444084,
-0.04312209039926529,
-0.020730359479784966,
0.09586154669523239,
-0.03170035406947136,
-0.007126000244170427,
-0.004570217337459326,
0.07106059044599533,
0.00... | -0.002872 |
This page shows how to manually rotate the certificate authority (CA) certificates. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} - For more information about authentication in Kubernetes, see [Authenticating](/docs/reference/access-authn-authz/authentication). - For more information abo... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/tls/manual-rotation-of-ca-certificates.md | main | kubernetes | [
-0.006804516073316336,
0.06153571233153343,
0.02174476534128189,
-0.011586378328502178,
-0.06431720405817032,
-0.0018849148182198405,
-0.03668886050581932,
-0.00722297839820385,
0.0810282900929451,
0.034132882952690125,
-0.006842662114650011,
-0.01985711045563221,
0.10002202540636063,
0.02... | -0.014663 |
certificates. 1. Restart the kubelet by update the file against `clientCAFile` in kubelet configuration and `certificate-authority-data` in `kubelet.conf` to use both the old and new CA on all nodes. If your kubelet is not using client certificate rotation, update `client-certificate-data` and `client-key-data` in `kub... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/tls/manual-rotation-of-ca-certificates.md | main | kubernetes | [
0.0415106900036335,
0.02042011171579361,
0.06834983080625534,
-0.012161063961684704,
-0.06399083882570267,
-0.0114459078758955,
-0.05949917435646057,
-0.01709253527224064,
0.11006198823451996,
-0.00643558893352747,
0.004435637500137091,
-0.08036080747842789,
0.049990493804216385,
0.0135397... | 0.034111 |
Kubernetes provides a `certificates.k8s.io` API, which lets you provision TLS certificates signed by a Certificate Authority (CA) that you control. These CA and certificates can be used by your workloads to establish trust. `certificates.k8s.io` API uses a protocol that is similar to the [ACME draft](https://github.com... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/tls/managing-tls-in-a-cluster.md | main | kubernetes | [
-0.02058214321732521,
0.04402178153395653,
0.039012059569358826,
0.032731931656599045,
-0.02332935854792595,
0.001049509970471263,
-0.023282868787646294,
-0.002798008732497692,
0.07415638118982315,
0.03215991333127022,
-0.06826779991388321,
-0.08735550194978714,
0.0823109820485115,
0.08576... | 0.064442 |
certificates for those requests, and update the API object status with the issued certificate. ### Create a Certificate Authority You need an authority to provide the digital signature on the new certificate. First, create a signing certificate by running the following: ```shell cat <}} This uses the command line tool ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/tls/managing-tls-in-a-cluster.md | main | kubernetes | [
-0.037477172911167145,
0.10053286701440811,
-0.07394610345363617,
-0.021868497133255005,
-0.08924610167741776,
-0.05046940594911575,
-0.03938773274421692,
0.03821349889039993,
0.03387901559472084,
-0.016267890110611916,
-0.023656992241740227,
-0.09103327989578247,
0.0976649820804596,
0.007... | 0.072119 |
`--cluster-signing-cert-file` and `--cluster-signing-key-file` parameters to the controller manager with paths to your Certificate Authority's keypair. | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/tls/managing-tls-in-a-cluster.md | main | kubernetes | [
0.06581466645002365,
-0.015609425492584705,
-0.10748676210641861,
0.018254758790135384,
0.03749356418848038,
0.04010063409805298,
-0.019455021247267723,
0.02528727799654007,
-0.010226372629404068,
0.03706015646457672,
0.08265373110771179,
-0.07115091383457184,
0.0777280256152153,
0.0140261... | 0.014689 |
Kubernetes lets you use a public key infrastructure (PKI) to authenticate to your cluster as a client. A few steps are required in order to get a normal user to be able to authenticate and invoke an API. First, this user must have an [X.509](https://www.itu.int/rec/T-REC-X.509) certificate issued by an authority that y... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/tls/certificate-issue-client-csr.md | main | kubernetes | [
-0.015588817186653614,
0.04709979519248009,
-0.007603684905916452,
-0.023401349782943726,
-0.07195458561182022,
0.007757565006613731,
0.010864165611565113,
0.03502248600125313,
0.03984297066926956,
0.04630081728100777,
-0.03839323669672012,
-0.07299405336380005,
0.0635237768292427,
0.04415... | 0.081374 |
PKCS#10 certificate signing requests, refer to [RFC 2986](https://tools.ietf.org/html/rfc2986) \* Read about [ClusterTrustBundles](/docs/reference/access-authn-authz/certificate-signing-requests/#cluster-trust-bundles) | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/tls/certificate-issue-client-csr.md | main | kubernetes | [
-0.04305151849985123,
0.03049793653190136,
-0.059000708162784576,
0.0027722592931240797,
0.03641504421830177,
-0.004055995959788561,
0.027892066165804863,
0.02811851166188717,
-0.014201365411281586,
-0.020163023844361305,
-0.0012886965414509177,
-0.022119922563433647,
0.04664295166730881,
... | -0.021856 |
{{< feature-state state="stable" for\_k8s\_version="v1.26" >}} Kubernetes includes \*\*stable\*\* support for managing AMD and NVIDIA GPUs (graphical processing units) across different nodes in your cluster, using {{< glossary\_tooltip text="device plugins" term\_id="device-plugin" >}}. This page describes how users ca... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/manage-gpus/scheduling-gpus.md | main | kubernetes | [
0.02861415036022663,
-0.02763736993074417,
0.0419568195939064,
0.05279171094298363,
-0.0227936040610075,
-0.004683209583163261,
-0.04173728823661804,
-0.008170143701136112,
-0.004333644639700651,
0.017742417752742767,
-0.0532403327524662,
-0.05497008189558983,
-0.016322771087288857,
-0.024... | 0.177752 |
# NFD Feature label values: ["true"] # (optional) only schedule on nodes with PCI device 10 containers: - name: example-vector-add image: "registry.example/example-vector-add:v42" resources: limits: gpu-vendor.example/example-gpu: 1 # requesting 1 GPU {{< /highlight >}} #### GPU vendor implementations - [Intel](https:/... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/manage-gpus/scheduling-gpus.md | main | kubernetes | [
-0.019593747332692146,
0.047051701694726944,
0.01083168014883995,
0.02632194198668003,
0.02883361279964447,
0.008386436849832535,
-0.033800460398197174,
-0.048425521701574326,
-0.005141280125826597,
-0.06007393077015877,
-0.013843557797372341,
-0.05333101376891136,
-0.05150088295340538,
0.... | 0.126681 |
Setting up an extension API server to work with the aggregation layer allows the Kubernetes apiserver to be extended with additional APIs, which are not part of the core Kubernetes APIs. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} \* You must [configure the aggreg... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/setup-extension-api-server.md | main | kubernetes | [
-0.06457424908876419,
-0.007740730885416269,
0.09586014598608017,
0.002900786465033889,
-0.055886417627334595,
0.012008239515125751,
-0.06132499873638153,
-0.0028154419269412756,
0.07728370279073715,
0.019711270928382874,
-0.03426731377840042,
-0.044182270765304565,
0.017765924334526062,
0... | 0.110447 |
you currently have no objects of that resource type created. ## {{% heading "whatsnext" %}} \* Walk through the steps to [configure the API aggregation layer](/docs/tasks/extend-kubernetes/configure-aggregation-layer/) and enable the apiserver flags. \* For a high level overview, see [Extending the Kubernetes API with ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/setup-extension-api-server.md | main | kubernetes | [
-0.012175990268588066,
0.03641596809029579,
0.06428087502717972,
0.042707476764917374,
-0.06707200407981873,
0.06891246140003204,
0.02164277993142605,
-0.00883119460195303,
0.07167542725801468,
0.026151159778237343,
-0.05337274447083473,
-0.06546346098184586,
0.004396094009280205,
0.031120... | 0.115674 |
Kubernetes ships with a default scheduler that is described [here](/docs/reference/command-line-tools-reference/kube-scheduler/). If the default scheduler does not suit your needs you can implement your own scheduler. Moreover, you can even run multiple schedulers simultaneously alongside the default scheduler and inst... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md | main | kubernetes | [
-0.010609555058181286,
-0.03917234018445015,
0.04099111258983612,
0.016190189868211746,
-0.06539727747440338,
0.02142544649541378,
-0.06559185683727264,
-0.03260192647576332,
0.03751550614833832,
0.047156963497400284,
-0.09764397144317627,
-0.04454445838928223,
-0.009516915306448936,
0.038... | 0.065495 |
1/1 Running 0 2m ... ``` You should see a "Running" my-scheduler pod, in addition to the default kube-scheduler pod in this list. ### Enable leader election To run multiple-scheduler with leader election enabled, you must do the following: Update the following fields for the KubeSchedulerConfiguration in the `my-schedu... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md | main | kubernetes | [
-0.0017537424573674798,
-0.06016223505139351,
-0.0028700465336441994,
0.031371451914310455,
-0.06537489593029022,
0.04172699153423309,
-0.03325830027461052,
-0.03687027469277382,
0.0591772198677063,
0.07303408533334732,
-0.0171327106654644,
-0.07181362062692642,
-0.002180642681196332,
-0.0... | 0.094538 |
This page shows how to use an HTTP proxy to access the Kubernetes API. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} If you do not already have an application running in your cluster, start a Hello world application by entering this command: ```shell kubectl create ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/http-proxy-access-api.md | main | kubernetes | [
-0.022723505273461342,
-0.0016149694565683603,
0.046909186989068985,
-0.048492398113012314,
-0.08423078805208206,
-0.014244472607970238,
-0.04559095948934555,
-0.031361810863018036,
0.026809092611074448,
0.0944778323173523,
-0.061873339116573334,
-0.03985930234193802,
-0.0028120579663664103,... | 0.07739 |
The Konnectivity service provides a TCP level proxy for the control plane to cluster communication. ## {{% heading "prerequisites" %}} You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/setup-konnectivity.md | main | kubernetes | [
0.0324779748916626,
-0.012093192897737026,
-0.003805199172347784,
0.0437447614967823,
-0.042106952518224716,
0.04443979635834694,
-0.003339329967275262,
-0.005324022378772497,
0.04151129722595215,
0.09737648069858551,
-0.08765118569135666,
-0.07324931770563126,
-0.013090839609503746,
-0.03... | 0.087748 |
{{< feature-state for\_k8s\_version="v1.24" state="stable" >}} This page shows how to use a SOCKS5 proxy to access the API of a remote Kubernetes cluster. This is useful when the cluster you want to access does not expose its API directly on the public internet. ## {{% heading "prerequisites" %}} {{< include "task-tuto... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/socks5-proxy-access-api.md | main | kubernetes | [
-0.04995312914252281,
0.01175367459654808,
0.046525318175554276,
0.003158366773277521,
-0.06095302477478981,
0.04338812083005905,
-0.03205401822924614,
-0.02089867927134037,
-0.02991527132689953,
0.08553697913885117,
-0.07668177038431168,
-0.002926850924268365,
0.005978238768875599,
0.0261... | 0.120915 |
tunnel via the ssh command mentioned earlier, and defined either the environment variable or the `proxy-url` attribute, you can interact with your cluster through that proxy. For example: ```shell kubectl get pods ``` ```console NAMESPACE NAME READY STATUS RESTARTS AGE kube-system coredns-85cb69466-klwq8 1/1 Running 0 ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/socks5-proxy-access-api.md | main | kubernetes | [
0.010596898384392262,
-0.029867591336369514,
0.01809130609035492,
0.003942126873880625,
-0.08287917822599411,
0.034996602684259415,
-0.07270929217338562,
-0.02419082447886467,
0.04053895175457001,
0.05333545804023743,
-0.058720313012599945,
-0.06350681185722351,
-0.014386328868567944,
-0.0... | 0.090652 |
Configuring the [aggregation layer](/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/) allows the Kubernetes apiserver to be extended with additional APIs, which are not part of the core Kubernetes APIs. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/configure-aggregation-layer.md | main | kubernetes | [
-0.047146838158369064,
0.02346218004822731,
0.09877224266529083,
-0.012505983002483845,
-0.08141003549098969,
-0.0015927717322483659,
-0.017650945112109184,
-0.027665408328175545,
0.10056431591510773,
0.016029851511120796,
-0.07889030128717422,
-0.05391860753297806,
0.06526175886392593,
0.... | 0.018402 |
Client Authentication The Kubernetes apiserver connects to the extension apiserver over TLS, authenticating itself using a client certificate. You must provide the following to the Kubernetes apiserver upon startup, using the provided flags: \* private key file via `--proxy-client-key-file` \* signed client certificate... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/configure-aggregation-layer.md | main | kubernetes | [
-0.04561522975564003,
0.02732718549668789,
0.0311459731310606,
-0.07879159599542618,
-0.08353515714406967,
-0.019507724791765213,
0.0015082336030900478,
0.03213735297322273,
0.12690216302871704,
0.03535992652177811,
-0.04901112988591194,
-0.06440301239490509,
0.048111442476511,
0.084565646... | 0.026196 |
of the extension apiserver implementation to provide the above. Many do it by default, leveraging the `k8s.io/apiserver/` package. Others may provide options to override it using command-line options. In order to have permission to retrieve the configmap, an extension apiserver requires the appropriate role. There is a... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/configure-aggregation-layer.md | main | kubernetes | [
-0.027787454426288605,
0.05736706778407097,
-0.006869826465845108,
-0.027649560943245888,
-0.01003575511276722,
-0.04166583716869354,
0.012562085874378681,
0.027002863585948944,
0.020446816459298134,
0.049533408135175705,
-0.049540404230356216,
-0.08150187879800797,
0.0373770110309124,
0.0... | 0.131946 |
protect the CA's usage. {{< /warning >}} If you are not running kube-proxy on a host running the API server, then you must make sure that the system is enabled with the following `kube-apiserver` flag: --enable-aggregator-routing=true ### Register APIService objects You can dynamically configure what client requests ar... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/configure-aggregation-layer.md | main | kubernetes | [
-0.04808446392416954,
0.026047583669424057,
0.046056609600782394,
-0.01925504207611084,
-0.06624308973550797,
-0.014680083841085434,
-0.01654118299484253,
0.012743566185235977,
0.08615409582853317,
0.04661957919597626,
-0.036955706775188446,
-0.07393806427717209,
0.011666782200336456,
0.03... | 0.123211 |
This page explains how to add versioning information to [CustomResourceDefinitions](/docs/reference/kubernetes-api/extend-resources/custom-resource-definition-v1/), to indicate the stability level of your CustomResourceDefinitions or advance your API to a new version with conversion between API representations. It also... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning.md | main | kubernetes | [
-0.026392510160803795,
0.0019363266183063388,
0.09101495146751404,
-0.012267122976481915,
0.0007994176703505218,
0.04358609393239021,
-0.026182029396295547,
-0.0064729019068181515,
0.040551912039518356,
0.004903940483927727,
-0.0336543545126915,
-0.021799655631184578,
-0.02480556070804596,
... | 0.059301 |
support for the old version in conversion webhooks. ## Specify multiple versions The CustomResourceDefinition API `versions` field can be used to support multiple versions of custom resources that you have developed. Versions can have different schemas, and conversion webhooks can convert custom resources between versi... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning.md | main | kubernetes | [
-0.04905594512820244,
0.06622117757797241,
0.0700240358710289,
-0.042149197310209274,
0.02570902369916439,
0.006303821224719286,
-0.06797690689563751,
-0.025089384987950325,
0.05272306129336357,
-0.0010842904448509216,
-0.03551851212978363,
-0.08041054010391235,
-0.016709113493561745,
-0.0... | 0.103379 |
to be used as an alias on the CLI and for display singular: crontab # kind is normally the PascalCased singular type. Your resource manifests use this. kind: CronTab # shortNames allow shorter string to match your resource on the CLI shortNames: - ct ``` {{% /tab %}} {{< /tabs >}} You can save the CustomResourceDefinit... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning.md | main | kubernetes | [
-0.003104043658822775,
0.02791956253349781,
0.05159759148955345,
-0.10239234566688538,
-0.07093390822410583,
0.051110394299030304,
-0.013108017854392529,
0.02381734922528267,
0.06141195073723793,
-0.01605459861457348,
-0.047435957938432693,
-0.06928735226392746,
-0.03080739825963974,
0.003... | 0.067512 |
v1alpha1 served: true storage: false # This indicates the v1alpha1 version of the custom resource is deprecated. # API requests to this version receive a warning header in the server response. deprecated: true # This overrides the default warning returned to API clients making v1alpha1 API requests. deprecationWarning:... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning.md | main | kubernetes | [
-0.04914543777704239,
0.019439131021499634,
0.004503170493990183,
-0.02052517794072628,
0.051384419202804565,
0.00495010893791914,
-0.04186568036675453,
-0.004113898146897554,
-0.03798069804906845,
0.006481050048023462,
0.004370832350105047,
-0.03243163973093033,
-0.010965680703520775,
0.0... | 0.098885 |
of these cases and to optimize conversion by the API server, the conversion requests may contain multiple objects in order to minimize the external calls. The webhook should perform these conversions independently. ### Write a conversion webhook server Please refer to the implementation of the [custom resource conversi... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning.md | main | kubernetes | [
-0.054725855588912964,
0.10219316929578781,
-0.022244349122047424,
-0.017032140865921974,
-0.023627277463674545,
-0.07883593440055847,
-0.05890023708343506,
-0.0009324880666099489,
0.09348801523447037,
0.041228242218494415,
-0.05480995029211044,
-0.10155678540468216,
0.016422422602772713,
... | 0.111524 |
are understood/preferred by the webhook. # The first version in the list understood by the API server is sent to the webhook. # The webhook must respond with a ConversionReview object in the same version it received. conversionReviewVersions: ["v1","v1beta1"] clientConfig: service: namespace: default name: example-conv... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning.md | main | kubernetes | [
-0.09674537926912308,
0.12352987378835678,
-0.08219189941883087,
-0.050232093781232834,
0.004649185109883547,
-0.04343966022133827,
-0.01905156672000885,
-0.009054679423570633,
0.01806218922138214,
0.002095042495056987,
-0.02316104806959629,
-0.18495063483715057,
0.059666506946086884,
-0.0... | 0.071537 |
may also be an IP address. Please note that using `localhost` or `127.0.0.1` as a `host` is risky unless you take great care to run this webhook on all hosts which run an apiserver which might need to make calls to this webhook. Such installations are likely to be non-portable or not readily run in a new cluster. The s... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning.md | main | kubernetes | [
-0.04794711992144585,
0.08676038682460785,
-0.058083996176719666,
-0.06969791650772095,
-0.04390217736363411,
-0.09113242477178574,
-0.08580754697322845,
-0.04623860865831375,
0.03087802603840828,
-0.0035122381523251534,
-0.0021715809125453234,
-0.11237995326519012,
0.04391026496887207,
-0... | 0.065359 |
be created. If an API server encounters a conversion webhook configuration that was previously created and does not support any of the `ConversionReview` versions the API server knows how to send, attempts to call to the webhook will fail. This example shows the data contained in an `ConversionReview` object for a requ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning.md | main | kubernetes | [
-0.09228035062551498,
0.06901421397924423,
-0.04282693937420845,
-0.04341505095362663,
-0.029128987342119217,
-0.04752075672149658,
-0.01121711265295744,
-0.04280256852507591,
0.020971018821001053,
0.026890942826867104,
-0.016487693414092064,
-0.12284788489341736,
0.011335293762385845,
-0.... | 0.098422 |
by the webhook. # metadata.labels and metadata.annotations fields may be changed by the webhook. # All other changes to metadata fields by the webhook are ignored. "convertedObjects": [ { "kind": "CronTab", "apiVersion": "example.com/v1", "metadata": { "creationTimestamp": "2019-09-04T14:03:02Z", "name": "local-crontab... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning.md | main | kubernetes | [
-0.041760411113500595,
0.10431013256311417,
-0.07624776661396027,
-0.04545772448182106,
0.029580285772681236,
-0.05433743819594383,
-0.04063650593161583,
-0.013588703237473965,
0.017751963809132576,
0.03714943677186966,
-0.019404541701078415,
-0.1612856239080429,
-0.028395721688866615,
-0.... | 0.045798 |
object. It is stored at version `v1beta1` 2. You add version `v1` to your CustomResourceDefinition and designate it as the storage version. Here the schemas for `v1` and `v1beta1` are identical, which is typically the case when promoting an API to stable in the Kubernetes ecosystem. 3. You read your object at version `... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning.md | main | kubernetes | [
-0.00608641654253006,
-0.009351040236651897,
0.042822450399398804,
-0.0001491423900006339,
-0.009119740687310696,
-0.010450853034853935,
-0.044612180441617966,
-0.03892926499247551,
0.10677166283130646,
0.02611883170902729,
0.012902987189590931,
-0.02610294707119465,
-0.016808990389108658,
... | 0.053919 |
This page shows how to install a [custom resource](/docs/concepts/extend-kubernetes/api-extension/custom-resources/) into the Kubernetes API by creating a [CustomResourceDefinition](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#customresourcedefinition-v1-apiextensions-k8s-io). ## {{% heading "prere... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
-0.02693169191479683,
-0.018264837563037872,
0.055912408977746964,
-0.012995753437280655,
-0.023807551711797714,
0.07703286409378052,
-0.050285324454307556,
-0.008377551101148129,
0.04651626944541931,
0.047743942588567734,
-0.04453856498003006,
-0.05966876074671745,
0.0034174202010035515,
... | 0.099373 |
raw YAML data: ```shell kubectl get ct -o yaml ``` You should see that it contains the custom `cronSpec` and `image` fields from the YAML you used to create it: ```yaml apiVersion: v1 items: - apiVersion: stable.example.com/v1 kind: CronTab metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"ap... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
0.001184918568469584,
0.027143601328134537,
0.008497790433466434,
-0.027016988024115562,
0.013136972673237324,
0.028782688081264496,
0.000506332260556519,
0.04058101400732994,
0.08353493362665176,
0.02342965640127659,
0.015574336051940918,
-0.11847458779811859,
-0.0214875265955925,
-0.0151... | 0.043127 |
"foo bar object" properties: foo: type: string pattern: "abc" bar: type: integer metadata: type: object properties: name: type: string pattern: "^a" anyOf: - properties: bar: minimum: 42 required: ["bar"] ``` Violations of the structural schema rules are reported in the `NonStructural` condition in the CustomResourceDe... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
-0.028562873601913452,
0.02820972353219986,
0.07101988047361374,
-0.018549898639321327,
-0.04854719713330269,
0.015342725440859795,
0.00043613454909063876,
-0.08810663223266602,
0.08408383280038834,
0.023487752303481102,
-0.00959874503314495,
-0.11757046729326248,
0.030713649466633797,
0.0... | 0.044846 |
more ... ``` With one of those specification, both an integer and a string validate. In [Validation Schema Publishing](#publish-validation-schema-in-openapi), `x-kubernetes-int-or-string: true` is unfolded to one of the two patterns shown above. ### RawExtension RawExtensions (as in [`runtime.RawExtension`](/docs/refer... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
-0.0014273443957790732,
0.05306338518857956,
0.04613708332180977,
0.01463919784873724,
0.037799008190631866,
-0.0003692095051519573,
-0.037043649703264236,
-0.02414538711309433,
0.057944297790527344,
0.013636461459100246,
-0.02970699779689312,
-0.09757068008184433,
0.01815095543861389,
0.0... | 0.096978 |
metadata: name: crontabs.stable.example.com spec: group: stable.example.com versions: - name: v1 served: true storage: true schema: # openAPIV3Schema is the schema for validating custom objects. openAPIV3Schema: type: object properties: spec: type: object properties: cronSpec: type: string pattern: '^(\d+|\\*)(/\d+)?(\... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
-0.00846042949706316,
0.06310444325208664,
0.019531458616256714,
-0.050193484872579575,
-0.048033613711595535,
0.0044137355871498585,
0.05252186954021454,
0.005205222871154547,
0.06577970832586288,
0.014416356571018696,
-0.02336234599351883,
-0.15232212841510773,
-0.008774329908192158,
0.0... | 0.109512 |
from changing the list type of a subschema will not be ratcheted. For example adding `set` onto a list with duplicates will always result in an error. - `x-kubernetes-list-map-keys` Errors arising from changing the map keys of a list schema will not be ratcheted. - `required` Errors arising from changing the list of re... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
-0.030114004388451576,
0.02294136770069599,
0.0658814087510109,
-0.010846720077097416,
-0.031174631789326668,
-0.014632108621299267,
0.023809164762496948,
-0.03297656029462814,
0.01704990118741989,
0.04118115082383156,
-0.014063762500882149,
-0.019649563357234,
-0.025670332834124565,
-0.00... | 0.083468 |
error: ```none Invalid value: apiextensions.ValidationRule{Rule:"has(self)", Message:""}: compilation failed: ERROR: :1:4: invalid argument to has() macro ``` Validation Rules Examples: | Rule | Purpose | | ---------------- | ------------ | | `self.minReplicas <= self.replicas && self.replicas <= self.maxReplicas` | Va... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
-0.04235612601041794,
0.023544378578662872,
0.03238464891910553,
-0.03841580078005791,
0.02817809022963047,
-0.045029133558273315,
0.010707782581448555,
-0.0027350913733243942,
-0.026438429951667786,
-0.018924279138445854,
-0.005483737215399742,
-0.06133092939853668,
0.0946483165025711,
0.... | 0.039307 |
type: object properties: # ... foo: type: array x-kubernetes-validations: - rule: "size(self) == 1" items: type: string ``` - If the Rule is scoped to a scalar, `self` is bound to the scalar value. ```yaml # ... openAPIV3Schema: type: object properties: spec: type: object properties: # ... foo: type: integer x-kubernet... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
0.06226326525211334,
0.0906531810760498,
0.023868419229984283,
-0.031979236751794815,
-0.00024494374520145357,
-0.05197331681847572,
0.07782581448554993,
0.023059671744704247,
0.0017152767395600677,
0.023736774921417236,
-0.0194495040923357,
-0.056545957922935486,
-0.01777602732181549,
0.0... | 0.030308 |
check the type | | 'array | list | | 'array' with x-kubernetes-list-type=map | list with map based Equality & unique key guarantees | | 'array' with x-kubernetes-list-type=set | list with set based Equality & unique entry guarantees | | 'boolean' | boolean | | 'number' (all formats) | double | | 'integer' (all formats)... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
-0.0003698513319250196,
-0.009188844822347164,
0.03478160873055458,
-0.09365005046129227,
-0.024425849318504333,
0.031178483739495277,
0.05378665030002594,
-0.018133340403437614,
0.06270882487297058,
-0.022737370803952217,
0.007015529554337263,
-0.1209389790892601,
0.024362897500395775,
-0... | 0.015873 |
be default to wherever `self` scoped. With `fieldPath` specified, the returned error will have `fieldPath` properly refer to the location of field `x`. The `fieldPath` value must be a relative JSON path that is scoped to the location of this x-kubernetes-validations extension in the schema. Additionally, it should refe... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
0.020825430750846863,
0.03440748155117035,
0.0443514920771122,
-0.025519993156194687,
0.018386945128440857,
-0.00404035858809948,
0.019941898062825203,
-0.005444732028990984,
0.016028814017772675,
-0.03189144283533096,
-0.01584225706756115,
-0.08335140347480774,
0.036548931151628494,
0.073... | 0.039822 |
never applied to custom resource creation. When placed on an optional field, a transition rule will not apply to update operations that set or unset the field. - The path to the schema node being validated by a transition rule must resolve to a node that is comparable between the old object and the new object. For exam... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
-0.032312847673892975,
0.009811889380216599,
0.051021967083215714,
-0.012978835962712765,
-0.0004931987496092916,
0.009178709238767624,
0.015546159818768501,
-0.055738553404808044,
0.059017788618803024,
0.006587051786482334,
0.00046817277325317264,
-0.07839778810739517,
0.008341568522155285,... | 0.091756 |
with one rule: ```yaml openAPIV3Schema: type: object properties: foo: type: array items: type: string x-kubernetes-validations: - rule: "self.all(x, x.contains('a string'))" ``` then the API server rejects this rule on validation budget grounds with error: ``` spec.validation.openAPIV3Schema.properties[spec].properties... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
0.02410576492547989,
0.08534697443246841,
0.07442550361156464,
-0.008124555461108685,
0.021404314786195755,
-0.06971901655197144,
0.03179817274212837,
-0.014891608618199825,
0.10107117891311646,
0.0413675382733345,
-0.04012720286846161,
-0.11325938254594803,
0.031006332486867905,
-0.025313... | 0.061733 |
version defaults, \* after mutating admission plugins with non-empty patches using the admission webhook object version defaults. Defaults applied when reading data from etcd are not automatically written back to etcd. An update request via the API is required to persist those defaults back into etcd. Default values fo... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
-0.019066933542490005,
0.07235849648714066,
0.03458463400602341,
-0.031120654195547104,
0.011199005879461765,
-0.017645541578531265,
-0.04985485225915909,
-0.030732817947864532,
-0.017935538664460182,
0.04848458245396614,
0.048869602382183075,
-0.063224196434021,
0.004626201465725899,
0.02... | 0.076387 |
a CustomResourceDefinition. The following example adds the `Spec`, `Replicas`, and `Age` columns. Save the CustomResourceDefinition to `resourcedefinition.yaml`: ```yaml apiVersion: apiextensions.k8s.io/v1 kind: CustomResourceDefinition metadata: name: crontabs.stable.example.com spec: group: stable.example.com scope: ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
-0.10368797928094864,
0.0008747904794290662,
-0.06565549224615097,
-0.0011534788645803928,
-0.011532776057720184,
0.024698380380868912,
-0.014290466904640198,
0.0374472476541996,
-0.004795474465936422,
0.024502528831362724,
0.013096862472593784,
-0.08345316350460052,
0.010193582624197006,
... | 0.109303 |
a `color` of `blue`): ```shell kubectl get shirts.stable.example.com --field-selector spec.color=blue ``` Should output: ``` NAME COLOR SIZE example1 blue S example2 blue M ``` Get only resources with a `color` of `green` and a `size` of `M`: ```shell kubectl get shirts.stable.example.com --field-selector spec.color=gr... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
-0.007283746264874935,
0.07394543290138245,
-0.02668697200715542,
0.04429296776652336,
0.020220700651407242,
0.006595316343009472,
0.02705688215792179,
0.025984318926930428,
0.018845301121473312,
-0.008832219056785107,
-0.00837252102792263,
-0.109954833984375,
0.03724338859319687,
-0.02886... | 0.114472 |
labelSelector: type: string # subresources describes the subresources for custom resources. subresources: # status enables the status subresource. status: {} # scale enables the scale subresource. scale: # specReplicasPath defines the JSONPath inside of a custom resource that corresponds to Scale.Spec.Replicas. specRep... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md | main | kubernetes | [
-0.04600369185209274,
0.015657803043723106,
-0.04335582256317139,
0.027560006827116013,
-0.062361620366573334,
0.026754964143037796,
0.007679299917072058,
0.03357888013124466,
0.02141195721924305,
-0.011447558179497719,
0.017160683870315552,
-0.11095597594976425,
-0.0301967803388834,
0.018... | 0.150406 |
This page shows how to run automated tasks using Kubernetes {{< glossary\_tooltip text="CronJob" term\_id="cronjob" >}} object. ## {{% heading "prerequisites" %}} \* {{< include "task-tutorial-prereqs.md" >}} ## Creating a CronJob {#creating-a-cron-job} Cron jobs require a config file. Here is a manifest for a CronJob ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/automated-tasks-with-cron-jobs.md | main | kubernetes | [
-0.07088340818881989,
0.011758101172745228,
0.029030900448560715,
-0.03789720684289932,
-0.08187806606292725,
-0.0007017036550678313,
0.004928357899188995,
0.0006523823831230402,
0.015590683557093143,
0.06235862895846367,
-0.021883845329284668,
-0.129948690533638,
-0.013528560288250446,
0.... | 0.090116 |
{{< feature-state feature\_gate\_name="JobPodFailurePolicy" >}} This document shows you how to use the [Pod failure policy](/docs/concepts/workloads/controllers/job#pod-failure-policy), in combination with the default [Pod backoff failure policy](/docs/concepts/workloads/controllers/job#pod-backoff-failure-policy), to ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/pod-failure-policy.md | main | kubernetes | [
-0.007593181915581226,
0.055311642587184906,
0.06809110194444656,
0.062442846596241,
0.04828517884016037,
-0.026388706639409065,
0.011223026551306248,
-0.01448974758386612,
-0.07848610728979111,
0.01998170278966427,
-0.013231071643531322,
0.03998906910419464,
0.005724876653403044,
-0.00246... | 0.127289 |
Job is not incremented: ```sh kubectl get jobs -l job-name=job-pod-failure-policy-ignore -o yaml ``` 1. Uncordon the node: ```sh kubectl uncordon nodes/$nodeName ``` The Job resumes and succeeds. For comparison, if the Pod failure policy was disabled the Pod disruption would result in terminating the entire Job (as the... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/pod-failure-policy.md | main | kubernetes | [
-0.0431661382317543,
-0.004098234698176384,
0.07374393939971924,
0.03669429197907448,
0.051684919744729996,
-0.022736605256795883,
-0.0349910631775856,
-0.07681471854448318,
0.015775464475154877,
0.06287764757871628,
0.03169183060526848,
0.015634773299098015,
-0.009172895923256874,
-0.0482... | 0.154046 |
for the Job. You can do that by running: ```shell kubectl get pods -l job-name=job-backoff-limit-per-index-failindex -o yaml ``` You will see output similar to this: ```none NAME READY STATUS RESTARTS AGE job-backoff-limit-per-index-failindex-0-4g4cm 0/1 Error 0 4s job-backoff-limit-per-index-failindex-0-fkdzq 0/1 Erro... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/pod-failure-policy.md | main | kubernetes | [
0.03608294948935509,
-0.024103455245494843,
0.010706596076488495,
0.04424130916595459,
-0.018396874889731407,
0.007882446981966496,
-0.035880882292985916,
-0.042236484587192535,
0.008206703700125217,
0.013519467785954475,
-0.0035079289227724075,
-0.024604860693216324,
0.0020270557142794132,
... | 0.154055 |
In this example, you will run a Kubernetes Job with multiple parallel worker processes. In this example, as each pod is created, it picks up one unit of work from a task queue, completes it, deletes it from the queue, and exits. Here is an overview of the steps in this example: 1. \*\*Start a message queue service.\*\*... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/coarse-parallel-processing-work-queue.md | main | kubernetes | [
0.00443373853340745,
-0.021364448592066765,
0.0007112135645002127,
0.04455914348363876,
-0.08175947517156601,
-0.033306438475847244,
0.0612042099237442,
-0.061352670192718506,
0.03741424158215523,
0.07034876197576523,
-0.0006824056035839021,
0.0034325048327445984,
0.02359357662498951,
0.00... | 0.196743 |
the Pod # In the next line, rabbitmq-service is the hostname where the rabbitmq-service # can be reached. 5672 is the standard port for rabbitmq. export BROKER\_URL=amqp://guest:guest@rabbitmq-service:5672 # If you could not resolve "rabbitmq-service" in the previous step, # then use this command instead: BROKER\_URL=a... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/coarse-parallel-processing-work-queue.md | main | kubernetes | [
0.10263903439044952,
0.015141753479838371,
-0.01852455362677574,
0.05626964941620827,
-0.12238644808530807,
-0.02723129279911518,
0.05673953890800476,
-0.047768279910087585,
0.014937249012291431,
0.09354732185602188,
-0.03647952526807785,
-0.044973231852054596,
0.0407426580786705,
0.022874... | 0.031216 |
%}} In this example, each pod works on one item from the queue and then exits. So, the completion count of the Job corresponds to the number of work items done. That is why the example manifest has `.spec.completions` set to `8`. ## Running the Job Now, run the Job: ```shell # this assumes you downloaded and then edite... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/coarse-parallel-processing-work-queue.md | main | kubernetes | [
0.01638508401811123,
-0.002363424049690366,
0.0014420348452404141,
-0.016611702740192413,
-0.021001022309064865,
-0.03233864903450012,
0.03559894487261772,
-0.05563969910144806,
0.10430429875850677,
0.020097116008400917,
0.003013439243659377,
-0.06789765506982803,
-0.02011847123503685,
-0.... | 0.158635 |
container is killed in between the time that the message is acknowledged by the `amqp-consume` command and the time that the container exits with success, or if the node crashes before the kubelet is able to post the success of the pod back to the API server, then the Job will not appear to be complete, even though all... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/coarse-parallel-processing-work-queue.md | main | kubernetes | [
0.021474923938512802,
0.06718718260526657,
0.042264025658369064,
0.03448248282074928,
-0.00028650229796767235,
-0.05551041290163994,
0.009118716232478619,
-0.06799077242612839,
0.08951221406459808,
0.014069278724491596,
-0.047616180032491684,
-0.038315050303936005,
-0.01589878462255001,
-0... | 0.134426 |
In this example, you will run a Kubernetes Job that runs multiple parallel tasks as worker processes, each running as a separate Pod. In this example, as each pod is created, it picks up one unit of work from a task queue, processes it, and repeats until the end of the queue is reached. Here is an overview of the steps... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/fine-parallel-processing-work-queue.md | main | kubernetes | [
-0.029509978368878365,
-0.02279595099389553,
-0.007850894704461098,
0.03098149038851261,
-0.10928931832313538,
-0.04495891183614731,
0.034495677798986435,
-0.040813516825437546,
0.08075739443302155,
0.06489881128072739,
-0.042408253997564316,
-0.007297573611140251,
0.02992803417146206,
-0.... | 0.223382 |
DNS setup correctly, you may need to change the first step of the above block to `redis-cli -h $REDIS\_SERVICE\_HOST`. ## Create a container image {#create-an-image} Now you are ready to create an image that will process the work in that queue. You're going to use a Python worker program with a Redis client to read the... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/fine-parallel-processing-work-queue.md | main | kubernetes | [
-0.05355029180645943,
-0.022357916459441185,
-0.053157415241003036,
-0.0034472281113266945,
-0.03811004385352135,
-0.13078844547271729,
0.042928315699100494,
-0.03870806097984314,
0.006298982072621584,
-0.004191124811768532,
-0.05636279657483101,
-0.0005020871758460999,
0.014540047384798527,... | 0.098759 |
a continuous stream of background processing work to run, then consider running your background workers with a ReplicaSet instead, and consider running a background processing library such as [https://github.com/resque/resque](https://github.com/resque/resque). | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/fine-parallel-processing-work-queue.md | main | kubernetes | [
-0.017210373654961586,
-0.056257352232933044,
-0.02903030440211296,
-0.021780312061309814,
0.04644493758678436,
-0.1281987726688385,
-0.0673576220870018,
-0.0654466450214386,
0.00462624104693532,
0.023776108399033546,
-0.05706057325005531,
0.0039351871237158775,
-0.021904943510890007,
-0.0... | 0.079302 |
{{< feature-state for\_k8s\_version="v1.24" state="stable" >}} In this example, you will run a Kubernetes Job that uses multiple parallel worker processes. Each worker is a different container running in its own Pod. The Pods have an \_index number\_ that the control plane sets automatically, which allows each Pod to i... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/indexed-parallel-processing-static.md | main | kubernetes | [
-0.03391454741358757,
0.031979456543922424,
0.049510784447193146,
0.027528883889317513,
-0.030323421582579613,
0.006289327517151833,
0.05699162557721138,
-0.03777977451682091,
0.049311891198158264,
0.016361990943551064,
-0.07098173350095749,
-0.06307084858417511,
-0.04442468658089638,
-0.0... | 0.191235 |
Job Now run the Job: ```shell # This uses the first approach (relying on $JOB\_COMPLETION\_INDEX) kubectl apply -f https://kubernetes.io/examples/application/job/indexed-job.yaml ``` When you create this Job, the control plane creates a series of Pods, one for each index you specified. The value of `.spec.parallelism` ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/indexed-parallel-processing-static.md | main | kubernetes | [
0.004866140428930521,
0.0063950843177735806,
0.001953974599018693,
0.01972482167184353,
-0.02396492101252079,
-0.04188951477408409,
-0.0420728363096714,
-0.03266998380422592,
0.08992515504360199,
0.0425008200109005,
0.01076466217637062,
-0.05090828239917755,
-0.018632065504789352,
-0.09490... | 0.140839 |
In this example, you will run a Job in [Indexed completion mode](/blog/2021/04/19/introducing-indexed-jobs/) configured such that the pods created by the Job can communicate with each other using pod hostnames rather than pod IP addresses. Pods within a Job might need to communicate among themselves. The user workload ... | https://github.com/kubernetes/website/blob/main//content/en/docs/tasks/job/job-with-pod-to-pod-communication.md | main | kubernetes | [
-0.0026576260570436716,
0.0051438044756650925,
0.06557109206914902,
0.03152962774038315,
-0.08953311294317245,
-0.013136805966496468,
-0.008333651348948479,
-0.07497153431177139,
0.051522914320230484,
0.028179815039038658,
-0.10847517848014832,
-0.013484456576406956,
-0.011546852067112923,
... | 0.160776 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.