content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 49
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
0 34s ``` At this point, it should be clear that the resources users create in one namespace are hidden from the other namespace. As the policy support in Kubernetes evolves, we will extend this scenario to show how you can provide different authorization rules for each namespace. ## Understanding the motivation for us... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/namespaces.md | main | kubernetes | [
-0.007306437939405441,
-0.03304173797369003,
0.008298144675791264,
-0.016821343451738358,
-0.04858318343758583,
-0.02220364287495613,
0.10821493715047836,
-0.0785524919629097,
0.06004444137215614,
0.02629234455525875,
-0.056987084448337555,
-0.10892728716135025,
0.05389914661645889,
0.0546... | 0.152745 |
This page shows how to configure and enable the `ip-masq-agent`. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## IP Masquerade Agent User Guide The `ip-masq-agent` configures iptables rules to hide a pod's IP address behind the cluster node's IP address. This is ty... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/ip-masq-agent.md | main | kubernetes | [
0.018076092004776,
0.022414766252040863,
-0.023113375529646873,
0.0032336495351046324,
0.009212031960487366,
-0.01891171932220459,
-0.0058429064229130745,
-0.04589315503835678,
-0.013715947978198528,
-0.040967073291540146,
0.024772852659225464,
-0.004572758451104164,
0.06053878739476204,
-... | 0.192117 |
the default set of rules that are applied by the ip-masq-agent: ```shell iptables -t nat -L IP-MASQ-AGENT ``` ```none target prot opt source destination RETURN all -- anywhere 169.254.0.0/16 /\* ip-masq-agent: cluster-local traffic should not be subject to MASQUERADE \*/ ADDRTYPE match dst-type !LOCAL RETURN all -- any... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/ip-masq-agent.md | main | kubernetes | [
0.06217867136001587,
0.0221871230751276,
-0.056550104171037674,
-0.025721438229084015,
0.020978355780243874,
-0.0006026214105077088,
-0.036489684134721756,
0.0037329373881220818,
-0.04751739650964737,
0.004692398011684418,
0.021265337243676186,
-0.08615292608737946,
-0.013042539358139038,
... | 0.06795 |
{{< feature-state for\_k8s\_version="v1.18" state="stable" >}} This page provides an overview of NodeLocal DNSCache feature in Kubernetes. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## Introduction NodeLocal DNSCache improves Cluster DNS performance by running a ... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/nodelocaldns.md | main | kubernetes | [
0.0033059814013540745,
0.004142974503338337,
0.08375398814678192,
-0.008584314025938511,
-0.04438275843858719,
-0.03144557401537895,
-0.022269755601882935,
-0.04764125868678093,
0.055300045758485794,
0.06055906414985657,
-0.06404446810483932,
0.006095669232308865,
-0.041047126054763794,
-0... | 0.208145 |
so pods can look up DNS records using either IP address. \* If kube-proxy is running in IPVS mode: ``` bash sed -i "s/\_\_PILLAR\_\_LOCAL\_\_DNS\_\_/$localdns/g; s/\_\_PILLAR\_\_DNS\_\_DOMAIN\_\_/$domain/g; s/,\_\_PILLAR\_\_DNS\_\_SERVER\_\_//g; s/\_\_PILLAR\_\_CLUSTER\_\_DNS\_\_/$kubedns/g" nodelocaldns.yaml ``` In th... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/nodelocaldns.md | main | kubernetes | [
-0.012763170525431633,
0.0025981676299124956,
0.06954342126846313,
-0.041094690561294556,
-0.08596862107515335,
-0.04744785279035568,
-0.04746999219059944,
-0.07031875848770142,
0.08950094878673553,
0.033882029354572296,
-0.04848315194249153,
-0.025761393830180168,
-0.029175931587815285,
-... | 0.082326 |
{{< feature-state for\_k8s\_version="v1.22" state="alpha" >}} This document describes how to run Kubernetes Node components such as kubelet, CRI, OCI, and CNI without root privileges, by using a {{< glossary\_tooltip text="user namespace" term\_id="userns" >}}. This technique is also known as \_rootless mode\_. {{< not... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubelet-in-userns.md | main | kubernetes | [
0.03452172502875328,
0.003807960543781519,
0.03706374391913414,
-0.01801004819571972,
-0.049139540642499924,
-0.03513817489147186,
0.00440232316032052,
0.03813115134835243,
-0.008038684725761414,
0.02265402115881443,
-0.010517152026295662,
-0.07404216378927231,
0.003321391763165593,
0.0200... | 0.118074 |
also need to have a writable cgroup tree with cgroup v2. {{< note >}} Kubernetes support for running Node components in user namespaces requires cgroup v2. Cgroup v1 is not supported. {{< /note >}} If you are trying to run Kubernetes in Rootless Docker/Podman or LXC/LXD on a systemd-based host, you are all set. Otherwi... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubelet-in-userns.md | main | kubernetes | [
0.03792884200811386,
-0.02202708274126053,
-0.03008219599723816,
-0.027038905769586563,
-0.0663912370800972,
0.0325617678463459,
-0.03924580290913582,
0.022171061486005783,
0.04093156382441521,
0.03946416452527046,
-0.03295949473977089,
-0.0843418538570404,
0.01497971173375845,
0.023312250... | 0.009945 |
is enabled, the kubelet ignores errors that may happen during setting the following sysctl values on the node. - `vm.overcommit\_memory` - `vm.panic\_on\_oom` - `kernel.panic` - `kernel.panic\_on\_oops` - `kernel.keys.root\_maxkeys` - `kernel.keys.root\_maxbytes`. Within a user namespace, the kubelet also ignores any e... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubelet-in-userns.md | main | kubernetes | [
0.03347622975707054,
-0.012976105324923992,
0.009372526779770851,
-0.013352515175938606,
-0.050366465002298355,
-0.03417054936289787,
-0.026897558942437172,
0.05574384704232216,
0.06455185264348984,
0.00011400190851418301,
-0.01175200380384922,
-0.03579483553767204,
0.0032445022370666265,
... | 0.132849 |
{{< glossary\_definition term\_id="etcd" length="all" prepend="etcd is a ">}} ## {{% heading "prerequisites" %}} Before you follow steps in this page to deploy, manage, back up or restore etcd, you need to understand the typical expectations for operating an etcd cluster. Refer to the [etcd documentation](https://etcd.... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md | main | kubernetes | [
-0.04292125254869461,
0.008486809208989143,
0.05360084027051926,
-0.048226505517959595,
0.016545327380299568,
-0.00924056675285101,
-0.0932416319847107,
-0.04884140565991402,
-0.07684127986431122,
0.02159029245376587,
0.029939142987132072,
0.0377216711640358,
0.045328136533498764,
-0.04519... | 0.09827 |
`http://$IP2:2379`, `http://$IP3:2379`, `http://$IP4:2379`, and `http://$IP5:2379`. To start a Kubernetes API server: 1. Run the following: ```shell etcd --listen-client-urls=http://$IP1:2379,http://$IP2:2379,http://$IP3:2379,http://$IP4:2379,http://$IP5:2379 --advertise-client-urls=http://$IP1:2379,http://$IP2:2379,ht... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md | main | kubernetes | [
0.00304598780348897,
0.014244203455746174,
0.035510819405317307,
-0.09643914550542831,
-0.05841398984193802,
-0.011983511969447136,
-0.07552361488342285,
-0.07981198281049728,
0.0923653095960617,
0.05136648938059807,
-0.024745848029851913,
-0.04884133115410805,
-0.027004389092326164,
-0.01... | 0.004499 |
member3, http://10.0.0.3:2380, http://10.0.0.3:2379 ``` 1. Do either of the following: 1. If each Kubernetes API server is configured to communicate with all etcd members, remove the failed member from the `--etcd-servers` flag, then restart each Kubernetes API server. 1. If each Kubernetes API server communicates with... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md | main | kubernetes | [
-0.02353779785335064,
0.04439929872751236,
0.11914072930812836,
-0.054456692188978195,
0.05852004885673523,
0.0032547051087021828,
-0.05929087847471237,
-0.04822478070855141,
0.05698048323392868,
0.07995440065860748,
0.002338592428714037,
-0.02209615334868431,
-0.005587359890341759,
0.0035... | 0.014506 |
a snapshot: ```shell export ETCDCTL\_API=3 etcdctl --write-out=table snapshot status snapshot.db ``` This should generate an output resembling the example provided below: ```console Deprecated: Use `etcdutl snapshot status` instead. +----------+----------+------------+------------+ | HASH | REVISION | TOTAL KEYS | TOTA... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md | main | kubernetes | [
-0.02256990224123001,
0.07110727578401566,
-0.06661000847816467,
-0.0105771254748106,
-0.028410710394382477,
-0.04660503938794136,
-0.05004672706127167,
0.03014249913394451,
-0.004624990280717611,
0.038690853863954544,
0.023045353591442108,
-0.06796307116746902,
0.08975160121917725,
-0.106... | -0.039989 |
the same folder as before, delete it and stop the etcd process before restoring the cluster. Otherwise, change etcd configuration and restart the etcd process after restoration to have it use the new data directory: first change `/etc/kubernetes/manifests/etcd.yaml`'s `volumes.hostPath.path` for `name: etcd-data` to ``... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md | main | kubernetes | [
-0.009695049375295639,
0.010170520283281803,
0.09450901299715042,
-0.06785744428634644,
-0.022980544716119766,
0.029674610123038292,
-0.0710354819893837,
-0.09017983078956604,
0.07445038855075836,
-0.010360302403569221,
0.017969666048884392,
0.055931344628334045,
0.024856023490428925,
-0.0... | 0.040164 |
This page explains how to configure your DNS {{< glossary\_tooltip text="Pod(s)" term\_id="pod" >}} and customize the DNS resolution process in your cluster. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} Your cluster must be running the CoreDNS add-on. {{% version-check %}} ## Introducti... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md | main | kubernetes | [
-0.05804869905114174,
-0.05015949159860611,
0.08200579136610031,
-0.043363191187381744,
-0.11108485609292984,
-0.008168376050889492,
-0.04025694727897644,
-0.059979528188705444,
0.04687478393316269,
0.05780224874615669,
-0.045711491256952286,
-0.0704943910241127,
-0.03372334688901901,
-0.0... | 0.120153 |
the maximum is capped at 3600 seconds. Setting TTL to 0 will prevent records from being cached. - The `pods insecure` option is provided for backward compatibility with `kube-dns`. - You can use the `pods verified` option, which returns an A record only if there exists a pod in the same namespace with a matching IP. - ... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md | main | kubernetes | [
-0.024203432723879814,
-0.0035770023241639137,
0.019448168575763702,
0.005346985068172216,
-0.06145944818854332,
-0.06758057326078415,
-0.04955601319670677,
-0.0390300415456295,
0.09116021543741226,
0.044835470616817474,
-0.013054396957159042,
-0.014317670837044716,
-0.008686846122145653,
... | 0.199136 |
{{< feature-state feature\_gate\_name="MemoryManager" >}} The Kubernetes \*Memory Manager\* enables the feature of guaranteed memory (and hugepages) allocation for pods in the `Guaranteed` {{< glossary\_tooltip text="QoS class" term\_id="qos-class" >}}. The Memory Manager employs a hint generation protocol to yield the... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/memory-manager.md | main | kubernetes | [
0.026834797114133835,
0.02987411990761757,
0.017832688987255096,
0.0333281010389328,
-0.02126353606581688,
0.00014580239076167345,
0.04419687017798424,
-0.015904810279607773,
0.06762071698904037,
0.0647849515080452,
-0.00522532919421792,
-0.01451780553907156,
0.0003206431574653834,
-0.0333... | 0.270285 |
memory manager provides three policies. You can select a policy via the `memoryManagerPolicy` configuration field in the kubelet configuration; the values available in Kubernetes {{< skew currentVersion >}} are: \* [`None`](#policy-none) (default) \* [`Static`](#policy-static) (Linux only) \* [`BestEffort`](#policy-bes... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/memory-manager.md | main | kubernetes | [
0.04354329779744148,
0.019282473251223564,
-0.029259206727147102,
0.021984878927469254,
-0.03498983755707741,
0.04873554781079292,
0.019171668216586113,
-0.004589182790368795,
0.08806265145540237,
0.012610480189323425,
0.008225378580391407,
-0.030620258301496506,
-0.012346357107162476,
-0.... | 0.237992 |
will need to specify `reservedMemory` for at least one NUMA node. In fact, the `evictionHard` threshold value is equal to `100Mi` by default, so if you use the `Static` policy, specifying `reservedMemory` is obligatory. ### Memory manager reserved memory syntax {#reserved-memory-syntax} Here are some examples of how to... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/memory-manager.md | main | kubernetes | [
0.06514438986778259,
0.021315032616257668,
-0.018420731648802757,
-0.003066999139264226,
-0.05474165454506874,
0.030237043276429176,
-0.01270468533039093,
0.026799893006682396,
0.05873383209109306,
0.03541982173919678,
0.0003461419546511024,
-0.12242085486650467,
-0.002250530757009983,
-0.... | 0.208929 |
the `Guaranteed` QoS class, when `requests` are equal to `limits`: ```yaml spec: containers: - name: nginx image: nginx resources: limits: memory: "200Mi" cpu: "2" example.com/device: "1" requests: memory: "200Mi" cpu: "2" example.com/device: "1" ``` Also, a pod sharing CPU(s) runs in the `Guaranteed` QoS class, when `... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/memory-manager.md | main | kubernetes | [
0.00032369946711696684,
0.05653037875890732,
-0.004025781527161598,
0.013361824676394463,
-0.035684600472450256,
-0.0655980110168457,
0.03427630290389061,
-0.01926509290933609,
0.05898198485374451,
0.015515470877289772,
-0.025991316884756088,
0.01943495124578476,
-0.001335766981355846,
0.0... | 0.137973 |
{{< feature-state feature\_gate\_name="EventedPLEG" >}} This page shows how to migrate nodes to use event based updates for container status. The event-based implementation reduces node resource consumption by the kubelet, compared to the legacy approach that relies on polling. You may know this feature as \_evented Po... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/switch-to-evented-pleg.md | main | kubernetes | [
0.03155123442411423,
0.021424174308776855,
0.09517206251621246,
0.0129478108137846,
0.012964044697582722,
-0.01409381628036499,
-0.014556709676980972,
-0.04234766587615013,
0.07048755884170532,
0.03440091758966446,
-0.059133030474185944,
-0.03836164250969887,
-0.059634651988744736,
-0.0734... | 0.159003 |
{{< feature-state state="beta" for\_k8s\_version="v1.26" >}} ## {{% heading "prerequisites" %}} You will need to have the following tools installed: - `cosign` ([install guide](https://docs.sigstore.dev/cosign/system\_config/installation/)) - `curl` (often provided by your operating system) - `jq` ([download jq](https:... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/verify-signed-artifacts.md | main | kubernetes | [
0.004346873611211777,
0.08288441598415375,
0.03389689326286316,
-0.07283411175012589,
-0.0375630147755146,
-0.0011605563340708613,
-0.016909433528780937,
0.00164466118440032,
0.0006235211621969938,
0.003895936766639352,
0.008128619752824306,
-0.10356730967760086,
0.0006700397934764624,
-0.... | 0.130115 |
{{< feature-state for\_k8s\_version="v1.11" state="beta" >}} {{< glossary\_definition term\_id="cloud-controller-manager" length="all" prepend="The cloud-controller-manager is">}} ## Background Since cloud providers develop and release at a different pace compared to the Kubernetes project, abstracting the provider-spe... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/developing-cloud-controller-manager.md | main | kubernetes | [
-0.03122011013329029,
-0.02861716039478779,
0.05258884280920029,
0.008661461994051933,
-0.021047430112957954,
0.06734944880008698,
0.009069206193089485,
-0.02377483621239662,
0.046548280864953995,
0.10192269831895828,
0.03528384864330292,
-0.035359933972358704,
-0.008055527694523335,
-0.03... | 0.061161 |
This page provides hints on diagnosing DNS problems. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} Your cluster must be configured to use the CoreDNS {{< glossary\_tooltip text="addon" term\_id="addons" >}} or its precursor, kube-dns. {{% version-check %}} ### Create a simple Pod to use ... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md | main | kubernetes | [
-0.05325407162308693,
-0.04919232055544853,
0.06883932650089264,
-0.036013539880514145,
-0.11132055521011353,
-0.03205607458949089,
-0.047005657106637955,
-0.05105585232377052,
0.03533278405666351,
0.06402476131916046,
-0.028741229325532913,
-0.07292710989713669,
-0.04680640622973442,
-0.0... | 0.111212 |
you have created the Service or in the case it should be created by default but it does not appear, see [debugging Services](/docs/tasks/debug/debug-application/debug-service/) for more information. ### Are DNS endpoints exposed? You can verify that DNS endpoints are exposed by using the `kubectl get endpointslice` com... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md | main | kubernetes | [
-0.010790351778268814,
-0.03823577240109444,
0.02512575313448906,
-0.05937168747186661,
-0.0845758244395256,
-0.028799423947930336,
-0.033246759325265884,
-0.03245871886610985,
0.10709012299776077,
0.0694773718714714,
-0.035553526133298874,
-0.09434447437524796,
-0.02949502505362034,
-0.01... | 0.119867 |
`/etc/resolv.conf` with a stub file that can cause a fatal forwarding loop when resolving names in upstream servers. This can be fixed manually by using kubelet's `--resolv-conf` flag to point to the correct `resolv.conf` (With `systemd-resolved`, this is `/run/systemd/resolve/resolv.conf`). kubeadm automatically detec... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md | main | kubernetes | [
-0.0191262885928154,
-0.03971335291862488,
0.06308503448963165,
-0.032713647931814194,
-0.0919799953699112,
-0.013210819102823734,
-0.10352060198783875,
-0.01909574121236801,
0.08187054097652435,
0.017474371939897537,
-0.07559532672166824,
-0.02087312564253807,
-0.03176078945398331,
-0.077... | 0.074455 |
{{< feature-state for\_k8s\_version="v1.26" state="stable" >}} Starting from Kubernetes v1.20, the kubelet can dynamically retrieve credentials for a container image registry using exec plugins. The kubelet and the exec plugin communicate through stdio (stdin, stdout, and stderr) using Kubernetes versioned APIs. These ... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubelet-credential-provider.md | main | kubernetes | [
-0.03831355646252632,
0.036674801260232925,
0.013564636930823326,
-0.04223326966166496,
-0.09585821628570557,
0.018561866134405136,
-0.007624347694218159,
0.04077541455626488,
0.08664211630821228,
0.010099513456225395,
-0.02298697642982006,
-0.10032269358634949,
0.015665091574192047,
-0.00... | 0.08625 |
using if you are using the [ECR-based plugin](https://github.com/kubernetes/cloud-provider-aws/tree/master/cmd/ecr-credential-provider): ```yaml apiVersion: kubelet.config.k8s.io/v1 kind: CredentialProviderConfig # providers is a list of credential provider helper plugins that will be enabled by the kubelet. # Multiple... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubelet-credential-provider.md | main | kubernetes | [
-0.022151164710521698,
0.030039921402931213,
0.03911525383591652,
-0.03271578997373581,
-0.030492011457681656,
-0.0006946202483959496,
0.011702473275363445,
-0.032786112278699875,
0.15455880761146545,
-0.02485589310526848,
0.02446778677403927,
-0.10509945452213287,
0.08857249468564987,
-0.... | 0.045103 |
projected service account token. # +required serviceAccountTokenAudience: "" # cacheType indicates the type of cache key use for caching the credentials returned by the plugin # when the service account token is used. # The most conservative option is to set this to "Token", which means the kubelet will cache # returne... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubelet-credential-provider.md | main | kubernetes | [
-0.0582016259431839,
-0.03636729344725609,
0.028426066040992737,
-0.04123726859688759,
-0.09435930848121643,
0.01731286011636257,
0.06910096853971481,
-0.012872097082436085,
0.12456522136926651,
0.056837864220142365,
-0.04650259017944336,
-0.06798098981380463,
0.00631737569347024,
0.002631... | 0.152385 |
images in order to determine if this provider should be invoked. More on this below. \* `defaultCacheDuration`: the default duration the kubelet will cache credentials in-memory if a cache duration was not specified by the plugin. \* `apiVersion`: the API version that the kubelet and the exec plugin will use when commu... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubelet-credential-provider.md | main | kubernetes | [
-0.03827662020921707,
-0.021163567900657654,
0.02641909383237362,
-0.032224033027887344,
-0.09617616981267929,
0.02084735780954361,
0.05778107792139053,
-0.008799724280834198,
0.1094784289598465,
0.021653948351740837,
-0.037088267505168915,
-0.12056131660938263,
-0.013296889141201973,
0.02... | 0.113408 |
of `matchImages` patterns are: \* `123456789.dkr.ecr.us-east-1.amazonaws.com` \* `\*.azurecr.io` \* `gcr.io` \* `\*.\*.registry.io` \* `foo.registry.io:8080/path` ## {{% heading "whatsnext" %}} \* Read the details about `CredentialProviderConfig` in the [kubelet configuration API (v1) reference](/docs/reference/config-... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubelet-credential-provider.md | main | kubernetes | [
-0.06340282410383224,
0.027905257418751717,
-0.00754461158066988,
-0.08250370621681213,
-0.04778648540377617,
0.02572413720190525,
-0.014225298538804054,
-0.03874000906944275,
0.0677909255027771,
-0.005500575061887503,
-0.0020528468303382397,
-0.11920277774333954,
0.05832697078585625,
-0.0... | 0.083947 |
This page shows how to enable or disable an API version from your cluster's {{< glossary\_tooltip text="control plane" term\_id="control-plane" >}}. Specific API versions can be turned on or off by passing `--runtime-config=api/` as a command line argument to the API server. The values for this argument are a comma-sep... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/enable-disable-api.md | main | kubernetes | [
-0.01726820319890976,
0.02037830464541912,
0.06436193734407425,
-0.020837895572185516,
-0.01444584783166647,
0.009271468967199326,
-0.07896044850349426,
-0.09401602298021317,
-0.011417215690016747,
0.03065665066242218,
-0.023572593927383423,
-0.05507514998316765,
-0.059268224984407425,
-0.... | 0.058902 |
When using client certificate authentication, you can generate certificates manually through [`easyrsa`](https://github.com/OpenVPN/easy-rsa), [`openssl`](https://github.com/openssl/openssl) or [`cfssl`](https://github.com/cloudflare/cfssl). ### easyrsa \*\*easyrsa\*\* can manually generate certificates for your cluste... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/certificates.md | main | kubernetes | [
-0.06089754402637482,
-0.03205491602420807,
-0.05474862456321716,
0.031731825321912766,
0.0035062714014202356,
-0.0007061599171720445,
-0.06104138866066933,
0.03875657916069031,
-0.025829771533608437,
-0.0027123161125928164,
0.04423558712005615,
-0.05657845363020897,
0.07274279743432999,
0... | -0.020122 |
curl -L https://github.com/cloudflare/cfssl/releases/download/v1.5.0/cfssl\_1.5.0\_linux\_amd64 -o cfssl chmod +x cfssl curl -L https://github.com/cloudflare/cfssl/releases/download/v1.5.0/cfssljson\_1.5.0\_linux\_amd64 -o cfssljson chmod +x cfssljson curl -L https://github.com/cloudflare/cfssl/releases/download/v1.5.0... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/certificates.md | main | kubernetes | [
-0.06733948737382889,
-0.016067693009972572,
-0.10740126669406891,
-0.04002511128783226,
0.05815054476261139,
-0.09241243451833725,
-0.054519541561603546,
0.03098970279097557,
0.04754702001810074,
-0.01324386801570654,
0.04695282503962517,
-0.04188805818557739,
-0.006098899524658918,
0.024... | 0.014084 |
Kubernetes core components such as the API server, scheduler, and controller-manager run on a control plane node. However, add-ons must run on a regular cluster node. Some of these add-ons are critical to a fully functional cluster, such as metrics-server, DNS, and UI. A cluster may stop working properly if a critical ... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods.md | main | kubernetes | [
0.03493572771549225,
-0.053975190967321396,
0.0325733982026577,
0.060967426747083664,
0.053513046354055405,
0.0014907618751749396,
-0.04240812361240387,
-0.03014054149389267,
0.06909395009279251,
0.1067323237657547,
0.016862893477082253,
-0.015117743983864784,
-0.018177572637796402,
-0.000... | 0.165793 |
{{< feature-state state="stable" for\_k8s\_version="v1.27" >}} An increasing number of systems leverage a combination of CPUs and hardware accelerators to support latency-critical execution and high-throughput parallel computation. These include workloads in fields such as telecommunications, scientific computing, mach... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/topology-manager.md | main | kubernetes | [
0.02435855008661747,
0.03214030712842941,
0.004740927368402481,
0.01047180313616991,
-0.014824624173343182,
-0.011401884257793427,
0.01064241211861372,
-0.00547351548448205,
0.045095011591911316,
-0.00769606651738286,
-0.044616010040044785,
-0.017899101600050926,
0.024031104519963264,
-0.0... | 0.188953 |
be configured on a Node. See [Control CPU Management Policies on the Node](/docs/tasks/administer-cluster/cpu-management-policies/). {{< /note >}} {{< note >}} To align memory (and hugepages) resources with other requested resources in a Pod spec, the Memory Manager should be enabled and proper Memory Manager policy sh... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/topology-manager.md | main | kubernetes | [
0.03905341401696205,
0.011976392939686775,
-0.04904494062066078,
0.03573238477110863,
-0.08604470640420914,
0.002096910495311022,
-0.03941949084401131,
0.004538748878985643,
0.05726810544729233,
0.01344604603946209,
-0.01544490922242403,
-0.01658281497657299,
-0.015087367966771126,
-0.0497... | 0.189413 |
`--topology-manager-policy`. There are four supported policies: \* `none` (default) \* `best-effort` \* `restricted` \* `single-numa-node` {{< note >}} If the Topology Manager is configured with the \*\*pod\*\* scope, the container, which is considered by the policy, is reflecting requirements of the entire pod, and th... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/topology-manager.md | main | kubernetes | [
-0.020329739898443222,
-0.023561622947454453,
0.00801595114171505,
-0.010255647823214531,
0.011382022872567177,
0.009945976547896862,
0.028601298108696938,
-0.03706774488091469,
0.022067371755838394,
0.02557407319545746,
-0.0001753010874381289,
-0.055969610810279846,
0.012625264003872871,
... | 0.164469 |
gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled. The Topology Manager is not aware by default of NUMA distances, and does not take them into account when making Pod admission decisions. This limitation surfaces in multi-socket, as well as single-socket multi NUMA systems, and can cause sig... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/topology-manager.md | main | kubernetes | [
0.06477776914834976,
-0.07024098932743073,
-0.049147576093673706,
-0.012889699079096317,
-0.00807251874357462,
-0.0425899513065815,
-0.06263206154108047,
-0.004251805134117603,
0.024839557707309723,
0.053891927003860474,
-0.03337961807847023,
-0.017933428287506104,
-0.00042066205060109496,
... | 0.195637 |
pod with sharing CPU request runs in the `Guaranteed` QoS class because `requests` are equal to `limits`. ```yaml spec: containers: - name: nginx image: nginx resources: limits: example.com/deviceA: "1" example.com/deviceB: "1" requests: example.com/deviceA: "1" example.com/deviceB: "1" ``` This pod runs in the `BestEf... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/topology-manager.md | main | kubernetes | [
-0.02740810438990593,
-0.0009419982088729739,
0.0035753578413277864,
0.02244124934077263,
0.01224702037870884,
-0.07716312259435654,
0.014352758415043354,
-0.01253005675971508,
0.05854025483131409,
-0.005780019331723452,
0.026536207646131516,
0.011490842327475548,
-0.0017378430347889662,
-... | 0.195915 |
This page shows how to change the default Storage Class that is used to provision volumes for PersistentVolumeClaims that have no special requirements. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## Why change the default storage class? Depending on the installati... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/change-default-storage-class.md | main | kubernetes | [
0.018519330769777298,
0.01854567788541317,
0.045730214565992355,
0.02297486551105976,
-0.054386407136917114,
0.020661110058426857,
-0.042985670268535614,
-0.02984154410660267,
0.02099362574517727,
0.05331552028656006,
-0.016839785501360893,
-0.0031770593486726284,
-0.008587745949625969,
0.... | 0.025743 |
{{< feature-state for\_k8s\_version="v1.21" state="stable" >}} This document describes how to configure and use kernel parameters within a Kubernetes cluster using the {{< glossary\_tooltip term\_id="sysctl" >}} interface. {{< note >}} Starting from Kubernetes version 1.23, the kubelet supports the use of either `/` or... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/sysctl-cluster.md | main | kubernetes | [
-0.004733098670840263,
0.017716053873300552,
0.07696417719125748,
-0.03386986628174782,
-0.0624641515314579,
0.0012251987354829907,
0.0032624551095068455,
0.014218210242688656,
0.06035228446125984,
0.01418346632272005,
0.010719500482082367,
-0.10477814823389053,
-0.01713571697473526,
-0.02... | 0.118178 |
sysctls are enabled on a node-by-node basis with a flag of the kubelet; for example: ```shell kubelet --allowed-unsafe-sysctls \ 'kernel.msg\*,net.core.somaxconn' ... ``` For {{< glossary\_tooltip term\_id="minikube" >}}, this can be done via the `extra-config` flag: ```shell minikube start --extra-config="kubelet.allo... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/sysctl-cluster.md | main | kubernetes | [
0.04376188665628433,
-0.004833062645047903,
0.013737686909735203,
-0.030532779172062874,
0.00881335511803627,
-0.00183587777428329,
0.026805367320775986,
0.010199894197285175,
0.05308986082673073,
0.02854171022772789,
0.022312341257929802,
-0.07817911356687546,
0.017062082886695862,
-0.040... | 0.122518 |
This page provides an overview of the steps you should follow to upgrade a Kubernetes cluster. The Kubernetes project recommends upgrading to the latest patch releases promptly, and to ensure that you are running a supported minor release of Kubernetes. Following this recommendation helps you to stay secure. The way th... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/cluster-upgrade.md | main | kubernetes | [
0.020815404132008553,
-0.05054672062397003,
0.06673697382211685,
-0.03535613417625427,
-0.00537942536175251,
0.03927134722471237,
-0.000930792884901166,
-0.07521244883537292,
-0.005036536604166031,
0.07933656871318817,
0.007221186999231577,
-0.07667254656553268,
-0.023563532158732414,
-0.0... | 0.044604 |
convert -f pod.yaml --output-version v1 ``` The `kubectl` tool replaces the contents of `pod.yaml` with a manifest that sets `kind` to Pod (unchanged), but with a revised `apiVersion`. ### Device Plugins If your cluster is running device plugins and the node needs to be upgraded to a Kubernetes release with a newer dev... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/cluster-upgrade.md | main | kubernetes | [
0.05045248195528984,
-0.014168365858495235,
0.07347962260246277,
-0.014651809819042683,
0.026905611157417297,
-0.0039359587244689465,
-0.08764907717704773,
-0.046148769557476044,
0.029669953510165215,
0.03947894647717476,
0.016909455880522728,
-0.037698086351156235,
-0.05136679857969284,
-... | 0.09244 |
This document covers topics related to protecting a cluster from accidental or malicious access and provides recommendations on overall security. ## {{% heading "prerequisites" %}} \* {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## Controlling access to the Kubernetes API As Kubernetes is entirely A... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/securing-a-cluster.md | main | kubernetes | [
-0.002235591411590576,
0.06734972447156906,
0.0591774508357048,
-0.015994854271411896,
0.002918334910646081,
0.06001715734601021,
0.02500198222696781,
-0.018040848895907402,
0.08349514752626419,
0.03384464979171753,
-0.035224102437496185,
-0.027536263689398766,
0.039731964468955994,
-0.001... | 0.17471 |
details, see [Hardening Guide - Dynamic Resource Allocation](/docs/concepts/security/hardening-guide/dynamic-resource-allocation/) and [Harden Dynamic Resource Allocation in Your Cluster](/docs/tasks/administer-cluster/hardening-dra/). ## Controlling access to the Kubelet Kubelets expose HTTPS endpoints which grant pow... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/securing-a-cluster.md | main | kubernetes | [
0.007626026403158903,
0.08289380371570587,
0.0020069018937647343,
-0.005920486059039831,
-0.07163726538419724,
-0.02598422020673752,
0.03255443274974823,
0.008663997054100037,
0.04147202521562576,
-0.012103480286896229,
-0.06767543405294418,
-0.05591663718223572,
0.02223552018404007,
-0.01... | 0.149488 |
able to use modules that had been loaded manually, or modules that were loaded by the kernel on behalf of some more-privileged process.) ### Restricting network access The [network policies](/docs/tasks/administer-cluster/declare-network-policy/) for a namespace allows application authors to restrict which pods in othe... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/securing-a-cluster.md | main | kubernetes | [
0.010948960669338703,
-0.028126217424869537,
-0.008226603269577026,
-0.0499044805765152,
0.02064589224755764,
0.027126600965857506,
0.02173314057290554,
-0.00932466983795166,
0.060968831181526184,
0.03658736124634743,
-0.024974703788757324,
0.00579109089449048,
0.027795635163784027,
-0.042... | 0.219986 |
active development and may have limitations or bugs that result in security vulnerabilities. Always assess the value an alpha or beta feature may provide against the possible risk to your security posture. When in doubt, disable features you do not use. ### Rotate infrastructure credentials frequently The shorter the l... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/securing-a-cluster.md | main | kubernetes | [
-0.01332477293908596,
0.01566973328590393,
0.031226227059960365,
-0.018686862662434578,
0.019177276641130447,
0.015184474177658558,
-0.016106843948364258,
0.025510406121611595,
0.060537271201610565,
-0.007389938458800316,
0.010153579525649548,
0.062030963599681854,
0.03038998320698738,
0.0... | 0.092198 |
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/decrypt-data.md | main | kubernetes | [
-0.04032835736870766,
0.08601973950862885,
0.025456704199314117,
0.01484718732535839,
-0.011492817662656307,
0.008512920700013638,
-0.024239206686615944,
-0.034966085106134415,
0.11622118204832077,
0.03523928299546242,
-0.07850729674100876,
-0.021842513233423233,
0.023531928658485413,
-0.0... | 0.018915 |
the volume you can find the file on the node filesystem and inspect it. ### Configure the API server to decrypt objects To disable encryption at rest, place the `identity` provider as the first entry in your encryption configuration file. For example, if your existing EncryptionConfiguration file reads: ```yaml --- api... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/decrypt-data.md | main | kubernetes | [
-0.04782826453447342,
0.07563009113073349,
-0.0012802563142031431,
0.0044949850998818874,
0.03247463330626488,
-0.00706472946330905,
-0.043042540550231934,
-0.02274700440466404,
0.06816903501749039,
0.04575737938284874,
-0.00363327469676733,
-0.01689239963889122,
0.023973286151885986,
0.01... | -0.003178 |
This example demonstrates how to limit the amount of storage consumed in a namespace. The following resources are used in the demonstration: [ResourceQuota](/docs/concepts/policy/resource-quotas/), [LimitRange](/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/), and [PersistentVolumeClaim](/docs... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/limit-storage-consumption.md | main | kubernetes | [
-0.07293333113193512,
0.027497518807649612,
-0.047356341034173965,
0.03375834599137306,
-0.006502008065581322,
-0.04280872642993927,
0.07252830266952515,
0.004156145267188549,
-0.007742965128272772,
0.09302414208650589,
-0.04077880457043648,
-0.040067389607429504,
0.12150629609823227,
0.04... | 0.071671 |
This page shows how to change the reclaim policy of a Kubernetes PersistentVolume. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## Why change reclaim policy of a PersistentVolume PersistentVolumes can have various reclaim policies, including "Retain", "Recycle", an... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/change-pv-reclaim-policy.md | main | kubernetes | [
-0.009404502809047699,
0.024188024923205376,
0.06676997989416122,
0.0022730042692273855,
0.01730327680706978,
0.032499875873327255,
0.04254469648003578,
-0.0803220272064209,
0.06643907725811005,
0.03286253660917282,
0.010176576673984528,
0.020639091730117798,
0.05317150428891182,
0.0080505... | 0.057984 |
This page shows cluster administrators how to harden authorization for Dynamic Resource Allocation (DRA), with a focus on least-privilege access for `ResourceClaim` status updates. ## {{% heading "prerequisites" %}} - {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} - Dynamic Resource Allocation is conf... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/hardening-dra.md | main | kubernetes | [
-0.059199560433626175,
-0.008008257485926151,
-0.024386221542954445,
0.012377176433801651,
-0.05271358788013458,
-0.009671799838542938,
-0.005654028616845608,
-0.02372518554329872,
0.009479562751948833,
0.07288260012865067,
-0.08147711306810379,
-0.006243297830224037,
0.008323300629854202,
... | 0.147717 |
{{< glossary\_definition term\_id="cloud-controller-manager" length="all" prepend="The cloud-controller-manager is">}} ## Background As part of the [cloud provider extraction effort](/blog/2019/04/17/the-future-of-cloud-providers-in-kubernetes/), all cloud specific controllers must be moved out of the `kube-controller-... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/controller-manager-leader-migration.md | main | kubernetes | [
-0.009510877542197704,
-0.04526398330926895,
-0.014154122211039066,
0.019717196002602577,
0.06885073333978653,
0.041523221880197525,
-0.021695340052247047,
-0.07392869889736176,
0.032579533755779266,
0.10457198321819305,
0.06975400447845459,
0.003135015955194831,
0.03242068737745285,
-0.10... | 0.035936 |
role 'system::leader-locking-cloud-controller-manager' -p '{"rules": [ {"apiGroups":[ "coordination.k8s.io"], "resources": ["leases"], "resourceNames": ["cloud-provider-extraction-migration"], "verbs": ["create", "list", "get", "update"] } ]}' --type=merge` ``` ### Initial Leader Migration configuration Leader Migratio... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/controller-manager-leader-migration.md | main | kubernetes | [
-0.03699204698204994,
-0.024703584611415863,
0.018990064039826393,
0.03251512348651886,
0.037571437656879425,
0.018763141706585884,
-0.012666151858866215,
-0.07820788025856018,
0.03635020926594734,
0.11952377110719681,
0.050766535103321075,
-0.027191024273633957,
0.04350549727678299,
-0.03... | 0.024674 |
from version N + 1 to N is required, add nodes of version N with Leader Migration enabled for `kube-controller-manager` back to the control plane, replacing one of version N + 1 each time until there are only nodes of version N. ### (Optional) Disable Leader Migration {#disable-leader-migration} Now that the control pl... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/controller-manager-leader-migration.md | main | kubernetes | [
-0.0047185407020151615,
-0.04065132886171341,
0.041860975325107574,
-0.01582242175936699,
0.005709108896553516,
0.05994299426674843,
-0.07206972688436508,
-0.11433017998933792,
0.05729277431964874,
0.08686450123786926,
0.059799838811159134,
0.030428659170866013,
0.001345923519693315,
-0.05... | -0.037698 |
{{< feature-state for\_k8s\_version="v1.26" state="stable" >}} Kubernetes keeps many aspects of how pods execute on nodes abstracted from the user. This is by design. However, some workloads require stronger guarantees in terms of latency and/or performance in order to operate acceptably. The kubelet provides methods t... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/cpu-management-policies.md | main | kubernetes | [
0.06060231849551201,
0.07244869321584702,
0.07950196415185928,
0.041988831013441086,
-0.04589449614286423,
-0.01999996416270733,
-0.0244385227560997,
-0.02161325328052044,
0.0573740117251873,
0.014358052052557468,
-0.06837315112352371,
-0.01862317882478237,
-0.004981428384780884,
-0.043021... | 0.167547 |
so that the cpu-sets set up by the new policy won’t conflict with it. 4. Edit the kubelet configuration to change the CPU manager policy to the desired value. 5. Start kubelet. Repeat this process for every node that needs its CPU manager policy changed. Skipping this process will result in kubelet crashlooping with th... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/cpu-management-policies.md | main | kubernetes | [
0.016055278480052948,
0.0129310954362154,
0.04981614276766777,
-0.007633393630385399,
-0.031259022653102875,
0.018590321764349937,
-0.0013733021914958954,
-0.020145615562796593,
-0.006474616006016731,
-0.00016771342779975384,
-0.028143757954239845,
-0.059682607650756836,
-0.01910174824297428... | 0.121815 |
It cannot be used with `full-pcpus-only` or `distribute-cpus-across-numa` policy options together at this moment. The `strict-cpu-reservation` option can be enabled by adding `strict-cpu-reservation=true` to the CPUManager policy options followed by removing the `/var/lib/kubelet/cpu\_manager\_state` file and restart k... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/cpu-management-policies.md | main | kubernetes | [
0.018429050222039223,
0.040446218103170395,
0.03048032708466053,
0.03125663101673126,
-0.04189494252204895,
-0.010586440563201904,
-0.02248549461364746,
-0.022976575419306755,
0.04182033613324165,
0.014950559474527836,
-0.006660928949713707,
-0.08582743257284164,
-0.04011979326605797,
-0.0... | 0.150863 |
{{< feature-state state="beta" for\_k8s\_version="v1.11" >}} Since cloud providers develop and release at a different pace compared to the Kubernetes project, abstracting the provider-specific code to the `{{< glossary\_tooltip text="cloud-controller-manager" term\_id="cloud-controller-manager" >}}` binary allows cloud... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/running-cloud-controller.md | main | kubernetes | [
-0.0742407739162445,
-0.0200987309217453,
0.05074277147650719,
0.010872913524508476,
0.013868868350982666,
0.0901472195982933,
0.01735755242407322,
-0.019390298053622246,
0.03489192575216293,
0.08871546387672424,
0.05512858182191849,
-0.017986848950386047,
-0.004626000765711069,
0.00140954... | 0.058626 |
maintained by cloud vendors or by SIGs. For providers already in Kubernetes core, you can run the in-tree cloud controller manager as a DaemonSet in your cluster, use the following as a guideline: {{% code\_sample file="admin/cloud/ccm-example.yaml" %}} ## Limitations Running cloud controller manager comes with a few p... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/running-cloud-controller.md | main | kubernetes | [
0.009229684248566628,
-0.06957168132066727,
-0.006649211514741182,
0.03189083933830261,
-0.01926845870912075,
0.04451316222548485,
-0.06103954464197159,
0.008065363392233849,
0.07093409448862076,
0.07016801089048386,
-0.017629344016313553,
-0.048880141228437424,
0.03917943313717842,
-0.028... | 0.077147 |
This page shows how to access clusters using the Kubernetes API. ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## Accessing the Kubernetes API ### Accessing for the first time with kubectl When accessing the Kubernetes API for the first time, use the Kubernetes comm... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/access-cluster-api.md | main | kubernetes | [
0.043871037662029266,
-0.04821746051311493,
-0.012956660240888596,
0.016901196911931038,
-0.03658605366945267,
0.06091535463929176,
-0.042363930493593216,
0.005586604587733746,
0.04545331001281738,
0.04931674897670746,
-0.05497448518872261,
-0.06417480111122131,
0.012257897295057774,
-0.05... | 0.118607 |
server. (These are installed in the `~/.kube` directory). Since cluster certificates are typically self-signed, it may take special configuration to get your http client to use root certificate. On some clusters, the API server does not require authentication; it may serve on localhost, or be protected by a firewall. T... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/access-cluster-api.md | main | kubernetes | [
-0.0006525571225211024,
0.0036556110717356205,
-0.024625927209854126,
-0.05004693940281868,
-0.062236569821834564,
0.01173098012804985,
-0.002022744854912162,
0.015861881896853447,
0.09069862216711044,
-0.018682487308979034,
-0.042334165424108505,
-0.03480503708124161,
0.04100094735622406,
... | 0.149777 |
CoreV1Api client V1PodList list = api.listPodForAllNamespaces(null, null, null, null, null, null, null, null, null); System.out.println("Listing all pods: "); for (V1Pod item : list.getItems()) { System.out.println(item.getMetadata().getName()); } } } ``` #### dotnet client To use [dotnet client](https://github.com/kub... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/access-cluster-api.md | main | kubernetes | [
0.00874705333262682,
-0.007707175333052874,
0.061082325875759125,
-0.031289923936128616,
0.01303744688630104,
0.03590760380029678,
-0.03913700953125954,
0.02481318823993206,
-0.01334574818611145,
0.057567205280065536,
-0.017694009467959404,
-0.09785909205675125,
-0.01587846130132675,
-0.00... | 0.114725 |
To avoid CNI plugin-related errors, verify that you are using or upgrading to a container runtime that has been tested to work correctly with your version of Kubernetes. ## About the "Incompatible CNI versions" and "Failed to destroy network for sandbox" errors Service issues exist for pod CNI network setup and tear do... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md | main | kubernetes | [
0.01896597631275654,
-0.00842868722975254,
0.0956464633345604,
-0.05589204654097557,
0.01340081449598074,
0.023188484832644463,
-0.06295917928218842,
-0.07111620157957077,
0.021761436015367508,
0.052936092019081116,
-0.023961681872606277,
-0.06633143872022629,
-0.022842729464173317,
0.0356... | 0.058795 |
loopback interface via a CNI plugin, `loopback`. The `loopback` plugin is distributed as part of the `containerd` release packages that have the `cni` designation. `containerd` v1.6.0 and later includes a CNI v1.0.0-compatible loopback plugin as well as other default CNI plugins. The configuration for the loopback plug... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md | main | kubernetes | [
-0.024785151705145836,
0.04020453616976738,
-0.04485124349594116,
-0.04030028358101845,
0.00845507811754942,
-0.039512984454631805,
-0.01828102394938469,
0.006866436451673508,
-0.024842990562319756,
-0.056328438222408295,
0.046232856810092926,
0.000361348211299628,
0.0043870676308870316,
-... | 0.030673 |
This task outlines the steps needed to update your container runtime to containerd from Docker. It is applicable for cluster operators running Kubernetes 1.23 or earlier. This also covers an example scenario for migrating from dockershim to containerd. Alternative container runtimes can be picked from this [page](/docs... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd.md | main | kubernetes | [
0.027512630447745323,
0.01612081192433834,
0.08525066077709198,
-0.015018508769571781,
-0.014767694287002087,
-0.023224879056215286,
-0.06927524507045746,
-0.03605012595653534,
0.015231099911034107,
0.06358214467763901,
-0.09136505424976349,
-0.08300908654928207,
-0.06135256215929985,
-0.0... | 0.035019 |
kubectl uncordon ``` Replace `` with the name of your node you previously drained. | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd.md | main | kubernetes | [
-0.017705421894788742,
0.07138345390558243,
0.06932791322469711,
0.02285509929060936,
-0.029818695038557053,
-0.03617836534976959,
-0.032750360667705536,
-0.048224207013845444,
0.11723248660564423,
0.0009192319121211767,
-0.02065226063132286,
-0.08988797664642334,
-0.026456622406840324,
-0... | 0.1187 |
{{% thirdparty-content %}} Kubernetes' support for direct integration with Docker Engine is deprecated and has been removed. Most apps do not have a direct dependency on runtime hosting containers. However, there are still a lot of telemetry and monitoring agents that have a dependency on Docker to collect containers m... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents.md | main | kubernetes | [
-0.009024899452924728,
-0.008719452656805515,
0.033066507428884506,
-0.0568806529045105,
0.04729875922203064,
-0.06272465735673904,
0.007089425344020128,
-0.014719230122864246,
0.08238586038351059,
0.007948069833219051,
-0.024418611079454422,
-0.07613653689622879,
-0.006690419279038906,
-0... | 0.198305 |
version of migration instructions for various telemetry and security agent vendors in [Google doc](https://docs.google.com/document/d/1ZFi4uKit63ga5sxEiZblfb-c23lFhvy6RXVPikS8wf0/edit#). Please contact the vendor to get up to date instructions for migrating from dockershim. ## Migration from dockershim ### [Aqua](https... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents.md | main | kubernetes | [
-0.048304878175258636,
0.005181971937417984,
0.04068409278988838,
-0.10642262548208237,
0.006663371343165636,
-0.07411342859268188,
-0.03367976099252701,
-0.009305262006819248,
-0.039656758308410645,
0.011665618978440762,
0.035402875393629074,
-0.05180168151855469,
0.030163588002324104,
-0... | 0.00131 |
The `dockershim` component of Kubernetes allows the use of Docker as a Kubernetes's {{< glossary\_tooltip text="container runtime" term\_id="container-runtime" >}}. Kubernetes' built-in `dockershim` component was removed in release v1.24. This page explains how your cluster could be using Docker as a container runtime,... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-removal-affects-you.md | main | kubernetes | [
0.010330354794859886,
0.025216490030288696,
0.0754939466714859,
0.03878236189484596,
0.06935962289571762,
-0.009256890043616295,
-0.01559020858258009,
-0.05569162964820862,
0.058243971318006516,
-0.0030220085754990578,
-0.010666940361261368,
-0.03448803722858429,
-0.009140146896243095,
-0.... | 0.073702 |
using `docker ps` or `docker inspect` commands. As you cannot list containers, you cannot get logs, stop containers, or execute something inside a container using `docker exec`. {{< note >}} If you're running workloads via Kubernetes, the best way to stop a container is through the Kubernetes API rather than directly t... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-removal-affects-you.md | main | kubernetes | [
0.016639208421111107,
0.08372858166694641,
0.02506357990205288,
-0.008013172075152397,
0.0748719647526741,
-0.015372417867183685,
-0.00851812306791544,
-0.002621408784762025,
0.0713188648223877,
0.0461357906460762,
-0.02992020733654499,
-0.09145550429821014,
-0.02139938995242119,
0.0203828... | 0.08618 |
This page outlines steps to find out what [container runtime](/docs/setup/production-environment/container-runtimes/) the nodes in your cluster use. Depending on the way you run your cluster, the container runtime for the nodes may have been pre-configured or you need to configure it. If you're using a managed Kubernet... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use.md | main | kubernetes | [
0.08969666063785553,
-0.012417253106832504,
0.04055137187242508,
-0.015753397718071938,
0.029032425954937935,
0.0001189211689052172,
-0.10293829441070557,
-0.0655742809176445,
0.03870769590139389,
0.012354536913335323,
-0.05401201173663139,
-0.08530320227146149,
-0.06456716358661652,
-0.06... | 0.08262 |
This section presents information you need to know when migrating from dockershim to other container runtimes. Since the announcement of [dockershim deprecation](/blog/2020/12/08/kubernetes-1-20-release-announcement/#dockershim-deprecation) in Kubernetes 1.20, there were questions on how this will affect various worklo... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/_index.md | main | kubernetes | [
-0.0038998995441943407,
0.02639792487025261,
0.07410454005002975,
-0.028538988903164864,
0.04297719895839691,
-0.018012376502156258,
-0.0403362475335598,
0.00006222096271812916,
0.011758877895772457,
-0.005914532579481602,
-0.05047517642378807,
-0.0355890728533268,
-0.021310584619641304,
-... | 0.003408 |
This page shows how to set minimum and maximum values for memory used by containers running in a {{< glossary\_tooltip text="namespace" term\_id="namespace" >}}. You specify minimum and maximum memory values in a [LimitRange](/docs/reference/kubernetes-api/policy-resources/limit-range-v1/) object. If a Pod does not mee... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/memory-constraint-namespace.md | main | kubernetes | [
0.05089200660586357,
0.026311038061976433,
0.0012512606335803866,
0.003095915075391531,
-0.08542205393314362,
0.007773236371576786,
0.03758981451392174,
-0.004678767640143633,
0.022133203223347664,
0.06706368178129196,
-0.04283008351922035,
-0.09847252070903778,
0.037553250789642334,
-0.04... | 0.095933 |
that has one container. That container specifies a memory request of 100 MiB and a memory limit of 800 MiB. {{% code\_sample file="admin/resource/memory-constraints-pod-3.yaml" %}} Attempt to create the Pod: ```shell kubectl apply -f https://k8s.io/examples/admin/resource/memory-constraints-pod-3.yaml --namespace=const... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/memory-constraint-namespace.md | main | kubernetes | [
0.06046475097537041,
0.04424527660012245,
-0.01877567358314991,
0.011665569618344307,
-0.01024292316287756,
-0.07748215645551682,
-0.01386863924562931,
0.03448929637670517,
0.045866914093494415,
0.06145302951335907,
-0.005836064461618662,
-0.036554303020238876,
-0.015571645461022854,
-0.01... | 0.163328 |
production and development, and you apply memory constraints to each namespace. ## Clean up Delete your namespace: ```shell kubectl delete namespace constraints-mem-example ``` ## {{% heading "whatsnext" %}} ### For cluster administrators \* [Configure Default Memory Requests and Limits for a Namespace](/docs/tasks/adm... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/memory-constraint-namespace.md | main | kubernetes | [
0.04663122817873955,
-0.0005143379676155746,
-0.030792709439992905,
0.00846601091325283,
-0.06964388489723206,
-0.02968589961528778,
-0.018199516460299492,
-0.011204800568521023,
0.027539249509572983,
0.05864275246858597,
-0.02052343264222145,
-0.08820898830890656,
-0.005784711800515652,
-... | 0.207474 |
This page shows how to configure default CPU requests and limits for a {{< glossary\_tooltip text="namespace" term\_id="namespace" >}}. A Kubernetes cluster can be divided into namespaces. If you create a Pod within a namespace that has a default CPU [limit](/docs/concepts/configuration/manage-resources-containers/#req... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/cpu-default-namespace.md | main | kubernetes | [
-0.0025988477282226086,
-0.023398177698254585,
0.021036721765995026,
0.04135049507021904,
-0.07543662190437317,
-0.03186282142996788,
0.024699920788407326,
-0.060539089143276215,
0.03736747428774834,
0.04553092643618584,
-0.03196202218532562,
-0.08468905091285706,
-0.05446330085396767,
-0.... | 0.095631 |
set to 1 `cpu`, which is the default CPU limit for that namespace. ``` resources: limits: cpu: "1" requests: cpu: 750m ``` ## Motivation for default CPU limits and requests If your namespace has a CPU {{< glossary\_tooltip text="resource quota" term\_id="resource-quota" >}} configured, it is helpful to have a default v... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/cpu-default-namespace.md | main | kubernetes | [
-0.01046032551676035,
-0.023050574585795403,
-0.006937171798199415,
0.03312202915549278,
-0.017552416771650314,
-0.05503258481621742,
0.027120044454932213,
-0.051578935235738754,
0.027198143303394318,
0.035471849143505096,
-0.021971408277750015,
-0.07116317003965378,
-0.03159426525235176,
... | 0.149892 |
This page shows how to set quotas for the total amount memory and CPU that can be used by all Pods running in a {{< glossary\_tooltip text="namespace" term\_id="namespace" >}}. You specify quotas in a [ResourceQuota](/docs/reference/kubernetes-api/policy-resources/resource-quota-v1/) object. ## {{% heading "prerequisit... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/quota-memory-cpu-namespace.md | main | kubernetes | [
0.0384947843849659,
0.0051232436671853065,
0.003764618653804064,
0.013344728387892246,
-0.0973445475101471,
-0.02003248780965805,
0.027772212401032448,
-0.009812891483306885,
0.043618589639663696,
0.08876160532236099,
-0.0663851872086525,
-0.13438405096530914,
0.005979869514703751,
-0.0469... | 0.108541 |
namespace. You can also restrict the totals for memory limit, cpu request, and cpu limit. Instead of managing total resource use within a namespace, you might want to restrict individual Pods, or the containers in those Pods. To achieve that kind of limiting, use a [LimitRange](/docs/concepts/policy/limit-range/). {{< ... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/quota-memory-cpu-namespace.md | main | kubernetes | [
0.04460904747247696,
0.03160660341382027,
0.009591716341674328,
0.026155268773436546,
-0.045223914086818695,
-0.0391477569937706,
0.017719319090247154,
0.013592205010354519,
0.059044405817985535,
0.06401491165161133,
-0.056314535439014435,
-0.06332551687955856,
0.006567238364368677,
-0.024... | 0.17391 |
This page shows how to set a quota for the total number of Pods that can run in a {{< glossary\_tooltip text="Namespace" term\_id="namespace" >}}. You specify quotas in a [ResourceQuota](/docs/reference/kubernetes-api/policy-resources/resource-quota-v1/) object. ## {{% heading "prerequisites" %}} {{< include "task-tuto... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/quota-pod-namespace.md | main | kubernetes | [
-0.008945455774664879,
0.000768505793530494,
0.021375156939029694,
0.012112128548324108,
-0.091242715716362,
0.00013027142267674208,
0.04394647479057312,
-0.019113104790449142,
0.057427454739809036,
0.09048381447792053,
-0.05655190348625183,
-0.1319669932126999,
0.036251265555620193,
-0.02... | 0.077267 |
This page shows how to set minimum and maximum values for the CPU resources used by containers and Pods in a {{< glossary\_tooltip text="namespace" term\_id="namespace" >}}. You specify minimum and maximum CPU values in a [LimitRange](/docs/reference/kubernetes-api/policy-resources/limit-range-v1/) object. If a Pod doe... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/cpu-constraint-namespace.md | main | kubernetes | [
0.02454935573041439,
0.003708284581080079,
0.025215161964297295,
0.009052474051713943,
-0.06437516957521439,
-0.03015410527586937,
0.02133738435804844,
-0.035282496362924576,
0.0011191983940079808,
0.062344133853912354,
-0.05063240975141525,
-0.12584160268306732,
0.007077948190271854,
-0.0... | 0.086307 |
apply -f https://k8s.io/examples/admin/resource/cpu-constraints-pod-2.yaml --namespace=constraints-cpu-example ``` The output shows that the Pod does not get created, because it defines an unacceptable container. That container is not acceptable because it specifies a CPU limit that is too large: ``` Error from server ... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/cpu-constraint-namespace.md | main | kubernetes | [
0.002978699281811714,
0.056960754096508026,
0.010431849397718906,
-0.019395316019654274,
-0.008005421608686447,
-0.08881083875894547,
-0.024015076458454132,
0.022440876811742783,
-0.0004892038996331394,
0.04019663482904434,
-0.004732689820230007,
-0.07597796618938446,
-0.02208310179412365,
... | 0.135722 |
Node in the cluster can support the request. \* A cluster is shared by your production and development departments. You want to allow production workloads to consume up to 3 CPU, but you want development workloads to be limited to 1 CPU. You create separate namespaces for production and development, and you apply CPU c... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/cpu-constraint-namespace.md | main | kubernetes | [
0.028667353093624115,
0.0010126593988388777,
-0.0483100526034832,
0.018281012773513794,
-0.08649859577417374,
-0.03651008754968643,
-0.04935639351606369,
-0.027048075571656227,
0.01333347987383604,
0.060526784509420395,
-0.06530538201332092,
-0.10353925079107285,
-0.005598023999482393,
-0.... | 0.201875 |
This page shows how to configure default memory requests and limits for a {{< glossary\_tooltip text="namespace" term\_id="namespace" >}}. A Kubernetes cluster can be divided into namespaces. Once you have a namespace that has a default memory [limit](/docs/concepts/configuration/manage-resources-containers/#requests-a... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/memory-default-namespace.md | main | kubernetes | [
0.0356438122689724,
-0.018889470025897026,
-0.009141582995653152,
0.03534366562962532,
-0.0925290435552597,
0.011187690310180187,
0.042122870683670044,
-0.022736893966794014,
0.04951249435544014,
0.06952521950006485,
-0.01976695843040943,
-0.05153275281190872,
-0.02155311405658722,
-0.0223... | 0.099414 |
resources: limits: memory: 512Mi requests: memory: 128Mi ``` {{< note >}} A `LimitRange` does \*\*not\*\* check the consistency of the default values it applies. This means that a default value for the \_limit\_ that is set by `LimitRange` may be less than the \_request\_ value specified for the container in the spec t... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/manage-resources/memory-default-namespace.md | main | kubernetes | [
-0.07427164167165756,
0.013196585699915886,
0.015275384299457073,
0.0373096764087677,
-0.0553332082927227,
-0.041214972734451294,
0.03549452871084213,
-0.03328393027186394,
0.06633781641721725,
0.022524138912558556,
-0.03747973591089249,
-0.0258087869733572,
0.003760690800845623,
-0.009603... | 0.117589 |
This page shows how to use Romana for NetworkPolicy. ## {{% heading "prerequisites" %}} Complete steps 1, 2, and 3 of the [kubeadm getting started guide](/docs/reference/setup-tools/kubeadm/). ## Installing Romana with kubeadm Follow the [containerized installation guide](https://github.com/romana/romana/tree/master/co... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/network-policy-provider/romana-network-policy.md | main | kubernetes | [
-0.02400912158191204,
0.008127417415380478,
-0.01744910515844822,
-0.10387630760669708,
-0.11932329833507538,
0.00765975471585989,
-0.03826107457280159,
0.03983635455369949,
-0.050015274435281754,
0.0291538555175066,
-0.00968173798173666,
-0.07629624009132385,
-0.02145235240459442,
-0.0599... | 0.163493 |
This page shows a couple of quick ways to create a Calico cluster on Kubernetes. ## {{% heading "prerequisites" %}} Decide whether you want to deploy a [cloud](#creating-a-calico-cluster-with-google-kubernetes-engine-gke) or [local](#creating-a-local-calico-cluster-with-kubeadm) cluster. ## Creating a Calico cluster wi... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/network-policy-provider/calico-network-policy.md | main | kubernetes | [
0.0345897451043129,
-0.05209916830062866,
0.019280143082141876,
-0.033746637403964996,
-0.028977399691939354,
0.01969739980995655,
-0.026023022830486298,
-0.04119662940502167,
0.036971550434827805,
0.03584269806742668,
0.023649757727980614,
-0.13301301002502441,
0.021560095250606537,
-0.01... | 0.094821 |
This page shows how to use [Kube-router](https://github.com/cloudnativelabs/kube-router) for NetworkPolicy. ## {{% heading "prerequisites" %}} You need to have a Kubernetes cluster running. If you do not already have a cluster, you can create one by using any of the cluster installers like Kops, Bootkube, Kubeadm etc. ... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/network-policy-provider/kube-router-network-policy.md | main | kubernetes | [
-0.007674062624573708,
0.02220306545495987,
0.005631583742797375,
-0.027452748268842697,
-0.06127068027853966,
0.060548584908246994,
-0.03420328348875046,
-0.018092351034283638,
-0.0238826684653759,
0.10354405641555786,
-0.046893879771232605,
-0.013447997160255909,
-0.021243438124656677,
-... | 0.063447 |
This page shows how to use Weave Net for NetworkPolicy. ## {{% heading "prerequisites" %}} You need to have a Kubernetes cluster. Follow the [kubeadm getting started guide](/docs/reference/setup-tools/kubeadm/) to bootstrap one. ## Install the Weave Net addon Follow the [Integrating Kubernetes via the Addon](https://gi... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/network-policy-provider/weave-network-policy.md | main | kubernetes | [
-0.051892999559640884,
0.00284382002428174,
-0.024887748062610626,
0.0006558173336088657,
-0.019347218796610832,
0.05071753263473511,
-0.009550291113555431,
-0.027956807985901833,
-0.05246014893054962,
0.050570257008075714,
0.017947088927030563,
-0.031523775309324265,
0.010441933758556843,
... | 0.0713 |
This page shows how to use Cilium for NetworkPolicy. For background on Cilium, read the [Introduction to Cilium](https://docs.cilium.io/en/stable/overview/intro). ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} ## Deploying Cilium on Minikube for Basic Testing To get ... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/network-policy-provider/cilium-network-policy.md | main | kubernetes | [
0.002065948210656643,
0.01833176799118519,
-0.022632239386439323,
-0.030579838901758194,
-0.05874207988381386,
-0.015258080326020718,
-0.09849953651428223,
0.0953039899468422,
-0.0108035271987319,
0.026139557361602783,
-0.0004796675348188728,
-0.048493724316358566,
0.018755510449409485,
-0... | 0.132203 |
This page shows how to install and use Antrea CNI plugin on Kubernetes. For background on Project Antrea, read the [Introduction to Antrea](https://antrea.io/docs/). ## {{% heading "prerequisites" %}} You need to have a Kubernetes cluster. Follow the [kubeadm getting started guide](/docs/reference/setup-tools/kubeadm/)... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/network-policy-provider/antrea-network-policy.md | main | kubernetes | [
-0.03894004598259926,
-0.003668593242764473,
0.005395141895860434,
-0.04513299837708473,
-0.009153877384960651,
0.017607565969228745,
-0.023915844038128853,
-0.0013163007097318769,
-0.07006324827671051,
0.05453520640730858,
-0.03751107677817345,
-0.04835038632154465,
-0.01491414662450552,
... | 0.2088 |
This page explains how to enable a package repository for the desired Kubernetes minor release upon upgrading a cluster. This is only needed for users of the community-owned package repositories hosted at `pkgs.k8s.io`. Unlike the legacy package repositories, the community-owned package repositories are structured in a... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubeadm/change-package-repository.md | main | kubernetes | [
0.027910565957427025,
-0.042633119970560074,
0.10659953206777573,
-0.03796440362930298,
0.018058909103274345,
0.0411185622215271,
-0.035729654133319855,
-0.047362420707941055,
0.006388496607542038,
0.0958082377910614,
0.03310132026672363,
-0.0072877840138971806,
-0.055503346025943756,
-0.0... | 0.051797 |
- `pkgs.k8s.io` - `pkgs.kubernetes.io` - `packages.kubernetes.io` {{}} ## Switching to another Kubernetes package repository This step should be done upon upgrading from one to another Kubernetes minor release in order to get access to the packages of the desired Kubernetes minor version. {{< tabs name="k8s\_upgrade\_v... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubeadm/change-package-repository.md | main | kubernetes | [
0.05710874870419502,
0.0249499324709177,
0.11541998386383057,
-0.08325459808111191,
0.009188098832964897,
0.008769574575126171,
-0.007584494072943926,
-0.000010808234037540387,
0.045741308480501175,
0.07773639261722565,
0.01195587869733572,
-0.021486802026629448,
-0.08001910150051117,
-0.0... | -0.010804 |
This page explains how to upgrade a Linux Worker Nodes 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 kubeadm cluster](/docs/tasks/administer-cluster/kubeadm/k... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubeadm/upgrading-linux-nodes.md | main | kubernetes | [
0.03553524240851402,
-0.04418385401368141,
0.03721277415752411,
-0.032991353422403336,
0.0012005874887108803,
0.012289226986467838,
-0.0669439360499382,
-0.0472906194627285,
-0.02814432792365551,
0.1275741010904312,
-0.011453033424913883,
-0.052627772092819214,
-0.03741525858640671,
-0.053... | 0.060936 |
This page explains how to add Linux worker nodes to a kubeadm cluster. ## {{% heading "prerequisites" %}} \* Each joining worker node has installed the required components from [Installing kubeadm](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/), such as, kubeadm, the kubelet and a {{< glossary\_tool... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubeadm/adding-linux-nodes.md | main | kubernetes | [
0.036897074431180954,
-0.06621940433979034,
-0.017449181526899338,
-0.024550028145313263,
-0.03169829770922661,
0.007503828499466181,
-0.03740603104233742,
-0.02263951301574707,
-0.03921680897474289,
0.020143862813711166,
-0.01310757640749216,
-0.12102402001619339,
0.016912316903471947,
-0... | 0.145995 |
{{< feature-state for\_k8s\_version="v1.18" state="beta" >}} This page explains how to add Windows worker nodes to a kubeadm cluster. ## {{% heading "prerequisites" %}} \* A running [Windows Server 2022](https://www.microsoft.com/cloud-platform/windows-server-pricing) (or higher) instance with administrative access. \*... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md | main | kubernetes | [
0.011290744878351688,
-0.012242630124092102,
-0.003558667842298746,
0.05786886066198349,
-0.03356841206550598,
0.051642630249261856,
-0.03140188753604889,
-0.06626340001821518,
-0.03462522104382515,
0.08627832680940628,
-0.04901503771543503,
-0.11545296013355255,
-0.0020946431905031204,
-0... | 0.143765 |
control-plane to see this machine join. ``` A few seconds later, you should notice this node in the output from `kubectl get nodes`. (for example, run `kubectl` on a control plane node). ### Network configuration CNI setup on clusters mixed with Linux and Windows nodes requires more steps than just running `kubectl app... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md | main | kubernetes | [
-0.014573423191905022,
-0.02939746156334877,
-0.0561111755669117,
-0.0075604054145514965,
-0.02232024259865284,
0.022970983758568764,
-0.047668635845184326,
-0.038781020790338516,
0.005977114196866751,
0.012099937535822392,
-0.02820933796465397,
-0.13043750822544098,
-0.0159289613366127,
-... | 0.158294 |
This page explains how to upgrade a Kubernetes cluster created with kubeadm from version {{< skew currentVersionAddMinor -1 >}}.x to version {{< skew currentVersion >}}.x, and from version {{< skew currentVersion >}}.x to {{< skew currentVersion >}}.y (where `y > x`). Skipping MINOR versions when upgrading is unsupport... | https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md | main | kubernetes | [
0.09224793314933777,
-0.01916166953742504,
0.06413228809833527,
-0.066683329641819,
0.0642504096031189,
0.01273318286985159,
-0.08144006133079529,
-0.06417293101549149,
0.0073380679823458195,
0.047391001135110855,
0.0601394921541214,
-0.02844615839421749,
-0.02066240832209587,
-0.060720905... | 0.013556 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.