jiebi/CodeConvo huggingface dataset:
See [Add ImagePullSecrets to a service account](/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account) for a detailed explanation of that process. <del> ### Automatic mounting of manually created Secrets Manually created secrets (for example, one containing a token for accessing a GitHub account) can be automatically attached to pods based on their service account. </del> ## Details ### Restrictions
### rbd `rbd` 볼륨을 사용하면 <del> [Rados Block Device](https://ceph.com/docs/master/rbd/rbd/)(RBD) 볼륨을 파드에 마운트할 수 </del> <ins> [Rados Block Device](https://docs.ceph.com/en/latest/rbd/)(RBD) 볼륨을 파드에 마운트할 수 </ins> 있다. 파드를 제거할 때 지워지는 `emptyDir` 와는 다르게 `rbd` 볼륨의 내용은 유지되고, 볼륨은 마운트 해제만 된다. 이 의미는 RBD 볼륨에 데이터를 미리 채울 수 있으며, 데이터를
Area of Concern for Workload Security | Recommendation | ------------------------------ | --------------------- | RBAC Authorization (Access to the Kubernetes API) | https://kubernetes.io/docs/reference/access-authn-authz/rbac/ <del> Authentication | https://kubernetes.io/docs/reference/access-authn-authz/controlling-access/ </del> <ins> Authentication | https://kubernetes.io/docs/concepts/security/controlling-access/ </ins> Application secrets management (and encrypting them in etcd at rest) | https://kubernetes.io/docs/concepts/configuration/secret/ <br> https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/ Pod Security Policies | https://kubernetes.io/docs/concepts/policy/pod-security-policy/ Quality of Service (and Cluster resource management) | https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/
容易受到资源枯竭的攻击，则如果你不限制服务 B 的资源的话，损害服务 A 的风险就会很高。 下表列出了安全性关注的领域和建议，用以保护 Kubernetes 中运行的工作负载： <del> 工作负载安全性关注领域 |  建议 | </del> <ins> 工作负载安全性关注领域         |  建议                 | </ins> ------------------------------ | --------------------- | RBAC 授权(访问 Kubernetes API) | https://kubernetes.io/zh/docs/reference/access-authn-authz/rbac/ <del> 认证方式 | https://kubernetes.io/zh/docs/reference/access-authn-authz/controlling-access/ </del> <ins> 认证方式 | https://kubernetes.io/zh/docs/concepts/security/controlling-access/ </ins> 应用程序 Secret 管理 (并在 etcd 中对其进行静态数据加密) | https://kubernetes.io/zh/docs/concepts/configuration/secret/ <br> https://kubernetes.io/zh/docs/tasks/administer-cluster/encrypt-data/ Pod 安全策略 | https://kubernetes.io/zh/docs/concepts/policy/pod-security-policy/ 服务质量（和集群资源管理）| https://kubernetes.io/zh/docs/tasks/configure-pod-container/quality-service-pod/
Container Vulnerability Scanning and OS Dependency Security | As part of an image build step, you should scan your containers for known vulnerabilities. Image Signing and Enforcement | Sign container images to maintain a system of trust for the content of your containers. Disallow privileged users | When constructing containers, consult your documentation for how to create users inside of the containers that have the least level of operating system privilege necessary in order to carry out the goal of the container. <ins> Use container runtime with stronger isolation | Select [container runtime classes](/docs/concepts/containers/runtime-class/) that provider stronger isolation </ins> --> ## 容器
容器漏洞扫描和操作系统依赖安全性 | 作为镜像构建的一部分，您应该扫描您的容器里的已知漏洞。 镜像签名和执行 | 对容器镜像进行签名，以维护对容器内容的信任。 禁止特权用户 | 构建容器时，请查阅文档以了解如何在具有最低操作系统特权级别的容器内部创建用户，以实现容器的目标。 <ins> 使用带有较强隔离能力的容器运行时 | 选择提供较强隔离能力的[容器运行时类](/zh/docs/concepts/containers/runtime-class/)。 </ins> <!-- ## Code
* [Data encryption in transit](/docs/tasks/tls/managing-tls-in-a-cluster/) for the control plane * [Data encryption at rest](/docs/tasks/administer-cluster/encrypt-data/) * [Secrets in Kubernetes](/docs/concepts/configuration/secret/) <ins> * [Runtime class](/docs/concepts/containers/runtime-class) </ins> --> 学习了解相关的 Kubernetes 安全主题：
* 为控制面[加密通信中的数据](/zh/docs/tasks/tls/managing-tls-in-a-cluster/) * [加密静止状态的数据](/zh/docs/tasks/administer-cluster/encrypt-data/) * [Kubernetes 中的 Secret](/zh/docs/concepts/configuration/secret/) <ins> * [运行时类](/zh/docs/concepts/containers/runtime-class) </ins>
<!-- overview --> This page explains how to upgrade a Kubernetes cluster created with kubeadm from version <del> {{< skew latestVersionAddMinor -1 >}}.x to version {{< skew latestVersion >}}.x, and from version {{< skew latestVersion >}}.x to {{< skew latestVersion >}}.y (where `y > x`). Skipping MINOR versions </del> <ins> {{< 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 </ins> when upgrading is unsupported. To see information about upgrading clusters created using older versions of kubeadm, please refer to following pages instead: <del> - [Upgrading a kubeadm cluster from {{< skew latestVersionAddMinor -2 >}} to {{< skew latestVersionAddMinor -1 >}}](https://v{{< skew latestVersionAddMinor -1 "-" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew latestVersionAddMinor -3 >}} to {{< skew latestVersionAddMinor -2 >}}](https://v{{< skew latestVersionAddMinor -2 "-" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew latestVersionAddMinor -4 >}} to {{< skew latestVersionAddMinor -3 >}}](https://v{{< skew latestVersionAddMinor -3 "-" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew latestVersionAddMinor -5 >}} to {{< skew latestVersionAddMinor -4 >}}](https://v{{< skew latestVersionAddMinor -4 "-" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) </del> <ins> - [Upgrading a kubeadm cluster from {{< skew currentVersionAddMinor -2 >}} to {{< skew currentVersionAddMinor -1 >}}](https://v{{< skew currentVersionAddMinor -1 "-" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew currentVersionAddMinor -3 >}} to {{< skew currentVersionAddMinor -2 >}}](https://v{{< skew currentVersionAddMinor -2 "-" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew currentVersionAddMinor -4 >}} to {{< skew currentVersionAddMinor -3 >}}](https://v{{< skew currentVersionAddMinor -3 "-" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew currentVersionAddMinor -5 >}} to {{< skew currentVersionAddMinor -4 >}}](https://v{{< skew currentVersionAddMinor -4 "-" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) </ins> The upgrade workflow at high level is the following:
## Determine which version to upgrade to <del> Find the latest stable {{< skew latestVersion >}} version using the OS package manager: </del> <ins> Find the latest stable {{< skew currentVersion >}} version using the OS package manager: </ins> {{< tabs name="k8s_install_versions" >}} {{% tab name="Ubuntu, Debian or HypriotOS" %}} apt update apt-cache madison kubeadm <del> # find the latest {{< skew latestVersion >}} version in the list # it should look like {{< skew latestVersion >}}.x-00, where x is the latest patch </del> <ins> # find the latest {{< skew currentVersion >}} version in the list # it should look like {{< skew currentVersion >}}.x-00, where x is the latest patch </ins> {{% /tab %}} {{% tab name="CentOS, RHEL or Fedora" %}} yum list --showduplicates kubeadm --disableexcludes=kubernetes <del> # find the latest {{< skew latestVersion >}} version in the list # it should look like {{< skew latestVersion >}}.x-0, where x is the latest patch </del> <ins> # find the latest {{< skew currentVersion >}} version in the list # it should look like {{< skew currentVersion >}}.x-0, where x is the latest patch </ins> {{% /tab %}} {{< /tabs >}}
{{< tabs name="k8s_install_kubeadm_first_cp" >}} {{% tab name="Ubuntu, Debian or HypriotOS" %}} <del> # replace x in {{< skew latestVersion >}}.x-00 with the latest patch version </del> <ins> # replace x in {{< skew currentVersion >}}.x-00 with the latest patch version </ins> apt-mark unhold kubeadm &&  <del> apt-get update && apt-get install -y kubeadm={{< skew latestVersion >}}.x-00 &&  </del> <ins> apt-get update && apt-get install -y kubeadm={{< skew currentVersion >}}.x-00 &&  </ins> apt-mark hold kubeadm - # since apt-get version 1.1 you can also use the following method apt-get update &&  <del> apt-get install -y --allow-change-held-packages kubeadm={{< skew latestVersion >}}.x-00 </del> <ins> apt-get install -y --allow-change-held-packages kubeadm={{< skew currentVersion >}}.x-00 </ins> {{% /tab %}} {{% tab name="CentOS, RHEL or Fedora" %}} <del> # replace x in {{< skew latestVersion >}}.x-0 with the latest patch version yum install -y kubeadm-{{< skew latestVersion >}}.x-0 --disableexcludes=kubernetes </del> <ins> # replace x in {{< skew currentVersion >}}.x-0 with the latest patch version yum install -y kubeadm-{{< skew currentVersion >}}.x-0 --disableexcludes=kubernetes </ins> {{% /tab %}} {{< /tabs >}}
```shell # replace x with the patch version you picked for this upgrade <del> sudo kubeadm upgrade apply v{{< skew latestVersion >}}.x </del> <ins> sudo kubeadm upgrade apply v{{< skew currentVersion >}}.x </ins> ``` Once the command finishes you should see: ``` <del> [upgrade/successful] SUCCESS! Your cluster was upgraded to "v{{< skew latestVersion >}}.x". Enjoy! </del> <ins> [upgrade/successful] SUCCESS! Your cluster was upgraded to "v{{< skew currentVersion >}}.x". Enjoy! </ins> [upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so. ```
{{< tabs name="k8s_install_kubelet" >}} {{< tab name="Ubuntu, Debian or HypriotOS" >}} <pre> <del> # replace x in {{< skew latestVersion >}}.x-00 with the latest patch version </del> <ins> # replace x in {{< skew currentVersion >}}.x-00 with the latest patch version </ins> apt-mark unhold kubelet kubectl &&  <del> apt-get update && apt-get install -y kubelet={{< skew latestVersion >}}.x-00 kubectl={{< skew latestVersion >}}.x-00 &&  </del> <ins> apt-get update && apt-get install -y kubelet={{< skew currentVersion >}}.x-00 kubectl={{< skew currentVersion >}}.x-00 &&  </ins> apt-mark hold kubelet kubectl - # since apt-get version 1.1 you can also use the following method apt-get update &&  <del> apt-get install -y --allow-change-held-packages kubelet={{< skew latestVersion >}}.x-00 kubectl={{< skew latestVersion >}}.x-00 </del> <ins> apt-get install -y --allow-change-held-packages kubelet={{< skew currentVersion >}}.x-00 kubectl={{< skew currentVersion >}}.x-00 </ins> </pre> {{< /tab >}} {{< tab name="CentOS, RHEL or Fedora" >}} <pre> <del> # replace x in {{< skew latestVersion >}}.x-0 with the latest patch version yum install -y kubelet-{{< skew latestVersion >}}.x-0 kubectl-{{< skew latestVersion >}}.x-0 --disableexcludes=kubernetes </del> <ins> # replace x in {{< skew currentVersion >}}.x-0 with the latest patch version yum install -y kubelet-{{< skew currentVersion >}}.x-0 kubectl-{{< skew currentVersion >}}.x-0 --disableexcludes=kubernetes </ins> </pre> {{< /tab >}} {{< /tabs >}}
{{< tabs name="k8s_install_kubeadm_worker_nodes" >}} {{% tab name="Ubuntu, Debian or HypriotOS" %}} <del> # replace x in {{< skew latestVersion >}}.x-00 with the latest patch version </del> <ins> # replace x in {{< skew currentVersion >}}.x-00 with the latest patch version </ins> apt-mark unhold kubeadm &&  <del> apt-get update && apt-get install -y kubeadm={{< skew latestVersion >}}.x-00 &&  </del> <ins> apt-get update && apt-get install -y kubeadm={{< skew currentVersion >}}.x-00 &&  </ins> apt-mark hold kubeadm - # since apt-get version 1.1 you can also use the following method apt-get update &&  <del> apt-get install -y --allow-change-held-packages kubeadm={{< skew latestVersion >}}.x-00 </del> <ins> apt-get install -y --allow-change-held-packages kubeadm={{< skew currentVersion >}}.x-00 </ins> {{% /tab %}} {{% tab name="CentOS, RHEL or Fedora" %}} <del> # replace x in {{< skew latestVersion >}}.x-0 with the latest patch version yum install -y kubeadm-{{< skew latestVersion >}}.x-0 --disableexcludes=kubernetes </del> <ins> # replace x in {{< skew currentVersion >}}.x-0 with the latest patch version yum install -y kubeadm-{{< skew currentVersion >}}.x-0 --disableexcludes=kubernetes </ins> {{% /tab %}} {{< /tabs >}}
{{< tabs name="k8s_kubelet_and_kubectl" >}} {{% tab name="Ubuntu, Debian or HypriotOS" %}} <del> # replace x in {{< skew latestVersion >}}.x-00 with the latest patch version </del> <ins> # replace x in {{< skew currentVersion >}}.x-00 with the latest patch version </ins> apt-mark unhold kubelet kubectl &&  <del> apt-get update && apt-get install -y kubelet={{< skew latestVersion >}}.x-00 kubectl={{< skew latestVersion >}}.x-00 &&  </del> <ins> apt-get update && apt-get install -y kubelet={{< skew currentVersion >}}.x-00 kubectl={{< skew currentVersion >}}.x-00 &&  </ins> apt-mark hold kubelet kubectl - # since apt-get version 1.1 you can also use the following method apt-get update &&  <del> apt-get install -y --allow-change-held-packages kubelet={{< skew latestVersion >}}.x-00 kubectl={{< skew latestVersion >}}.x-00 </del> <ins> apt-get install -y --allow-change-held-packages kubelet={{< skew currentVersion >}}.x-00 kubectl={{< skew currentVersion >}}.x-00 </ins> {{% /tab %}} {{% tab name="CentOS, RHEL or Fedora" %}} <del> # replace x in {{< skew latestVersion >}}.x-0 with the latest patch version yum install -y kubelet-{{< skew latestVersion >}}.x-0 kubectl-{{< skew latestVersion >}}.x-0 --disableexcludes=kubernetes </del> <ins> # replace x in {{< skew currentVersion >}}.x-0 with the latest patch version yum install -y kubelet-{{< skew currentVersion >}}.x-0 kubectl-{{< skew currentVersion >}}.x-0 --disableexcludes=kubernetes </ins> {{% /tab %}} {{< /tabs >}}
{{- $latestVersionAddMinor = printf "%s%s%d" (index $versionArray 0) $seperator $latestVersionAddMinor -}} {{- $latestVersionAddMinor -}} {{- end -}} <ins> {{- $currentVersion := site.Params.version -}} {{- $currentVersion := (replace $currentVersion "v" "") -}} {{- $currentVersionArray := split $currentVersion "." -}} {{- $currentMinorVersion := int (index $currentVersionArray 1) -}} <!-- output latestVersion based on captured arg --> {{- if eq $version "currentVersion" -}} {{- $currentVersion -}} {{- end -}} <!-- output currentVersionAddMinor based on captured args --> {{- if eq $version "currentVersionAddMinor" -}} {{- $seperator := .Get 2 -}} {{- if eq $seperator "" -}} {{- $seperator = "." -}} {{- end -}} {{- $currentVersionAddMinor := int (.Get 1) -}} {{- $currentVersionAddMinor = add $currentMinorVersion $currentVersionAddMinor -}} {{- $currentVersionAddMinor = printf "%s%s%d" (index $versionArray 0) $seperator $currentVersionAddMinor -}} {{- $currentVersionAddMinor -}} {{- end -}} </ins> <!-- example shortcode use: - skew nextMinorVersion - skew latestVersion <ins> - skew currentVersion </ins> - skew prevMinorVersion - skew oldestMinorVersion - skew latestVersionAddMinor -1 "-" <ins> - skew currentVersionAddMinor -1 "-" </ins> -->  No newline at end of file
A longstanding bug regarding exec probe timeouts that may impact existing pod definitions has been fixed. Prior to this fix, the field `timeoutSeconds` was not respected for exec probes. Instead, probes would run indefinitely, even past their configured deadline, until a result was returned. With this change, the default value of `1 second` will be applied if a value is not specified and existing pod definitions may no longer be sufficient if a probe takes longer than one second. A feature gate, called `ExecProbeTimeout`, has been added with this fix that enables cluster operators to revert to the previous behavior, but this will be locked and removed in subsequent releases. In order to revert to the previous behavior, cluster operators should set this feature gate to `false`. <del> Please review the updated documentation regarding [configuring probes](docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes) for more details. </del> <ins> Please review the updated documentation regarding [configuring probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes) for more details. </ins> ## Other Updates
{{< note >}} To be able to create Indexed Jobs, make sure to enable the `IndexedJob` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) <del> on the [API server](docs/reference/command-line-tools-reference/kube-apiserver/) </del> <ins> on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/) </ins> and the [controller manager](/docs/reference/command-line-tools-reference/kube-controller-manager/). {{< /note >}}
{{< note >}} Suspending Jobs is available in Kubernetes versions 1.21 and above. You must enable the `SuspendJob` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) <del> on the [API server](docs/reference/command-line-tools-reference/kube-apiserver/) </del> <ins> on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/) </ins> and the [controller manager](/docs/reference/command-line-tools-reference/kube-controller-manager/) in order to use this feature. {{< /note >}}
### Migrating to the `systemd` driver in kubeadm managed clusters <del> Follow this [Migration guide](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver) </del> <ins> Follow this [Migration guide](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/) </ins> if you wish to migrate to the `systemd` cgroup driver in existing kubeadm managed clusters. ## Container runtimes
Refer to the following table for Windows operating system support in Kubernetes. A single heterogeneous Kubernetes cluster can have both Windows and Linux worker nodes. Windows containers have to be scheduled on Windows nodes and Linux containers on Linux nodes. | Kubernetes version | Windows Server LTSC releases | Windows Server SAC releases | <del> | --- | --- | --- | --- | </del> <ins> | --- | --- | --- | </ins> | *Kubernetes v1.17* | Windows Server 2019 | Windows Server ver 1809 | | *Kubernetes v1.18* | Windows Server 2019 | Windows Server ver 1809, Windows Server ver 1903, Windows Server ver 1909 | | *Kubernetes v1.19* | Windows Server 2019 | Windows Server ver 1909, Windows Server ver 2004 |
{{< note >}} Kubeadm uses the same `KubeletConfiguration` for all nodes in the cluster. <del> The `KubeletConfiguration` is stored in a [ConfigMap](docs/concepts/configuration/configmap) </del> <ins> The `KubeletConfiguration` is stored in a [ConfigMap](/docs/concepts/configuration/configmap) </ins> object under the `kube-system` namespace. Executing the sub commands `init`, `join` and `upgrade` would result in kubeadm
To be able to create Indexed Jobs, make sure to enable the `IndexedJob` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) <del> on the [API server](docs/reference/command-line-tools-reference/kube-apiserver/) </del> <ins> on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/) </ins> and the [controller manager](/docs/reference/command-line-tools-reference/kube-controller-manager/). <!-- steps -->
## Downloads for v1.21.0 <ins> ### Source Code </ins> filename | sha512 hash -------- | ----------- [kubernetes.tar.gz](https://dl.k8s.io/v1.21.0/kubernetes.tar.gz) | `19bb76a3fa5ce4b9f043b2a3a77c32365ab1fcb902d8dd6678427fb8be8f49f64a5a03dc46aaef9c7dadee05501cf83412eda46f0edacbb8fc1ed0bf5fb79142`
Los objetos básicos de Kubernetes incluyen: <del> * [Pod](/docs/concepts/workloads/pods/pod-overview/) </del> <ins> * [Pod](/es/docs/concepts/workloads/pods/pod/) </ins> * [Service](/docs/concepts/services-networking/service/) * [Volume](/docs/concepts/storage/volumes/) <del> * [Namespace](/docs/concepts/overview/working-with-objects/namespaces/) </del> <ins> * [Namespace](/es/docs/concepts/overview/working-with-objects/namespaces/) </ins> Además, Kubernetes contiene abstracciónes de nivel superior llamadas Controladores. Los Controladores se basan en los objetos básicos y proporcionan funcionalidades adicionales sobre ellos. Incluyen: <del> * [ReplicaSet](/docs/concepts/workloads/controllers/replicaset/) * [Deployment](/docs/concepts/workloads/controllers/deployment/) * [StatefulSet](/docs/concepts/workloads/controllers/statefulset/) * [DaemonSet](/docs/concepts/workloads/controllers/daemonset/) * [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/) </del> <ins> * [ReplicaSet](/es/docs/concepts/workloads/controllers/replicaset/) * [Deployment](/es/docs/concepts/workloads/controllers/deployment/) * [StatefulSet](/es/docs/concepts/workloads/controllers/statefulset/) * [DaemonSet](/es/docs/concepts/workloads/controllers/daemonset/) * [Job](/es/docs/concepts/workloads/controllers/jobs-run-to-completion/) </ins> ## Plano de Control de Kubernetes
#### Metadatos de los Objectos <del> * [Annotations](/docs/concepts/overview/working-with-objects/annotations/) </del> <ins> * [Annotations](/es/docs/concepts/overview/working-with-objects/annotations/) </ins> ## {{% heading "whatsnext" %}} <del> Si estás interesado en escribir una página sobre conceptos, revisa [Usando Templates de Páginas](/docs/home/contribute/page-templates/) para obtener información sobre el tipo de página conceptos y la plantilla conceptos. </del> <ins> Si quieres empezar a contribuir a la documentación de Kubernetes accede a la página [Empieza a contribuir](/es/docs/contribute/start/). </ins>
| `ProbeTerminationGracePeriod` | `false` | Alpha | 1.21 | | | `ProcMountType` | `false` | Alpha | 1.12 | | | `QOSReserved` | `false` | Alpha | 1.11 | | <del> | `RemainingItemCount` | `false` | Alpha | 1.15 | | </del> <ins> | `RemainingItemCount` | `false` | Alpha | 1.15 | 1.15 | | `RemainingItemCount` | `true` | Beta | 1.16 | | </ins> | `RemoveSelfLink` | `false` | Alpha | 1.16 | 1.19 | | `RemoveSelfLink` | `true` | Beta | 1.20 | | | `RotateKubeletServerCertificate` | `false` | Alpha | 1.7 | 1.11 |
} ``` <del> Note that the `resourceVersion` of the list remains constant across each request, indicating the server is showing us a consistent snapshot of the pods. Pods that are created, updated, or deleted after version `10245` would not be shown unless the user makes a list request without the `continue` token.  This allows clients to break large requests into smaller chunks and then perform a watch operation on the full set without missing any updates. </del> <ins> Note that the `resourceVersion` of the list remains constant across each request, indicating the server is showing us a consistent snapshot of the pods. Pods that are created, updated, or deleted after version `10245` would not be shown unless the user makes a list request without the `continue` token.  This allows clients to break large requests into smaller chunks and then perform a watch operation on the full set without missing any updates. `remainingItemCount` is the number of subsequent items in the list which are not included in this list response. If the list request contained label or field selectors, then the number of remaining items is unknown and the API server does not include a `remainingItemCount` field in its response. If the list is complete (either because it is not chunking or because this is the last chunk), then there are no more remaining items and the API server does not include a `remainingItemCount` field in its response. The intended use of the `remainingItemCount` is estimating the size of a collection. </ins> ## Receiving resources as Tables