---
title: Kubelet 配置 (v1beta1)
content_type: tool-reference
package: kubelet.config.k8s.io/v1beta1
---
<!--
title: Kubelet Configuration (v1beta1)
content_type: tool-reference
package: kubelet.config.k8s.io/v1beta1
auto_generated: true
-->

<!--
## Resource Types
-->
## 资源类型   {#resource-types}

- [CredentialProviderConfig](#kubelet-config-k8s-io-v1beta1-CredentialProviderConfig)
- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)
- [SerializedNodeConfigSource](#kubelet-config-k8s-io-v1beta1-SerializedNodeConfigSource)

## `FormatOptions`     {#FormatOptions}

<!--
**Appears in:**
-->
**出现在：**

- [LoggingConfiguration](#LoggingConfiguration)

<p>
<!--
FormatOptions contains options for the different logging formats.
-->
FormatOptions 包含为不同日志格式提供的选项。
</p>

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr>
<td>
<code>text</code> <B><!-- [Required] -->[必需]</B><br/>
<a href="#TextOptions"><code>TextOptions</code></a>
</td>
<td>
<!--
   <p>[Alpha] Text contains options for logging format &quot;text&quot;.
Only available when the LoggingAlphaOptions feature gate is enabled.</p>
-->
   <p>[Alpha] 文本包含用于记录 &quot;text&quot; 格式的选项。
仅当 LoggingAlphaOptions 特性门控被启用时可用。</p>
</td>
</tr>

<tr><td><code>json</code> <B><!-- [Required] -->[必需]</B><br/>
<a href="#JSONOptions"><code>JSONOptions</code></a>
</td>
<td>
   <!--
   [Alpha] JSON contains options for logging format &quot;json&quot;.
Only available when the LoggingAlphaOptions feature gate is enabled.
   -->
   <p>[Alpha] <code>json</code> 包含 &quot;json&quot; 日志格式的选项。
只有 LoggingAlphaOptions 特性门控被启用时才可用。</p>
</td>
</tr>
</tbody>
</table>

## `JSONOptions`     {#JSONOptions}

<!--
**Appears in:**
-->
**出现在：**

- [FormatOptions](#FormatOptions)

<p>
<!--
JSONOptions contains options for logging format &quot;json&quot;.
-->
JSONOptions 包含为 &quot;json&quot; 日志格式提供的选项。
</p>

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr>
<td>
<code>OutputRoutingOptions</code> <B><!-- [Required] -->[必需]</B><br/>
<a href="#OutputRoutingOptions"><code>OutputRoutingOptions</code></a>
 </td>
<td>
<!--
(Members of <code>OutputRoutingOptions</code> are embedded into this type.)
   <span class="text-muted">No description provided.</span>
-->
（<code>OutputRoutingOptions</code> 的成员嵌入到此类型中。）
   <span class="text-muted">没有提供描述。</span>
</td>
</tr>
</tbody>
</table>

## `LogFormatFactory`     {#LogFormatFactory}

<p>
<!--
LogFormatFactory provides support for a certain additional,
non-default log format.
-->
LogFormatFactory 提供了对某些附加的、非默认的日志格式的支持。
</p>

## `LoggingConfiguration`     {#LoggingConfiguration}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)

<p>
<!--
LoggingConfiguration contains logging options.
-->
LoggingConfiguration 包含日志选项。
</p>

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>format</code> <B><!-- [Required] -->[必需]</B><br/>
<code>string</code>
</td>
<td>
  <p>
  <!--
  Format Flag specifies the structure of log messages.
default value of format is `text`
  -->
  <code>format<code> 设置日志消息的结构。默认的格式取值为 <code>text</code>。
  </p>
</td>
</tr>

<tr><td><code>flushFrequency</code> <B><!-- [Required] -->[必需]</B><br/>
<a href="#TimeOrMetaDuration"><code>TimeOrMetaDuration</code></a>
</td>
<td>
  <p>
  <!--
   Maximum time between log flushes.
If a string, parsed as a duration (i.e. &quot;1s&quot;)
If an int, the maximum number of nanoseconds (i.e. 1s = 1000000000).
Ignored if the selected logging backend writes log messages without buffering.
  -->
   日志清洗之间的最大时间间隔。
如果是字符串，则解析为持续时间（例如 "1s"）。
如果是整数，则表示为最大纳秒数（例如 1s = 1000000000）。
如果所选的日志后端在写入日志消息时未缓冲，则被忽略。
  </p>
</td>
</tr>

<tr><td><code>verbosity</code> <B><!-- [Required] -->[必需]</B><br/>
<a href="#VerbosityLevel"><code>VerbosityLevel</code></a>
</td>
<td>
  <p>
  <!--
  Verbosity is the threshold that determines which log messages are
logged. Default is zero which logs only the most important
messages. Higher values enable additional messages. Error messages
are always logged.
  -->
  <code>verbosity</code> 用来确定日志消息记录的详细程度阈值。默认值为 0，
意味着仅记录最重要的消息。数值越大，额外的消息越多。出错消息总是会被记录下来。
  </p>
</td>
</tr>

<tr><td><code>vmodule</code> <B><!-- [Required] -->[必需]</B><br/>
<a href="#VModuleConfiguration"><code>VModuleConfiguration</code></a>
</td>
<td>
  <p>
  <!--
  VModule overrides the verbosity threshold for individual files.
Only supported for &quot;text&quot; log format.
  -->
  <code>vmodule</code> 会在单个文件层面重载 verbosity 阈值的设置。
这一选项仅支持 &quot;text&quot; 日志格式。
  </p>
</td>
</tr>

<tr><td><code>options</code> <B><!-- [Required] -->[必需]</B><br/>
<a href="#FormatOptions"><code>FormatOptions</code></a>
</td>
<td>
  <p>
  <!--
  [Alpha] Options holds additional parameters that are specific
to the different logging formats. Only the options for the selected
format get used, but all of them get validated.
Only available when the LoggingAlphaOptions feature gate is enabled.
  -->
  [Alpha] <code>options</code> 中包含特定于不同日志格式的附加参数。
只有针对所选格式的选项会被使用，但是合法性检查时会查看所有参数。
只有 LoggingAlphaOptions 特性门控被启用时才可用。
  </p>
</td>
</tr>
</tbody>
</table>

## `LoggingOptions`     {#LoggingOptions}

<p>
<!--
LoggingOptions can be used with ValidateAndApplyWithOptions to override
certain global defaults.
-->
<code>LoggingOptions</code> 可以与 <code>ValidateAndApplyWithOptions</code> 一起使用，以覆盖某些全局默认值。
</p>

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>
      
<tr><td><code>ErrorStream</code> <B><!--[Required]-->[必需]</B><br/>
<a href="https://pkg.go.dev/io#Writer"><code>io.Writer</code></a>
</td>
<td>
   <p>
   <!--
   ErrorStream can be used to override the os.Stderr default.
   -->
   <code>ErrorStream</code> 可用于覆盖默认值 <code>os.Stderr</code>。
   </p>
</td>
</tr>
<tr><td><code>InfoStream</code> <B><!--[Required]-->[必需]</B><br/>
<a href="https://pkg.go.dev/io#Writer"><code>io.Writer</code></a>
</td>
<td>
   <p>
   <!--
   InfoStream can be used to override the os.Stdout default.
   -->
   <code>InfoStream</code> 可用于覆盖默认值 <code>os.Stdout</code>。
   </p>
</td>
</tr>
</tbody>
</table>

<!--
## `OutputRoutingOptions`     {#OutputRoutingOptions}

**Appears in:**
-->
## `OutputRoutingOptions`     {#OutputRoutingOptions}

- [JSONOptions](#JSONOptions)

- [TextOptions](#TextOptions)

<p>
<!--
OutputRoutingOptions contains options that are supported by both &quot;text&quot; and &quot;json&quot;.
-->
OutputRoutingOptions 包含 &quot;text&quot; 和 &quot;json&quot; 支持的选项。
</p>

<table class="table">
<thead><tr><th width="30%">Field</th><th><!--Description-->描述<</th></tr></thead>

<tbody>
<tr><td><code>splitStream</code> <B><!--[Required]-->[必需]</B><br/>
<code>bool</code>
</td>
<td>
<!--
   <p>[Alpha] SplitStream redirects error messages to stderr while
info messages go to stdout, with buffering. The default is to write
both to stdout, without buffering. Only available when
the LoggingAlphaOptions feature gate is enabled.</p>
-->
   <p>[Alpha] SplitStream 将错误消息重定向到 stderr，而信息消息则转到 stdout，并进行缓冲。
默认是将两者都写入 stdout，而不进行缓冲。仅在 LoggingAlphaOptions 特性门控启用时可用。</p>
</td>
</tr>
<tr>
<td><code>infoBufferSize</code> <B><!--[Required]-->[必需]</B><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/api/resource#QuantityValue"><code>k8s.io/apimachinery/pkg/api/resource.QuantityValue</code></a>
</td>
<td>
<!--
   <p>[Alpha] InfoBufferSize sets the size of the info stream when
using split streams. The default is zero, which disables buffering.
Only available when the LoggingAlphaOptions feature gate is enabled.</p>
-->
   <p>[Alpha] InfoBufferSize 设置使用分割流时信息流的大小。默认值为零，表示禁用缓冲。
仅在 LoggingAlphaOptions 特性门控启用时可用。</p>
</td>
</tr>
</tbody>
</table>

## `TextOptions`     {#TextOptions}

<!--
**Appears in:**
-->
**出现在：**

- [FormatOptions](#FormatOptions)

<p>
<!--
TextOptions contains options for logging format &quot;text&quot;.
-->
TextOptions 包含用于记录 &quot;text&quot; 格式的选项。
</p>

<table class="table">
<thead><tr><th width="30%">Field</th><th><!--Description-->描述</th></tr></thead>
<tbody>
    
<tr>
<td><code>OutputRoutingOptions</code> <B><!--[Required]-->[必需]</B><br/>
<a href="#OutputRoutingOptions"><code>OutputRoutingOptions</code></a>
</td>
<td>
<!--
(Members of <code>OutputRoutingOptions</code> are embedded into this type.)
   <span class="text-muted">No description provided.</span>
-->
（<code>OutputRoutingOptions</code> 的成员嵌入到此类型中。）
   <span class="text-muted">未提供描述。</span>
</td>
</tr>
</tbody>
</table>

## `TimeOrMetaDuration`     {#TimeOrMetaDuration}

<!--
**Appears in:**
-->
**出现在：**

- [LoggingConfiguration](#LoggingConfiguration)

<p>
<!--
TimeOrMetaDuration is present only for backwards compatibility for the
flushFrequency field, and new fields should use metav1.Duration.
-->
<code>TimeOrMetaDuration</code> 仅出于向后兼容 <code>flushFrequency<code> 字段而存在，
新字段应使用 <code>metav1.Duration<code>。
</p>

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>
    
<tr><td><code>Duration</code> <B><!--[Required]-->[必需]</B><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <p>
   <!--
   Duration holds the duration
   -->
   <code>Duration<code> 保存持续时间。
   </p>
</td>
</tr>
<tr><td><code>-</code> <B><!--[Required]-->[必需]</B><br/>
<code>bool</code>
</td>
<td>
   <p>
   <!--
   SerializeAsString controls whether the value is serialized as a string or an integer
   -->
   <code>SerializeAsString</code> 控制此值是以字符串还是以整数进行序列化。
   </p>
</td>
</tr>
</tbody>
</table>

## `TracingConfiguration`     {#TracingConfiguration}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)

<p>
<!--
TracingConfiguration provides versioned configuration for OpenTelemetry tracing clients.
-->
TracingConfiguration 为 OpenTelemetry 追踪客户端提供版本化的配置信息。
</p>

<table class="table">
<thead><tr><th width="30%">字段</th><th>描述</th></tr></thead>
<tbody>

<tr><td><code>endpoint</code><br/>
<code>string</code>
</td>
<td>
   <!--
   Endpoint of the collector this component will report traces to.
The connection is insecure, and does not currently support TLS.
Recommended is unset, and endpoint is the otlp grpc default, localhost:4317.
   -->
   <p>采集器的端点，此组件将向其报告追踪链路。
此连接不安全，目前不支持 TLS。推荐不设置，端点是 otlp grpc 默认值 localhost:4317。</p>
</td>
</tr>
<tr><td><code>samplingRatePerMillion</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   SamplingRatePerMillion is the number of samples to collect per million spans.
Recommended is unset. If unset, sampler respects its parent span's sampling
rate, but otherwise never samples.
   -->
   <p><code>samplingRatePerMillion</code> 是每百万 span 要采集的样本数。推荐不设置。
如果不设置，则采样器优先使用其父级 span 的采样率，否则不采样。</p>
</td>
</tr>
</tbody>
</table>

## `VModuleConfiguration`     {#VModuleConfiguration}

<!--
(Alias of `[]k8s.io/component-base/logs/api/v1.VModuleItem`)
-->
（`[]k8s.io/component-base/logs/api/v1.VModuleItem` 的别名）

<!--
**Appears in:**
-->
**出现在：**

- [LoggingConfiguration](#LoggingConfiguration)

<p>
<!--
VModuleConfiguration is a collection of individual file names or patterns
and the corresponding verbosity threshold.
-->
VModuleConfiguration 是一个集合，其中包含一个个文件名（或文件名模式）
及其对应的详细程度阈值。
</p>

## `VerbosityLevel`     {#VerbosityLevel}
    
<!--
(Alias of `uint32`)
-->
（`uint32` 的别名）

<!--
**Appears in:**
-->
**出现在：**

- [LoggingConfiguration](#LoggingConfiguration)

<p>
<!--
VerbosityLevel represents a klog or logr verbosity threshold.
-->
VerbosityLevel 表示 klog 或 logr 的详细程度（verbosity）阈值。
</p>

## `CredentialProviderConfig`     {#kubelet-config-k8s-io-v1beta1-CredentialProviderConfig}

<p>
<!--
CredentialProviderConfig is the configuration containing information about
each exec credential provider. Kubelet reads this configuration from disk and enables
each provider as specified by the CredentialProvider type.
-->
CredentialProviderConfig 包含有关每个 exec 凭据提供者的配置信息。
kubelet 从磁盘上读取这些配置信息，并根据 CredentialProvider 类型启用各个提供者。
</p>

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>apiVersion</code><br/>string</td><td><code>kubelet.config.k8s.io/v1beta1</code></td></tr>
<tr><td><code>kind</code><br/>string</td><td><code>CredentialProviderConfig</code></td></tr>

<tr><td><code>providers</code> <B><!--[Required]-->[必需]</B><br/>
<a href="#kubelet-config-k8s-io-v1beta1-CredentialProvider"><code>[]CredentialProvider</code></a>
</td>
<td>
<!--
providers is a list of credential provider plugins that will be enabled by the kubelet.
Multiple providers may match against a single image, in which case credentials
from all providers will be returned to the kubelet. If multiple providers are called
for a single image, the results are combined. If providers return overlapping
auth keys, the value from the provider earlier in this list is attempted first.
-->
   <p>
   <code>providers</code> 是一组凭据提供者插件，这些插件会被 kubelet 启用。
   多个提供者可以匹配到同一镜像上，这时，来自所有提供者的凭据信息都会返回给 kubelet。
   如果针对同一镜像调用了多个提供者，则结果会被组合起来。如果提供者返回的认证主键有重复，
   列表中先出现的提供者所返回的值将被首先尝试。
   </p>
</td>
</tr>
</tbody>
</table>

## `KubeletConfiguration`     {#kubelet-config-k8s-io-v1beta1-KubeletConfiguration}

<p>
<!--
KubeletConfiguration contains the configuration for the Kubelet
-->
KubeletConfiguration 中包含 kubelet 的配置。
</p>

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>apiVersion</code><br/>string</td><td><code>kubelet.config.k8s.io/v1beta1</code></td></tr>
<tr><td><code>kind</code><br/>string</td><td><code>KubeletConfiguration</code></td></tr>
<tr><td><code>enableServer</code> <B><!-- [Required] -->[必需]</B><br/>
<code>bool</code>
</td>
<td>
   <!--
   enableServer enables Kubelet's secured server.
Note: Kubelet's insecure port is controlled by the readOnlyPort option.
Default: true
   -->
  <p><code>enableServer</code> 会启用 kubelet 的安全服务器。</p>
  <p>注意：kubelet 的不安全端口由 <code>readOnlyPort</code> 选项控制。</p>
  <p>默认值：<code>true</code></p>
</td>
</tr>

<tr><td><code>staticPodPath</code><br/>
<code>string</code>
</td>
<td>
   <!--
   staticPodPath is the path to the directory containing local (static) pods to
run, or the path to a single static pod file.
Default: &quot;&quot;
   -->
  <p><code>staticPodPath</code> 是指向要运行的本地（静态）Pod 的目录，
或者指向某个静态 Pod 文件的路径。</p>
  <p>默认值：&quot;&quot;</p>
</td>
</tr>

<tr><td><code>podLogsDir</code><br/>
<code>string</code>
</td>
<td>
<!--
   <p>podLogsDir is a custom root directory path kubelet will use to place pod's log files.
Default: &quot;/var/log/pods/&quot;
Note: it is not recommended to use the temp folder as a log directory as it may cause
unexpected behavior in many places.</p>
-->
   <p>podLogsDir 是 kubelet 用于放置 Pod 日志文件的自定义根目录路径。
默认值：&quot;/var/log/pods/&quot;
注意：不建议使用临时文件夹作为日志目录，因为它可能会在许多地方引起意外行为。</p>
</td>
</tr>


<tr><td><code>syncFrequency</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   syncFrequency is the max period between synchronizing running
containers and config.
Default: &quot;1m&quot;
   -->
  <p><code>syncFrequency</code> 是对运行中的容器和配置进行同步的最长周期。</p>
  <p>默认值：&quot;1m&quot;</p>
</td>
</tr>

<tr><td><code>fileCheckFrequency</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   fileCheckFrequency is the duration between checking config files for
new data.
Default: &quot;20s&quot;
   -->
  <p><code>fileCheckFrequency</code> 是对配置文件中新数据进行检查的时间间隔值。</p>
  <p>默认值：&quot;20s&quot;</p>
</td>
</tr>

<tr><td><code>httpCheckFrequency</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
  <!--
   httpCheckFrequency is the duration between checking http for new data.
Default: &quot;20s&quot;
  -->
  <p><code>httpCheckFrequency</code> 是对 HTTP 服务器上新数据进行检查的时间间隔值。</p>
  <p>默认值：&quot;20s&quot;</p>
</td>
</tr>

<tr><td><code>staticPodURL</code><br/>
<code>string</code>
</td>
<td>
  <!--
  staticPodURL is the URL for accessing static pods to run.
Default: &quot;&quot;
  -->
  <p><code>staticPodURL</code> 是访问要运行的静态 Pod 的 URL 地址。
  <p>默认值：&quot;&quot;</p>
</td>
</tr>

<tr><td><code>staticPodURLHeader</code><br/>
<code>map[string][]string</code>
</td>
<td>
   <!--
   staticPodURLHeader is a map of slices with HTTP headers to use when accessing the podURL.
Default: nil
   -->
   <p><code>staticPodURLHeader</code>是一个由字符串组成的映射表，其中包含的 HTTP
头部信息用于访问<code>podURL</code>。</p>
  <p>默认值：nil</p>
</td>
</tr>

<tr><td><code>address</code><br/>
<code>string</code>
</td>
<td>
   <!--
   address is the IP address for the Kubelet to serve on (set to 0.0.0.0
for all interfaces).
Default: &quot;0.0.0.0&quot;
   -->
   <p><code>address</code> 是 kubelet 提供服务所用的 IP 地址（设置为 0.0.0.0
使用所有网络接口提供服务）。</p>
  <p>默认值：&quot;0.0.0.0&quot;</p>
</td>
</tr>

<tr><td><code>port</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   port is the port for the Kubelet to serve on.
The port number must be between 1 and 65535, inclusive.
Default: 10250
   -->
   <p><code>port</code> 是 kubelet 用来提供服务所使用的端口号。
这一端口号必须介于 1 到 65535 之间，包含 1 和 65535。</p>
  <p>默认值：10250</p>
</td>
</tr>

<tr><td><code>readOnlyPort</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   readOnlyPort is the read-only port for the Kubelet to serve on with
no authentication/authorization.
The port number must be between 1 and 65535, inclusive.
Setting this field to 0 disables the read-only service.
Default: 0 (disabled)
   -->
   <p><code>readOnlyPort</code> 是 kubelet 用来提供服务所使用的只读端口号。
此端口上的服务不支持身份认证或鉴权。这一端口号必须介于 1 到 65535 之间，
包含 1 和 65535。将此字段设置为 0 会禁用只读服务。</p>
   <p>默认值：0（禁用）</p>
</td>
</tr>

<tr><td><code>tlsCertFile</code><br/>
<code>string</code>
</td>
<td>
   <!--
   tlsCertFile is the file containing x509 Certificate for HTTPS. (CA cert,
if any, concatenated after server cert). If tlsCertFile and
tlsPrivateKeyFile are not provided, a self-signed certificate
and key are generated for the public address and saved to the directory
passed to the Kubelet's --cert-dir flag.
Default:&quot;quot;
  -->
  <p><code>tlsCertFile</code> 是包含 HTTPS 所需要的 x509 证书的文件
（如果有 CA 证书，会串接到服务器证书之后）。如果<code>tlsCertFile</code>
和 <code>tlsPrivateKeyFile</code> 都没有设置，则系统会为节点的公开地址生成自签名的证书和私钥，
并将其保存到 kubelet <code>--cert-dir</code> 参数所指定的目录下。</p>
  <p>默认值：&quot;&quot;</p>
</td>
</tr>

<tr><td><code>tlsPrivateKeyFile</code><br/>
<code>string</code>
</td>
<td>
   <!--
   tlsPrivateKeyFile is the file containing x509 private key matching tlsCertFile.
Default: &quot;&quot;
   -->
   <p><code>tlsPrivateKeyFile</code> 是一个包含与 <code>tlsCertFile</code>
证书匹配的 X509 私钥的文件。</p>
  <p>默认值：&quot;&quot;</p>
</td>
</tr>

<tr><td><code>tlsCipherSuites</code><br/>
<code>[]string</code>
</td>
<td>
   <!--
   tlsCipherSuites is the list of allowed cipher suites for the server.
   Note that TLS 1.3 ciphersuites are not configurable.
   Values are from tls package constants (https://golang.org/pkg/crypto/tls/#pkg-constants).
   Default: nil
   -->
   <p><code>tlsCipherSuites</code> 是一个字符串列表，其中包含服务器所接受的加密包名称。
   请注意，TLS 1.3 密码套件是不可配置的。
   列表中的每个值来自于 <code>tls</code> 包中定义的常数（https://golang.org/pkg/crypto/tls/#pkg-constants）。</p>
  <p>默认值：nil</p>
</td>
</tr>

<tr><td><code>tlsMinVersion</code><br/>
<code>string</code>
</td>
<td>
   <!--
   tlsMinVersion is the minimum TLS version supported.
Values are from tls package constants (https://golang.org/pkg/crypto/tls/#pkg-constants).
Default: &quot;&quot;
   -->
   <p><code>tlsMinVersion</code> 给出所支持的最小 TLS 版本。
字段取值来自于 <code>tls</code> 包中的常数定义（https://golang.org/pkg/crypto/tls/#pkg-constants）。</p>
  <p>默认值：&quot;&quot;</p>
</td>
</tr>

<tr><td><code>rotateCertificates</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   rotateCertificates enables client certificate rotation. The Kubelet will request a
new certificate from the certificates.k8s.io API. This requires an approver to approve the
certificate signing requests.
Default: false
   -->
   <p><code>rotateCertificates</code> 用来启用客户端证书轮换。kubelet 会调用
<code>certificates.k8s.io</code> API 来请求新的证书。需要有一个批复人批准证书签名请求。</p>
  <p>默认值：false</code>
</td>
</tr>

<tr><td><code>serverTLSBootstrap</code><br/>
<code>bool</code>
</td>
<td>
   <!--serverTLSBootstrap enables server certificate bootstrap. Instead of self
signing a serving certificate, the Kubelet will request a certificate from
the 'certificates.k8s.io' API. This requires an approver to approve the
certificate signing requests (CSR). The RotateKubeletServerCertificate feature
must be enabled when setting this field.
Default: false
   -->
   <p><code>serverTLSBootstrap</code> 用来启用服务器证书引导。系统不再使用自签名的服务证书，
kubelet 会调用 <code>certificates.k8s.io</code> API 来请求证书。
需要有一个批复人来批准证书签名请求（CSR）。
设置此字段时，<code>RotateKubeletServerCertificate</code> 特性必须被启用。</p>
  <p>默认值：false</p>
</td>
</tr>

<tr><td><code>authentication</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-KubeletAuthentication"><code>KubeletAuthentication</code></a>
</td>
<td>
   <!--
   authentication specifies how requests to the Kubelet's server are authenticated.
Defaults:
anonymous:
enabled: false
webhook:
enabled: true
cacheTTL: &quot;2m&quot;
   -->
   <p><code>authentication</code> 设置发送给 kubelet 服务器的请求是如何进行身份认证的。</p>
<p>默认值：</p>
<p><code>
anonymous:
  enabled: false
webhook:
  enabled: true
  cacheTTL: &quot;2m&quot;
</code></p>
</td>
</tr>

<tr><td><code>authorization</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-KubeletAuthorization"><code>KubeletAuthorization</code></a>
</td>
<td>
   <!--
   authorization specifies how requests to the Kubelet's server are authorized.
Defaults:
mode: Webhook
webhook:
cacheAuthorizedTTL: &quot;5m&quot;
cacheUnauthorizedTTL: &quot;30s&quot;
   -->
   <p><code>authorization</code> 设置发送给 kubelet 服务器的请求是如何进行鉴权的。</p>
<p>默认值：</p>
<p><code>
mode: Webhook
webhook:
  cacheAuthorizedTTL: &quot;5m&quot;
  cacheUnauthorizedTTL: &quot;30s&quot;
</code></p>
</td>
</tr>

<tr><td><code>registryPullQPS</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   registryPullQPS is the limit of registry pulls per second.
The value must not be a negative number.
Setting it to 0 means no limit.
Default: 5
   -->
   <p><code>registryPullQPS</code> 是每秒钟可以执行的镜像仓库拉取操作限值。
此值必须不能为负数。将其设置为 0 表示没有限值。</p>
  <p>默认值：5</code>
</td>
</tr>

<tr><td><code>registryBurst</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   registryBurst is the maximum size of bursty pulls, temporarily allows
pulls to burst to this number, while still not exceeding registryPullQPS.
The value must not be a negative number.
Only used if registryPullQPS is greater than 0.
Default: 10
   -->
   <p><code>registryBurst</code> 是突发性镜像拉取的上限值，允许镜像拉取临时上升到所指定数量，
不过仍然不超过 <code>registryPullQPS</code> 所设置的约束。此值必须是非负值。
只有 <code>registryPullQPS</code> 参数值大于 0 时才会使用此设置。</p>
  <p>默认值：10</p>
</td>
</tr>

<tr><td><code>imagePullCredentialsVerificationPolicy</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-ImagePullCredentialsVerificationPolicy"><code>ImagePullCredentialsVerificationPolicy</code></a>
</td>
<td>
   <p>
   <!--
   imagePullCredentialsVerificationPolicy determines how credentials should be
verified when pod requests an image that is already present on the node:
-->
<code>imagePullCredentialsVerificationPolicy</code> 决定当 Pod 请求节点上已存在的镜像时，凭据应被如何验证：
</p>
<ul>
<li>NeverVerify
<!--
anyone on a node can use any image present on the node
-->
节点上的任何人都可以使用该节点上存在的所有镜像
</li>
<li>NeverVerifyPreloadedImages
<!--
images that were pulled to the node by something else than the kubelet
can be used without reverifying pull credentials
-->
由 kubelet 以外的方式拉取到节点上的镜像可以在不重新验证凭据的情况下使用
</li>
<li>NeverVerifyAllowlistedImages
<!--
like &quot;NeverVerifyPreloadedImages&quot; but only node images from
<code>preloadedImagesVerificationAllowlist</code> don't require reverification
-->
类似于 &quot;NeverVerifyPreloadedImages&quot;，但只有源于
<code>preloadedImagesVerificationAllowlist</code> 的节点镜像无需重新验证
</li>
<li>AlwaysVerify
<!--
all images require credential reverification
-->
所有镜像都需要重新验证凭据
</li>
</ul>
</td>
</tr>
<tr><td><code>preloadedImagesVerificationAllowlist</code><br/>
<code>[]string</code>
</td>
<td>
   <p>
   <!--
   preloadedImagesVerificationAllowlist specifies a list of images that are
exempted from credential reverification for the &quot;NeverVerifyAllowlistedImages&quot;
<code>imagePullCredentialsVerificationPolicy</code>.
The list accepts a full path segment wildcard suffix &quot;/*&quot;.
Only use image specs without an image tag or digest.
-->
<code>preloadedImagesVerificationAllowlist</code> 指定一个镜像列表，对于
<code>imagePullCredentialsVerificationPolicy</code> 设置为
&quot;NeverVerifyAllowlistedImages&quot; 时，这些镜像可免于重新验证凭据。
此列表支持以 &quot;/*&quot; 结尾的路径通配符。请仅使用不带镜像标签或摘要的镜像规约。
</p>
</td>
</tr>

<tr><td><code>eventRecordQPS</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   eventRecordQPS is the maximum event creations per second. If 0, there
is no limit enforced. The value cannot be a negative number.
Default: 50
   -->
   <p><code>eventRecordQPS</code> 设置每秒钟可创建的事件个数上限。如果此值为 0，
则表示没有限制。此值不能设置为负数。</p>
  <p>默认值：50</p>
</td>
</tr>

<tr><td><code>eventBurst</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   eventBurst is the maximum size of a burst of event creations, temporarily
allows event creations to burst to this number, while still not exceeding
eventRecordQPS. This field canot be a negative number and it is only used
when eventRecordQPS &gt; 0.
Default: 100
   -->
   <p><code>eventBurst</code> 是突发性事件创建的上限值，允许事件创建临时上升到所指定数量，
不过仍然不超过 <code>eventRecordQPS</code>所设置的约束。此值必须是非负值，
且只有 <code>eventRecordQPS</code> &gt; 0 时才会使用此设置。</p>
  <p>默认值：100</p>
</td>
</tr>

<tr><td><code>enableDebuggingHandlers</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   enableDebuggingHandlers enables server endpoints for log access
and local running of containers and commands, including the exec,
attach, logs, and portforward features.
Default: true
   -->
   <p><code>enableDebuggingHandlers</code> 启用服务器上用来访问日志、
在本地运行容器和命令的端点，包括 <code>exec</code>、<code>attach</code>、
<code>logs</code> 和 <code>portforward</code> 等功能。</p>
  <p>默认值：true</p>
</td>
</tr>

<tr><td><code>enableContentionProfiling</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   enableContentionProfiling enables block profiling, if enableDebuggingHandlers is true.
Default: false
   -->
   <p><code>enableContentionProfiling</code> 用于启用阻塞性能分析，
仅用于 <code>enableDebuggingHandlers</code> 为 <code>true</code> 的场合。</p>
  <p>默认值：false</code>
</td>
</tr>

<tr><td><code>healthzPort</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   healthzPort is the port of the localhost healthz endpoint (set to 0 to disable).
A valid number is between 1 and 65535.
Default: 10248
   -->
   <p><code>healthzPort</code> 是本地主机上提供 <code>healthz</code> 端点的端口
（设置值为 0 时表示禁止）。合法值介于 1 和 65535 之间。</p>
  <p>默认值：10248</p>
</td>
</tr>

<tr><td><code>healthzBindAddress</code><br/>
<code>string</code>
</td>
<td>
   <!--
   healthzBindAddress is the IP address for the healthz server to serve on.
Default: &quot;127.0.0.1&quot;
   -->
   <p><code>healthzBindAddress<code> 是 <code>healthz</code> 服务器用来提供服务的 IP 地址。</p>
  <p>默认值：&quot;127.0.0.1&quot;</p>
</td>
</tr>

<tr><td><code>oomScoreAdj</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   oomScoreAdj is The oom-score-adj value for kubelet process. Values
must be within the range [-1000, 1000].
Default: -999
   -->
   <p><code>oomScoreAdj</code> 是为 kubelet 进程设置的 <code>oom-score-adj</code> 值。
所设置的取值要在 [-1000, 1000] 范围之内。</p>
   <p>默认值：-999</p>
</td>
</tr>

<tr><td><code>clusterDomain</code><br/>
<code>string</code>
</td>
<td>
   <!--
   clusterDomain is the DNS domain for this cluster. If set, kubelet will
configure all containers to search this domain in addition to the
host's search domains.
Default: &quot;&quot;
   -->
   <p><code>clusterDomain</code> 是集群的 DNS 域名。如果设置了此字段，kubelet
会配置所有容器，使之在搜索主机的搜索域的同时也搜索这里指定的 DNS 域。</p>
   <p>默认值：&quot;&quot;</p>
</td>
</tr>

<tr><td><code>clusterDNS</code><br/>
<code>[]string</code>
</td>
<td>
   <!--
   clusterDNS is a list of IP addresses for the cluster DNS server. If set,
kubelet will configure all containers to use this for DNS resolution
instead of the host's DNS servers.
Default: nil
  -->
  <p><code>clusterDNS</code> 是集群 DNS 服务器的 IP 地址的列表。
如果设置了，kubelet 将会配置所有容器使用这里的 IP 地址而不是宿主系统上的 DNS
服务器来完成 DNS 解析。
  <p>默认值：nil</p>
</td>
</tr>

<tr><td><code>streamingConnectionIdleTimeout</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <p>
   <!--
   streamingConnectionIdleTimeout is the maximum time a streaming connection
can be idle before the connection is automatically closed.
Deprecated: no longer has any effect.
Default: &quot;4h&quot;
   -->
   <code>streamingConnectionIdleTimeout</code> 设置流式连接在被自动关闭之前可以空闲的最长时间。
   弃用：此字段不再有作用。
   默认值：&quot;4h&quot;
   </p>
</td>
</tr>

<tr><td><code>nodeStatusUpdateFrequency</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   nodeStatusUpdateFrequency is the frequency that kubelet computes node
status. If node lease feature is not enabled, it is also the frequency that
kubelet posts node status to master.
Note: When node lease feature is not enabled, be cautious when changing the
constant, it must work with nodeMonitorGracePeriod in nodecontroller.
Default: &quot;10s&quot;
   -->
   <p><code>nodeStatusUpdateFrequency</code> 是 kubelet 计算节点状态的频率。
如果未启用节点租约特性，这一字段设置的也是 kubelet 向控制面投递节点状态的频率。</p>
   <p>注意：如果节点租约特性未被启用，更改此参数设置时要非常小心，
所设置的参数值必须与节点控制器的 <code>nodeMonitorGracePeriod</code> 协同。</p>
   <p>默认值：&quot;10s&quot;</p>
</td>
</tr>

<tr><td><code>nodeStatusReportFrequency</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   nodeStatusReportFrequency is the frequency that kubelet posts node
status to master if node status does not change. Kubelet will ignore this
frequency and post node status immediately if any change is detected. It is
only used when node lease feature is enabled. nodeStatusReportFrequency's
default value is 5m. But if nodeStatusUpdateFrequency is set explicitly,
nodeStatusReportFrequency's default value will be set to
nodeStatusUpdateFrequency for backward compatibility.
Default: &quot;5m&quot;
   -->
   <p><code>nodeStatusReportFrequency</code> 是节点状态未发生变化时，kubelet
向控制面更新节点状态的频率。如果节点状态发生变化，则 kubelet 会忽略这一频率设置，
立即更新节点状态。</p>
   <p>此字段仅当启用了节点租约特性时才被使用。<code>nodeStatusReportFrequency</code>
的默认值是&quot;5m&quot;。不过，如果 <code>nodeStatusUpdateFrequency</code>
被显式设置了，则 <code>nodeStatusReportFrequency</code> 的默认值会等于
<code>nodeStatusUpdateFrequency</code> 值，这是为了实现向后兼容。</p>
   <p>默认值：&quot;5m&quot;</p>
</td>
</tr>

<tr><td><code>nodeLeaseDurationSeconds</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   nodeLeaseDurationSeconds is the duration the Kubelet will set on its corresponding Lease.
NodeLease provides an indicator of node health by having the Kubelet create and
periodically renew a lease, named after the node, in the kube-node-lease namespace.
If the lease expires, the node can be considered unhealthy.
The lease is currently renewed every 10s, per KEP-0009. In the future, the lease renewal
interval may be set based on the lease duration.
The field value must be greater than 0.
Default: 40
   -->
   <p><code>nodeLeaseDurationSeconds</code> 是 kubelet 会在其对应的 Lease 对象上设置的时长值。
<code>NodeLease</code> 让 kubelet 来在 <code>kube-node-lease</code>
名字空间中创建按节点名称命名的租约并定期执行续约操作，并通过这种机制来了解节点健康状况。</p>
   <p>如果租约过期，则节点可被视作不健康。根据 KEP-0009 约定，目前的租约每 10 秒钟续约一次。
在将来，租约的续约时间间隔可能会根据租约的时长来设置。</p>
   <p>此字段的取值必须大于零。</p>
  <p>默认值：40</p>
</td>
</tr>

<tr><td><code>imageMinimumGCAge</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   imageMinimumGCAge is the minimum age for an unused image before it is
garbage collected. 
Default: &quot;2m&quot;
   -->
   <p><code>imageMinimumGCAge</code> 是对未使用镜像进行垃圾收集之前允许其存在的时长。</p>
   <p>默认值：&quot;2m&quot;</p>
</td>
</tr>

<tr>
<td>
<code>imageMaximumGCAge</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   imageMaximumGCAge is the maximum age an image can be unused before it is garbage collected.
The default of this field is &quot;0s&quot;, which disables this field--meaning images won't be garbage
collected based on being unused for too long.
Default: &quot;0s&quot; (disabled)
   -->
   <p><code>imageMaximumGCAge</code> 是对未使用镜像进行垃圾收集之前允许其存在的时长。
   此字段的默认值为 &quot;0s&quot;，表示禁用此字段，这意味着镜像不会因为过长时间不使用而被垃圾收集。</p>
   <p>默认值：&quot;0s&quot;（已禁用）</p>
</td>
</tr>

<tr><td><code>imageGCHighThresholdPercent</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   imageGCHighThresholdPercent is the percent of disk usage after which
image garbage collection is always run. The percent is calculated by
dividing this field value by 100, so this field must be between 0 and
100, inclusive. When specified, the value must be greater than
imageGCLowThresholdPercent.
Default: 85
   -->
   <p><code>imageGCHighThresholdPercent</code> 所给的是镜像的磁盘用量百分数，
一旦镜像用量超过此阈值，则镜像垃圾收集会一直运行。百分比是用这里的值除以 100
得到的，所以此字段取值必须介于 0 和 100 之间，包括 0 和 100。如果设置了此字段，
则取值必须大于 <code>imageGCLowThresholdPercent</code> 取值。</p>
   <p>默认值：85</p>
</td>
</tr>

<tr><td><code>imageGCLowThresholdPercent</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   imageGCLowThresholdPercent is the percent of disk usage before which
image garbage collection is never run. Lowest disk usage to garbage
collect to. The percent is calculated by dividing this field value by 100,
so the field value must be between 0 and 100, inclusive. When specified, the
value must be less than imageGCHighThresholdPercent.
Default: 80
   -->
   <p><code>imageGCLowThresholdPercent</code> 所给的是镜像的磁盘用量百分数，
镜像用量低于此阈值时不会执行镜像垃圾收集操作。垃圾收集操作也将此作为最低磁盘用量边界。
百分比是用这里的值除以 100 得到的，所以此字段取值必须介于 0 和 100 之间，包括 0 和 100。
如果设置了此字段，则取值必须小于 <code>imageGCHighThresholdPercent</code> 取值。</p>
   <p>默认值：80</p>
</td>
</tr>

<tr><td><code>volumeStatsAggPeriod</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   volumeStatsAggPeriod is the frequency for calculating and caching volume
disk usage for all pods.
Default: &quot;1m&quot;
   -->
   <p><code>volumeStatsAggPeriod</code> 是计算和缓存所有 Pod 磁盘用量的频率。</p>
   <p>默认值：&quot;1m&quot;</p>
</td>
</tr>

<tr><td><code>kubeletCgroups</code><br/>
<code>string</code>
</td>
<td>
   <!--
   kubeletCgroups is the absolute name of cgroups to isolate the kubelet in
Default: &quot;&quot;
   -->
   <p><code>kubeletCgroups</code> 是用来隔离 kubelet 的控制组（CGroup）的绝对名称。</p>
   <p>默认值：&quot;&quot;</p>
</td>
</tr>

<tr><td><code>systemCgroups</code><br/>
<code>string</code>
</td>
<td>
   <!--
   systemCgroups is absolute name of cgroups in which to place
all non-kernel processes that are not already in a container. Empty
for no container. Rolling back the flag requires a reboot.
The cgroupRoot must be specified if this field is not empty.
Default: &quot;&quot;
   -->
   <p><code>systemCgroups</code> 是用来放置那些未被容器化的、非内核的进程的控制组
（CGroup）的绝对名称。设置为空字符串表示没有这类容器。回滚此字段设置需要重启节点。
当此字段非空时，必须设置 <code>cgroupRoot</code> 字段。</p>
   <p>默认值：&quot;&quot;</p>
</td>
</tr>

<tr><td><code>cgroupRoot</code><br/>
<code>string</code>
</td>
<td>
   <!--
   cgroupRoot is the root cgroup to use for pods. This is handled by the
container runtime on a best effort basis.
   -->
   <p><code>cgroupRoot</code> 是用来运行 Pod 的控制组（CGroup）。
容器运行时会尽可能处理此字段的设置值。</p>
</td>
</tr>

<tr><td><code>cgroupsPerQOS</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   cgroupsPerQOS enable QoS based CGroup hierarchy: top level CGroups for QoS classes
and all Burstable and BestEffort Pods are brought up under their specific top level
QoS CGroup.
Default: true
   -->
   <p><code>cgroupsPerQOS</code> 用来启用基于 QoS 的控制组（CGroup）层次结构：
顶层的控制组用于不同 QoS 类，所有 <code>Burstable</code> 和 <code>BestEffort</code> Pod
都会被放置到对应的顶级 QoS 控制组下。</p>
   <p>默认值：true</p>
</td>
</tr>

<tr><td><code>cgroupDriver</code><br/>
<code>string</code>
</td>
<td>
   <!--
   cgroupDriver is the driver kubelet uses to manipulate CGroups on the host (cgroupfs
or systemd).
Default: &quot;cgroupfs&quot;
   -->
   <p><code>cgroupDriver</code> 是 kubelet 用来操控宿主系统上控制组（CGroup）
的驱动程序（cgroupfs 或 systemd）。</p>
   <p>默认值：&quot;cgroupfs&quot;</p>
</td>
</tr>

<tr><td><code>cpuManagerPolicy</code><br/>
<code>string</code>
</td>
<td>
   <!--
   cpuManagerPolicy is the name of the policy to use.
Default: &quot;None&quot;
   -->
   <p><code>cpuManagerPolicy</code> 是要使用的策略名称。</p>
   <p>默认值：&quot;None&quot;</p>
</td>
</tr>

<tr><td><code>singleProcessOOMKill</code><br/>
<code>bool</code>
</td>
<td>
   <p>
   <!--
   singleProcessOOMKill, if true, will prevent the <code>memory.oom.group</code> flag from being set for container
cgroups in cgroups v2. This causes processes in the container to be OOM killed individually instead of as
a group. It means that if true, the behavior aligns with the behavior of cgroups v1.
The default value is determined automatically when you don't specify.
On non-linux such as windows, only null / absent is allowed.
On cgroup v1 linux, only null / absent and true are allowed.
On cgroup v2 linux, null / absent, true and false are allowed. The default value is false.
-->
如果 <code>singleProcessOOMKill</code> 为 true，将阻止在 cgroup v2 中为容器 cgroup
设置 <code>memory.oom.group</code> 标志。
这会导致容器中的单个进程因 OOM 被单独杀死，而不是作为一个组被杀死。
这意味着如果为 true，其行为与 cgroup v1 的行为一致。
当你未指定值时，默认值将被自动确定。
在 Windows 这类非 Linux 系统上，仅允许 null（或不设置）。
在 cgroup v1 Linux 上，仅允许 null（或不设置）和 true。
在 cgroup v2 Linux 上，允许 null（或不设置）、true 和 false。默认值为 false。
</p>
</td>
</tr>

<tr><td><code>cpuManagerPolicyOptions</code><br/>
<code>map[string]string</code>
</td>
<td>
   <!--
   cpuManagerPolicyOptions is a set of key=value which 	allows to set extra options
to fine tune the behaviour of the cpu manager policies.
Default: nil
   -->
   <p><code>cpuManagerPolicyOptions</code> 是一组 <code>key=value</code> 键值映射，
容许通过额外的选项来精细调整 CPU 管理器策略的行为。</p>
   <p>默认值：nil</p>
</td>
</tr>

<tr><td><code>cpuManagerReconcilePeriod</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   cpuManagerReconcilePeriod is the reconciliation period for the CPU Manager.
Default: &quot;10s&quot;
   -->
   <p><code>cpuManagerReconcilePeriod</code> 是 CPU 管理器的协调周期时长。
默认值：&quot;10s&quot;</p>
</td>
</tr>

<tr><td><code>memoryManagerPolicy</code><br/>
<code>string</code>
</td>
<td>
   <!--
   memoryManagerPolicy is the name of the policy to use by memory manager.
Requires the MemoryManager feature gate to be enabled.
Default: &quot;none&quot;
   -->
   <p><code>memoryManagerPolicy</code> 是内存管理器要使用的策略的名称。
要求启用 <code>MemoryManager</code> 特性门控。</p>
   <p>默认值：&quot;none&quot;</p>
</td>
</tr>

<tr><td><code>topologyManagerPolicy</code><br/>
<code>string</code>
</td>
<td>
  <!--
   <p>topologyManagerPolicy is the name of the topology manager policy to use.
Valid values include:</p>
<ul>
<li><code>restricted</code>: kubelet only allows pods with optimal NUMA node alignment for
requested resources;</li>
<li><code>best-effort</code>: kubelet will favor pods with NUMA alignment of CPU and device
resources;</li>
<li><code>none</code>: kubelet has no knowledge of NUMA alignment of a pod's CPU and device resources.</li>
<li><code>single-numa-node</code>: kubelet only allows pods with a single NUMA alignment
of CPU and device resources.</li>
</ul>
<p>Default: &quot;none&quot;</p>
  -->
   <p><code>topologyManagerPolicy</code> 是要使用的拓扑管理器策略名称。合法值包括：</p> 
   <ul>
    <li><code>restricted</code>：kubelet 仅接受在所请求资源上实现最佳 NUMA 对齐的 Pod。</li>
    <li><code>best-effort</code>：kubelet 会优选在 CPU 和设备资源上实现 NUMA 对齐的 Pod。</li>
    <li><code>none</code>：kubelet 不了解 Pod CPU 和设备资源 NUMA 对齐需求。</li>
    <li><code>single-numa-node</code>：kubelet 仅允许在 CPU 和设备资源上对齐到同一 NUMA 节点的 Pod。</li>
   </ul>
   <p>默认值：&quot;none&quot;</p>
</td>
</tr>

<tr><td><code>topologyManagerScope</code><br/>
<code>string</code>
</td>
<td>
   <!--
   <p>topologyManagerScope represents the scope of topology hint generation
that topology manager requests and hint providers generate. Valid values include:</p>
<ul>
<li><code>container</code>: topology policy is applied on a per-container basis.</li>
<li><code>pod</code>: topology policy is applied on a per-pod basis.</li>
</ul>
<p>Default: &quot;container&quot;</p>
   -->
   <p><code>topologyManagerScope</code> 代表的是拓扑提示生成的范围，
拓扑提示信息由提示提供者生成，提供给拓扑管理器。合法值包括：</p>
   <ul>
    <li><code>container</code>：拓扑策略是按每个容器来实施的。</li>
    <li><code>pod</code>：拓扑策略是按每个 Pod 来实施的。</li>
   </ul>
   <p>默认值：&quot;container&quot;</p>
</td>
</tr>

<tr><td><code>topologyManagerPolicyOptions</code><br/>
<code>map[string]string</code>
</td>
<td>
   <!--
   <p>TopologyManagerPolicyOptions is a set of key=value which allows to set extra options
to fine tune the behaviour of the topology manager policies.
Requires  both the &quot;TopologyManager&quot; and &quot;TopologyManagerPolicyOptions&quot; feature gates to be enabled.
Default: nil</p>
   -->
   <p>TopologyManagerPolicyOptions 是一组 key=value 键值映射，容许设置额外的选项来微调拓扑管理器策略的行为。
需要同时启用 &quot;TopologyManager&quot; 和 &quot;TopologyManagerPolicyOptions&quot; 特性门控。
默认值：nil</p>
</td>
</tr>

<tr><td><code>qosReserved</code><br/>
<code>map[string]string</code>
</td>
<td>
   <!--
   qosReserved is a set of resource name to percentage pairs that specify
the minimum percentage of a resource reserved for exclusive use by the
guaranteed QoS tier.
Currently supported resources: &quot;memory&quot;
Requires the QOSReserved feature gate to be enabled.
Default: nil
   -->
   <p><code>qosReserved</code> 是一组从资源名称到百分比值的映射，用来为 <code>Guaranteed</code>
QoS 类型的负载预留供其独占使用的资源百分比。目前支持的资源为：&quot;memory&quot;。
需要启用 <code>QOSReserved</code> 特性门控。</p>
   <p>默认值：nil</p>
</td>
</tr>

<tr><td><code>runtimeRequestTimeout</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   runtimeRequestTimeout is the timeout for all runtime requests except long running
requests - pull, logs, exec and attach.
Default: &quot;2m&quot;
   -->
   <p><code>runtimeRequestTimeout</code> 用来设置除长期运行的请求（<code>pull</code>、
<code>logs</code>、<code>exec</code> 和 <code>attach</code>）之外所有运行时请求的超时时长。</p>
   <p>默认值：&quot;2m&quot;</p>
</td>
</tr>

<tr><td><code>hairpinMode</code><br/>
<code>string</code>
</td>
<td>
   <!--
   <p>hairpinMode specifies how the Kubelet should configure the container
bridge for hairpin packets.
Setting this flag allows endpoints in a Service to loadbalance back to
themselves if they should try to access their own Service. Values:</p>
   -->
   <p><code>hairpinMode</code> 设置 kubelet 如何为发夹模式数据包配置容器网桥。
设置此字段可以让 Service 中的端点在尝试访问自身 Service 时将服务请求路由的自身。
可选值有：</p>
   <!--
<li>&quot;promiscuous-bridge&quot;: make the container bridge promiscuous.</li>
<li>&quot;hairpin-veth&quot;:       set the hairpin flag on container veth interfaces.</li>
<li>&quot;none&quot;:               do nothing.</li>
   -->
   <ul>
    <li>&quot;promiscuous-bridge&quot;：将容器网桥设置为混杂模式。</li>
    <li>&quot;hairpin-veth&quot;：在容器的 veth 接口上设置发夹模式标记。</li>
    <li>&quot;none&quot;：什么也不做。</li>
   </ul>
   <!--
   Generally, one must set <code>--hairpin-mode=hairpin-veth to</code> achieve hairpin NAT,
because promiscuous-bridge assumes the existence of a container bridge named cbr0.
Default: &quot;promiscuous-bridge&quot;
   -->
   <p>一般而言，用户必须设置 <code>--hairpin-mode=hairpin-veth</code> 才能实现发夹模式的网络地址转译
（NAT），因为混杂模式的网桥要求存在一个名为 <code>cbr0</code> 的容器网桥。</p>
   <p>默认值：&quot;promiscuous-bridge&quot;</p>
</td>
</tr>

<tr><td><code>maxPods</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   maxPods is the maximum number of Pods that can run on this Kubelet.
The value must be a non-negative integer.
Default: 110
   -->
   <p><code>maxPods</code> 是此 kubelet 上课运行的 Pod 个数上限。此值必须为非负整数。</p>
   <p>默认值：110</p>
</td>
</tr>

<tr><td><code>podCIDR</code><br/>
<code>string</code>
</td>
<td>
   <!--
   podCIDR is the CIDR to use for pod IP addresses, only used in standalone mode.
In cluster mode, this is obtained from the control plane.
Default: &quot;&quot;
   -->
   <p><code>podCIDR</code> 是用来设置 Pod IP 地址的 CIDR 值，仅用于独立部署模式。
运行于集群模式时，这一数值会从控制面获得。</p>
   <p>默认值：&quot;&quot;</p>
</td>
</tr>

<tr><td><code>podPidsLimit</code><br/>
<code>int64</code>
</td>
<td>
   <!--
   podPidsLimit is the maximum number of PIDs in any pod.
Default: -1
   -->
   <p><code>podPidsLimit</code> 是每个 Pod 中可使用的 PID 个数上限。</p>
   <p>默认值：-1</p>
</td>
</tr>

<tr><td><code>resolvConf</code><br/>
<code>string</code>
</td>
<td>
   <!--
   resolvConf is the resolver configuration file used as the basis
for the container DNS resolution configuration.
If set to the empty string, will override the default and effectively disable DNS lookups.
Default: &quot;/etc/resolv.conf&quot;
   -->
   <p><code>resolvConf</code> 是一个域名解析配置文件，用作容器 DNS 解析配置的基础。</p>
   <p>如果此值设置为空字符串，则会覆盖 DNS 解析的默认配置，本质上相当于禁用了 DNS 查询。</p>
   <p>默认值：&quot;/etc/resolv.conf&quot;</p>
</td>
</tr>

<tr><td><code>runOnce</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   runOnce causes the Kubelet to check the API server once for pods,
run those in addition to the pods specified by static pod files, and exit.
Default: false
   -->
   <p><code>runOnce</code> 字段被设置时，kubelet 会咨询 API 服务器一次并获得 Pod 列表，
运行在静态 Pod 文件中指定的 Pod 及这里所获得的 Pod，然后退出。</p>
   <p>默认值：false</p>
</td>
</tr>

<tr><td><code>cpuCFSQuota</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   cpuCFSQuota enables CPU CFS quota enforcement for containers that
specify CPU limits.
Default: true
   -->
   <p><code>cpuCFSQuota</code> 允许为设置了 CPU 限制的容器实施 CPU CFS 配额约束。</p>
   <p>默认值：true</p>
</td>
</tr>

<tr><td><code>cpuCFSQuotaPeriod</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   cpuCFSQuotaPeriod is the CPU CFS quota period value, <code>cpu.cfs_period_us</code>.
The value must be between 1 ms and 1 second, inclusive.
Requires the CustomCPUCFSQuotaPeriod feature gate to be enabled.
Default: &quot;100ms&quot;
   -->
   <p><code>cpuCFSQuotaPeriod</code> 设置 CPU CFS 配额周期值，<code>cpu.cfs_period_us</code>。
此值需要介于 1 毫秒和 1 秒之间，包含 1 毫秒和 1 秒。
此功能要求启用 <code>CustomCPUCFSQuotaPeriod</code> 特性门控被启用。</p>
   <p>默认值：&quot;100ms&quot;</p>
</td>
</tr>

<tr><td><code>nodeStatusMaxImages</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   nodeStatusMaxImages caps the number of images reported in Node.status.images.
The value must be greater than -2.
Note: If -1 is specified, no cap will be applied. If 0 is specified, no image is returned.
Default: 50
   -->
   <p><code>nodeStatusMaxImages</code> 限制 <code>Node.status.images</code> 中报告的镜像数量。
此值必须大于 -2。</p>
   <p>注意：如果设置为 -1，则不会对镜像数量做限制；如果设置为 0，则不会返回任何镜像。</p>
   <p>默认值：50</p>
</td>
</tr>

<tr><td><code>maxOpenFiles</code><br/>
<code>int64</code>
</td>
<td>
   <!--
   maxOpenFiles is Number of files that can be opened by Kubelet process.
The value must be a non-negative number.
Default: 1000000
   -->
   <p><code>maxOpenFiles</code> 是 kubelet 进程可以打开的文件个数。此值必须不能为负数。</p>
   <p>默认值：1000000</p>
</td>
</tr>

<tr><td><code>contentType</code><br/>
<code>string</code>
</td>
<td>
   <!--
   contentType is contentType of requests sent to apiserver.
Default: &quot;application/vnd.kubernetes.protobuf&quot;
   -->
   <p><code>contentType</code> 是向 API 服务器发送请求时使用的内容类型。</p>
   <p>默认值：&quot;application/vnd.kubernetes.protobuf&quot;</p>
</td>
</tr>

<tr><td><code>kubeAPIQPS</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   kubeAPIQPS is the QPS to use while talking with kubernetes apiserver.
Default: 50
   -->
   <p><code>kubeAPIQPS</code> 设置与 Kubernetes API 服务器通信时要使用的 QPS（每秒查询数）。</p>
   <p>默认值：50</p>
</td>
</tr>

<tr><td><code>kubeAPIBurst</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   kubeAPIBurst is the burst to allow while talking with kubernetes API server.
This field cannot be a negative number.
Default: 100
   -->
   <p><code>kubeAPIBurst</code> 设置与 Kubernetes API 服务器通信时突发的流量级别。
此字段取值不可以是负数。</p>
   <p>默认值：100</p>
</td>
</tr>

<tr><td><code>serializeImagePulls</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   serializeImagePulls when enabled, tells the Kubelet to pull images one
at a time. We recommend <em>not</em> changing the default value on nodes that
run docker daemon with version  &lt; 1.9 or an Aufs storage backend.
Issue #10959 has more details.
Default: true
   -->
   <p><code>serializeImagePulls</code> 被启用时会通知 kubelet 每次仅拉取一个镜像。
我们建议<em>不要</em>在所运行的 Docker 守护进程版本低于 1.9、使用 aufs
存储后端的节点上更改默认值。详细信息可参见 Issue #10959。</p>
   <p>默认值：true</p>
</td>
</tr>

<tr><td><code>maxParallelImagePulls</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   MaxParallelImagePulls sets the maximum number of image pulls in parallel.
This field cannot be set if SerializeImagePulls is true.
Setting it to nil means no limit.
Default: nil
   -->
   <p><code>maxParallelImagePulls</code> 设置并行拉取镜像的最大数量。
如果 <code>serializeImagePulls</code> 为 true，则无法设置此字段。
把它设置为 nil 意味着没有限制。</p>
   <p>默认值：nil</p>
</td>
</tr>
<tr><td><code>evictionHard</code><br/>
<code>map[string]string</code>
</td>
<td>
   <!--
   evictionHard is a map of signal names to quantities that defines hard eviction
thresholds. For example: <code>{&quot;memory.available&quot;: &quot;300Mi&quot;}</code>.
To explicitly disable, pass a 0% or 100% threshold on an arbitrary resource.
Default:
   memory.available:  &quot;100Mi&quot;
   nodefs.available:  &quot;10%&quot;
   nodefs.inodesFree: &quot;5%&quot;
   imagefs.available: &quot;15%&quot;
   -->
   <p><code>evictionHard</code> 是一个映射，是从信号名称到定义硬性驱逐阈值的映射。
例如：<code>{&quot;memory.available&quot;: &quot;300Mi&quot;}</code>。
如果希望显式地禁用，可以在任意资源上将其阈值设置为 0% 或 100%。</p>
   <p>默认值：</p>
   <code><pre>
   memory.available:  &quot;100Mi&quot;
   nodefs.available:  &quot;10%&quot;
   nodefs.inodesFree: &quot;5%&quot;
   imagefs.available: &quot;15%&quot;
  </pre></code>
</td>
</tr>

<tr><td><code>evictionSoft</code><br/>
<code>map[string]string</code>
</td>
<td>
   <!--
   evictionSoft is a map of signal names to quantities that defines soft eviction thresholds.
For example: <code>{&quot;memory.available&quot;: &quot;300Mi&quot;}</code>.
Default: nil
   -->
   <p><code>evictionSoft</code> 是一个映射，是从信号名称到定义软性驱逐阈值的映射。
例如：<code>{&quot;memory.available&quot;: &quot;300Mi&quot;}</code>。</p>
   <p>默认值：nil</p>
</td>
</tr>

<tr><td><code>evictionSoftGracePeriod</code><br/>
<code>map[string]string</code>
</td>
<td>
   <!--
   evictionSoftGracePeriod is a map of signal names to quantities that defines grace
periods for each soft eviction signal. For example: <code>{&quot;memory.available&quot;: &quot;30s&quot;}</code>.
Default: nil
   -->
   <p><code>evictionSoftGracePeriod</code> 是一个映射，是从信号名称到每个软性驱逐信号的宽限期限。
例如：<code>{&quot;memory.available&quot;: &quot;30s&quot;}</code>。</p>
   <p>默认值：nil</p>
</td>
</tr>

<tr><td><code>evictionPressureTransitionPeriod</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   evictionPressureTransitionPeriod is the duration for which the kubelet has to wait
before transitioning out of an eviction pressure condition.
A duration of 0s will be converted to the default value of 5m
Default: &quot;5m&quot;
   -->
   <p><code>evictionPressureTransitionPeriod</code> 设置 kubelet
离开驱逐压力状况之前必须要等待的时长。0s 的时长将被转换为默认值 5m。</p>
   <p>默认值：&quot;5m&quot;</p>
</td>
</tr>

<tr><td><code>evictionMaxPodGracePeriod</code><br/>
<code>int32</code>
</td>
<td>
<p>
<!--
evictionMaxPodGracePeriod is the maximum allowed grace period (in seconds) to use
when terminating pods in response to a soft eviction threshold being met. This value
effectively caps the Pod's terminationGracePeriodSeconds value during soft evictions. 
The pod's effective grace period is calculated as:
min(evictionMaxPodGracePeriod, pod.terminationGracePeriodSeconds).
Note: A negative value will cause pods to be terminated immediately, as if the value was 0.
Default: 0
-->
<code>evictionMaxPodGracePeriod</code> 是指达到软性逐出阈值而引起 Pod 终止时，
可以赋予的宽限期限最大值（按秒计）。这个值本质上限制了软性逐出事件发生时，
Pod 可以获得的 <code>terminationGracePeriodSeconds</code>。
Pod 的有效宽限期计算为：
min(evictionMaxPodGracePeriod, pod.terminationGracePeriodSeconds)。
注意：负值将导致 Pod 立即被终止，就如同该值为 0 一样。
默认值：0
</p>
</td>
</tr>

<tr><td><code>evictionMinimumReclaim</code><br/>
<code>map[string]string</code>
</td>
<td>
   <!--
   evictionMinimumReclaim is a map of signal names to quantities that defines minimum reclaims,
which describe the minimum amount of a given resource the kubelet will reclaim when
performing a pod eviction while that resource is under pressure.
For example: <code>{&quot;imagefs.available&quot;: &quot;2Gi&quot;}</code>.
Default: nil
   -->
   <p><code>evictionMinimumReclaim</code> 是一个映射，定义信号名称与最小回收量数值之间的关系。
最小回收量指的是资源压力较大而执行 Pod 驱逐操作时，kubelet 对给定资源的最小回收量。
例如：<code>{&quot;imagefs.available&quot;: &quot;2Gi&quot;}</code>。</p>
   <p>默认值：nil</p>
</td>
</tr>

<tr><td><code>mergeDefaultEvictionSettings</code><br/>
<code>bool</code>
</td>
<td>
   <p>
   <!--
   mergeDefaultEvictionSettings indicates that defaults for the evictionHard, evictionSoft, evictionSoftGracePeriod, and evictionMinimumReclaim
fields should be merged into values specified for those fields in this configuration.
Signals specified in this configuration take precedence.
Signals not specified in this configuration inherit their defaults.
If false, and if any signal is specified in this configuration then other signals that
are not specified in this configuration will be set to 0.
It applies to merging the fields for which the default exists, and currently only evictionHard has default values.
Default: false
-->
<code>mergeDefaultEvictionSettings</code> 表示是否应将 evictionHard、evictionSoft、
evictionSoftGracePeriod 和 evictionMinimumReclaim 字段的默认值合并到此配置中为这些字段指定的取值中。
在此配置中显式指定的信号优先生效。未在此配置中指定的信号将继承其默认值。
如果设置为 false，并且此配置中指定了任一信号，则此配置中未指定的其他信号将被设置为 0。
此字段适用于合并存在默认值的字段，目前仅 evictionHard 有默认值。
默认值：false。
</p>
</td>
</tr>

<tr><td><code>podsPerCore</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   podsPerCore is the maximum number of pods per core. Cannot exceed maxPods.
The value must be a non-negative integer.
If 0, there is no limit on the number of Pods.
Default: 0
   -->
   <p><code>podsPerCore</code> 设置的是每个核上 Pod 个数上限。此值不能超过 <code>maxPods</code>。
所设值必须是非负整数。如果设置为 0，则意味着对 Pod 个数没有限制。</p>
   <p>默认值：0</p>
</td>
</tr>

<tr><td><code>enableControllerAttachDetach</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   enableControllerAttachDetach enables the Attach/Detach controller to
manage attachment/detachment of volumes scheduled to this node, and
disables kubelet from executing any attach/detach operations.
Note: attaching/detaching CSI volumes is not supported by the kubelet,
so this option needs to be true for that use case.
Default: true
   -->
   <p><code>enableControllerAttachDetach</code> 用来允许 Attach/Detach
控制器管理调度到本节点的卷的挂接（attachment）和解除挂接（detachement），
并且禁止 kubelet 执行任何 attach/detach 操作。</p>
   <p>注意：kubelet 不支持挂接 CSI 卷和解除挂接，
因此对于该用例，此选项必须为 true。</p>
   <p>默认值：true</p>
</td>
</tr>

<tr><td><code>protectKernelDefaults</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   protectKernelDefaults, if true, causes the Kubelet to error if kernel
flags are not as it expects. Otherwise the Kubelet will attempt to modify
kernel flags to match its expectation.
Default: false
   -->
   <p><code>protectKernelDefaults</code> 设置为 <code>true</code> 时，会令 kubelet
在发现内核参数与预期不符时出错退出。若此字段设置为 <code>false</code>，则 kubelet
会尝试更改内核参数以满足其预期。</p>
   <p>默认值：false</p>
</td>
</tr>

<tr><td><code>makeIPTablesUtilChains</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   makeIPTablesUtilChains, if true, causes the Kubelet to create the
KUBE-IPTABLES-HINT chain in iptables as a hint to other components about the
configuration of iptables on the system.
Default: true
   -->
   <p><code>makeIPTablesUtilChains</code> 设置为 <code>true</code> 时，相当于允许 kubelet
在 iptables 中创建 KUBE-IPTABLES-HINT 链，提示其他组件有关系统上 iptables 的配置。</p>
   <p>默认值：true</p>
</td>
</tr>

<tr><td><code>iptablesMasqueradeBit</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   iptablesMasqueradeBit formerly controlled the creation of the KUBE-MARK-MASQ
chain.
Deprecated: no longer has any effect.
Default: 14
   -->
   <p><code>iptablesMasqueradeBit</code> 以前用于控制 KUBE-MARK-MASQ 链的创建。</p>
   <p>已弃用：不再有任何效果。</p>
   <p>默认值：14</p>
</td>
</tr>

<tr><td><code>iptablesDropBit</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   iptablesDropBit formerly controlled the creation of the KUBE-MARK-DROP chain.
Deprecated: no longer has any effect.
Default: 15
   -->
   <p><code>iptablesDropBit</code> 以前用于控制 KUBE-MARK-DROP 链的创建。</p>
   <p>已弃用：不再有任何效果。</p>
   <p>默认值：15</p>
</td>
</tr>

<tr><td><code>featureGates</code><br/>
<code>map[string]bool</code>
</td>
<td>
   <!--
   featureGates is a map of feature names to bools that enable or disable experimental
features. This field modifies piecemeal the built-in default values from
&quot;k8s.io/kubernetes/pkg/features/kube_features.go&quot;.
Default: nil
   -->
   <p><code>featureGates</code> 是一个从功能特性名称到布尔值的映射，用来启用或禁用实验性的功能。
此字段可逐条更改文件 &quot;k8s.io/kubernetes/pkg/features/kube_features.go&quot;
中所给的内置默认值。</p>
   <p>默认值：nil</p>
</td>
</tr>

<tr><td><code>failSwapOn</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   failSwapOn tells the Kubelet to fail to start if swap is enabled on the node.
Default: true
   -->
   <p><code>failSwapOn</code> 通知 kubelet 在节点上启用交换分区时拒绝启动。</p>
   <p>默认值：true</p>
</td>
</tr>

<tr><td><code>memorySwap</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-MemorySwapConfiguration"><code>MemorySwapConfiguration</code></a>
</td>
<td>
   <!--
   memorySwap configures swap memory available to container workloads.
   -->
   <p><code>memorySwap</code> 配置容器负载可用的交换内存。</p>
</td>
</tr>

<tr><td><code>containerLogMaxSize</code><br/>
<code>string</code>
</td>
<td>
   <!--
   containerLogMaxSize is a quantity defining the maximum size of the container log
file before it is rotated. For example: &quot;5Mi&quot; or &quot;256Ki&quot;.
Default: &quot;10Mi&quot;
   -->
   <p><code>containerLogMaxSize</code> 是定义容器日志文件被轮转之前可以到达的最大尺寸。
例如：&quot;5Mi&quot; 或 &quot;256Ki&quot;。</p>
   <p>默认值：&quot;10Mi&quot;</p>
</td>
</tr>

<tr><td><code>containerLogMaxFiles</code><br/>
<code>int32</code>
</td>
<td>
   <!--
   containerLogMaxFiles specifies the maximum number of container log files that can
be present for a container.
Default: 5
   -->
   <p><code>containerLogMaxFiles</code> 设置每个容器可以存在的日志文件个数上限。</p>
   <p>默认值：&quot;5&quot;</p>
</td>
</tr>

<tr><td><code>containerLogMaxWorkers</code><br/>
<code>int32</code>
</td>
<td>
<!--
   <p>ContainerLogMaxWorkers specifies the maximum number of concurrent workers to spawn
for performing the log rotate operations. Set this count to 1 for disabling the
concurrent log rotation workflows
Default: 1</p>
-->
   <p><code>containerLogMaxWorkers</code> 指定执行日志轮换操作所需的并发工作程序的最大数量。
将此计数设置为 1，以禁用并发日志轮换工作流程。
默认值：1</p>
</td>
</tr>
<tr>
<td><code>containerLogMonitorInterval</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
<!--
   <p>ContainerLogMonitorInterval specifies the duration at which the container logs are monitored
for performing the log rotate operation. This defaults to 10 * time.Seconds. But can be
customized to a smaller value based on the log generation rate and the size required to be
rotated against
Default: 10s</p>
-->
   <p><code>containerLogMonitorInterval</code> 指定监视容器日志以执行日志轮转操作的持续时间。
默认为 10s，但可以根据日志生成率和需要轮换的大小定制为较小的值。
默认值：10s
</p>
</td>
</tr>

<tr><td><code>configMapAndSecretChangeDetectionStrategy</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-ResourceChangeDetectionStrategy"><code>ResourceChangeDetectionStrategy</code></a>
</td>
<td>
   <!--
   <p>configMapAndSecretChangeDetectionStrategy is a mode in which ConfigMap and Secret
managers are running. Valid values include:</p>
<ul>
<li><code>Get</code>: kubelet fetches necessary objects directly from the API server;</li>
<li><code>Cache</code>: kubelet uses TTL cache for object fetched from the API server;</li>
<li><code>Watch</code>: kubelet uses watches to observe changes to objects that are in its interest.</li>
</ul>
<p>Default: &quot;Watch&quot;</p>
   -->
   <p><code>configMapAndSecretChangeDetectionStrategy</code> 是 ConfigMap 和 Secret
管理器的运行模式。合法值包括：</p>
   <ul>
    <li><code>Get</code>：kubelet 从 API 服务器直接取回必要的对象；</li>
    <li><code>Cache</code>：kubelet 使用 TTL 缓存来管理来自 API 服务器的对象；</li>
    <li><code>Watch</code>：kubelet 使用 watch 操作来观察所关心的对象的变更。</li>
    </ul>
   <p>默认值：&quot;Watch&quot;</p>
</td>
</tr>

<tr><td><code>systemReserved</code><br/>
<code>map[string]string</code>
</td>
<td>
   <!--
   systemReserved is a set of ResourceName=ResourceQuantity (e.g. cpu=200m,memory=150G)
pairs that describe resources reserved for non-kubernetes components.
Currently only cpu and memory are supported.
See https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources for more detail.
Default: nil
   -->
   <p><code>systemReserved</code> 是一组<code>资源名称=资源数量</code>对，
用来描述为非 Kubernetes 组件预留的资源（例如：'cpu=200m,memory=150G'）。</p>
   <p>目前仅支持 CPU 和内存。更多细节可参见
   https://kubernetes.io/zh-cn/docs/tasks/administer-cluster/reserve-compute-resources</p>
   <p>默认值：Nil</p>
</td>
</tr>

<tr><td><code>kubeReserved</code><br/>
<code>map[string]string</code>
</td>
<td>
   <!--
   kubeReserved is a set of ResourceName=ResourceQuantity (e.g. cpu=200m,memory=150G) pairs
that describe resources reserved for kubernetes system components.
Currently cpu, memory and local storage for root file system are supported.
See https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources
for more details.
Default: nil
   -->
   <p><code>kubeReserved</code> 是一组<code>资源名称=资源数量</code>对，
用来描述为 Kubernetes 系统组件预留的资源（例如：'cpu=200m,memory=150G'）。
目前支持 CPU、内存和根文件系统的本地存储。
更多细节可参见 https://kubernetes.io/zh-cn/docs/tasks/administer-cluster/reserve-compute-resources</p>
   <p>默认值：Nil</p>
</td>
</tr>

<tr><td><code>reservedSystemCPUs</code> <B><!-- [Required] -->[必需]</B><br/>
<code>string</code>
</td>
<td>
   <!--
   The reservedSystemCPUs option specifies the CPU list reserved for the host
level system threads and kubernetes related threads. This provide a &quot;static&quot;
CPU list rather than the &quot;dynamic&quot; list by systemReserved and kubeReserved.
This option does not support systemReservedCgroup or kubeReservedCgroup.
   -->
   <p><code>reservedSystemCPUs</code> 选项设置为宿主级系统线程和 Kubernetes
相关线程所预留的 CPU 列表。此字段提供的是一种“静态”的 CPU 列表，而不是像
<code>systemReserved</code> 和 <code>kubeReserved</code> 所提供的“动态”列表。
此选项不支持 <code>systemReservedCgroup</code> 或 <code>kubeReservedCgroup</code>。</p>
</td>
</tr>

<tr><td><code>showHiddenMetricsForVersion</code><br/>
<code>string</code>
</td>
<td>
   <!--
   showHiddenMetricsForVersion is the previous version for which you want to show
hidden metrics.
Only the previous minor version is meaningful, other values will not be allowed.
The format is <code>&lt;major&gt;.&lt;minor&gt;</code>, e.g.: <code>1.16</code>.
The purpose of this format is make sure you have the opportunity to notice
if the next release hides additional metrics, rather than being surprised
when they are permanently removed in the release after that.
Default: &quot;&quot;
   -->
   <p><code>showHiddenMetricsForVersion<code> 是你希望显示隐藏度量值的上一版本。
只有上一个次版本是有意义的，其他值都是不允许的。
字段值的格式为 <code>&lt;major&gt;.&lt;minor&gt;</code>，例如：<code>1.16</code>。
此格式的目的是为了确保在下一个版本中有新的度量值被隐藏时，你有机会注意到这类变化，
而不是当这些度量值在其后的版本中彻底去除时来不及应对。</p>
   <p>默认值：&quot;&quot;</p>
</td>
</tr>

<tr><td><code>systemReservedCgroup</code><br/>
<code>string</code>
</td>
<td>
   <!--
   systemReservedCgroup helps the kubelet identify absolute name of top level CGroup used
to enforce <code>systemReserved</code> compute resource reservation for OS system daemons.
Refer to <a href="https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable">Node Allocatable</a>
doc for more information.
Default: &quot;&quot;
   -->
   <p><code>systemReservedCgroup</code> 帮助 kubelet 识别用来为 OS 系统级守护进程实施
<code>systemReserved</code> 计算资源预留时使用的顶级控制组（CGroup）。
更多细节参阅<a href="https://kubernetes.io/zh-cn/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable">节点可分配资源</a>。</p>
   <p>默认值：&quot;&quot;</p>
</td>
</tr>


<tr><td><code>kubeReservedCgroup</code><br/>
<code>string</code>
</td>
<td>
   <!--
   kubeReservedCgroup helps the kubelet identify absolute name of top level CGroup used
to enforce <code>KubeReserved</code> compute resource reservation for Kubernetes node system daemons.
Refer to <a href="https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable">Node Allocatable</a>
doc for more information.
Default: &quot;&quot;
   -->
   <p><code>kubeReservedCgroup</code> 帮助 kubelet 识别用来为 Kubernetes 节点系统级守护进程实施
<code>kubeReserved</code> 计算资源预留时使用的顶级控制组（CGroup）。
更多细节参阅<a href="https://kubernetes.io/zh-cn/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable">节点可分配资源</a></p>
   <p>默认值：&quot;&quot;</p>
</td>
</tr>

<tr><td><code>enforceNodeAllocatable</code><br/>
<code>[]string</code>
</td>
<td>
   <!--
   This flag specifies the various Node Allocatable enforcements that Kubelet needs to perform.
This flag accepts a list of options. Acceptable options are <code>none</code>, <code>pods</code>,
<code>system-reserved</code> and <code>kube-reserved</code>.
If <code>none</code> is specified, no other options may be specified.
When <code>system-reserved</code> is in the list, systemReservedCgroup must be specified.
When <code>kube-reserved</code> is in the list, kubeReservedCgroup must be specified.
This field is supported only when <code>cgroupsPerQOS</code> is set to true.
Refer to <a href="https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable">Node Allocatable</a>
for more information.
Default: [&quot;pods&quot;]
   -->
   <p>此标志设置 kubelet 需要执行的各类节点可分配资源策略。此字段接受一组选项列表。
可接受的选项有 <code>none</code>、<code>pods</code>、<code>system-reserved</code> 和
<code>kube-reserved</code>。</p>
   <p>如果设置了 <code>none</code>，则字段值中不可以包含其他选项。</p>
   <p>如果列表中包含 <code>system-reserved</code>，则必须设置 <code>systemReservedCgroup</code>。</p>
   <p>如果列表中包含 <code>kube-reserved</code>，则必须设置 <code>kubeReservedCgroup</code>。</p>
   <p>这个字段只有在 <code>cgroupsPerQOS</code>被设置为 <code>true</code> 才被支持。</p>
   <p>更多细节参阅<a href="https://kubernetes.io/zh-cn/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable">节点可分配资源</a>。</p>
   <p>默认值：[&quot;pods&quot;]</p>
</td>
</tr>

<tr><td><code>allowedUnsafeSysctls</code><br/>
<code>[]string</code>
</td>
<td>
   <!--
   A comma separated whitelist of unsafe sysctls or sysctl patterns (ending in <code>*</code>).
Unsafe sysctl groups are <code>kernel.shm*</code>, <code>kernel.msg*</code>, <code>kernel.sem</code>, <code>fs.mqueue.*</code>,
and <code>net.*</code>. For example: &quot;<code>kernel.msg*,net.ipv4.route.min_pmtu</code>&quot;
Default: []
  -->
   <p>用逗号分隔的白名单列表，其中包含不安全的 sysctl 或 sysctl 模式（以 <code>*</code> 结尾）。
</p>
   <p>不安全的 sysctl 组有 <code>kernel.shm*</code>、<code>kernel.msg*</code>、
<code>kernel.sem</code>、<code>fs.mqueue.*</code> 和 <code>net.*</code>。</p>
   <p>例如：&quot;<code>kernel.msg*,net.ipv4.route.min\_pmtu</code>&quot;</p>
   <p>默认值：[]</p>
</td>
</tr>

<tr><td><code>volumePluginDir</code><br/>
<code>string</code>
</td>
<td>
   <!--
   volumePluginDir is the full path of the directory in which to search
for additional third party volume plugins.
Default: &quot;/usr/libexec/kubernetes/kubelet-plugins/volume/exec/&quot;
   -->
   <p><code>volumePluginDir</code> 是用来搜索其他第三方卷插件的目录的路径。</p>
   <p>默认值：&quot;/usr/libexec/kubernetes/kubelet-plugins/volume/exec/&quot;</p>
</td>
</tr>

<tr><td><code>providerID</code><br/>
<code>string</code>
</td>
<td>
   <!--
   providerID, if set, sets the unique ID of the instance that an external
provider (i.e. cloudprovider) can use to identify a specific node.
Default: &quot;quot;
   -->
   <p><code>providerID</code> 字段被设置时，指定的是一个外部提供者（即云驱动）实例的唯一 ID，
该提供者可用来唯一性地标识特定节点。</p>
   <p>默认值：&quot;&quot;</p>
</td>
</tr>

<tr><td><code>kernelMemcgNotification</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   kernelMemcgNotification, if set, instructs the kubelet to integrate with the
kernel memcg notification for determining if memory eviction thresholds are
exceeded rather than polling.
Default: false
   -->
   <p><code>kernelMemcgNotification</code> 字段如果被设置了，会告知 kubelet 集成内核的
memcg 通知机制来确定是否超出内存逐出阈值，而不是使用轮询机制来判定。</p>
   <p>默认值：false</p>
</td>
</tr>

<tr><td><code>logging</code> <B><!-- [Required] -->[必需]</B><br/>
<a href="#LoggingConfiguration"><code>LoggingConfiguration</code></a>
</td>
<td>
   <!--
   logging specifies the options of logging.
Refer to <a href="https://github.com/kubernetes/component-base/blob/master/logs/options.go">Logs Options</a>
for more information.
Default:
  Format: text
   -->
   <p><code>logging</code>设置日志机制选项。更多的详细信息可参阅
<a href="https://github.com/kubernetes/component-base/blob/master/logs/options.go">日志选项</a>。</p>
   <p>默认值：</p>
   <code><pre>Format: text</pre></code>
</td>
</tr>

<tr><td><code>enableSystemLogHandler</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   enableSystemLogHandler enables system logs via web interface host:port/logs/
Default: true
   -->
   <p><code>enableSystemLogHandler</code> 用来启用通过 Web 接口 host:port/logs/
访问系统日志的能力。</p>
   <p>默认值：true</p>
</td>
</tr>

<tr><td><code>enableSystemLogQuery</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   enableSystemLogQuery enables the node log query feature on the /logs endpoint.
EnableSystemLogHandler has to be enabled in addition for this feature to work.
Enabling this feature has security implications. The recommendation is to enable it on a need basis for debugging
purposes and disabling otherwise.
   -->
   <p><code>enableSystemLogQuery</code> 启用在 /logs 端点上的节点日志查询功能。
此外，还必须启用 enableSystemLogHandler 才能使此功能起作用。
启用此特性具有安全隐患。建议仅在调试需要时才启用，其他情况下应禁用。
</p>
   <p>默认值：false</p>
</td>
</tr>
<tr><td><code>shutdownGracePeriod</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   shutdownGracePeriod specifies the total duration that the node should delay the
shutdown and total grace period for pod termination during a node shutdown.
Default: &quot;0s&quot;
   -->
   <p><code>shutdownGracePeriod</code> 设置节点关闭期间，节点自身需要延迟以及为
Pod 提供的宽限期限的总时长。</p>
   <p>默认值：&quot;0s&quot;</p>
</td>
</tr>

<tr><td><code>shutdownGracePeriodCriticalPods</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   shutdownGracePeriodCriticalPods specifies the duration used to terminate critical
pods during a node shutdown. This should be less than shutdownGracePeriod.
For example, if shutdownGracePeriod=30s, and shutdownGracePeriodCriticalPods=10s,
during a node shutdown the first 20 seconds would be reserved for gracefully
terminating normal pods, and the last 10 seconds would be reserved for terminating
critical pods.
Default: &quot;0s&quot;
   -->
   <p><code>shutdownGracePeriodCriticalPods</code>设置节点关闭期间用来终止关键性
Pod 的时长。此时长要短于<code>shutdownGracePeriod</code>。
例如，如果<code>shutdownGracePeriod=30s</code>，<code>shutdownGracePeriodCriticalPods=10s<code>，
在节点关闭期间，前 20 秒钟被预留用来体面终止普通 Pod，后 10 秒钟用来终止关键 Pod。</p>
   <p>默认值：&quot;0s&quot;</p>
</td>
</tr>

<tr><td><code>shutdownGracePeriodByPodPriority</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-ShutdownGracePeriodByPodPriority"><code>[]ShutdownGracePeriodByPodPriority</code></a>
</td>
<td>
   <!--
   shutdownGracePeriodByPodPriority specifies the shutdown grace period for Pods based
on their associated priority class value.
When a shutdown request is received, the Kubelet will initiate shutdown on all pods
running on the node with a grace period that depends on the priority of the pod,
and then wait for all pods to exit.
Each entry in the array represents the graceful shutdown time a pod with a priority
class value that lies in the range of that value and the next higher entry in the
list when the node is shutting down.
For example, to allow critical pods 10s to shutdown, priority&gt;=10000 pods 20s to
shutdown, and all remaining pods 30s to shutdown.
-->
   <p><code>shutdownGracePeriodByPodPriority</code> 设置基于 Pod
相关的优先级类值而确定的体面关闭时间。当 kubelet 收到关闭请求的时候，kubelet
会针对节点上运行的所有 Pod 发起关闭操作，这些关闭操作会根据 Pod 的优先级确定其宽限期限，
之后 kubelet 等待所有 Pod 退出。</p>
   <p>数组中的每个表项代表的是节点关闭时 Pod 的体面终止时间；这里的 Pod
的优先级类介于列表中当前优先级类值和下一个表项的优先级类值之间。</p>
   <p>例如，要赋予关键 Pod 10 秒钟时间来关闭，赋予优先级 &gt;=10000 Pod 20 秒钟时间来关闭，
赋予其余的 Pod 30 秒钟来关闭。</p>
   <p>shutdownGracePeriodByPodPriority:</p>
   <ul>
   <li>priority: 2000000000
   shutdownGracePeriodSeconds: 10</li>
   <li>priority: 10000
   shutdownGracePeriodSeconds: 20</li>
   <li>priority: 0
   shutdownGracePeriodSeconds: 30</li>
   </ul>
<!--
The time the Kubelet will wait before exiting will at most be the maximum of all
shutdownGracePeriodSeconds for each priority class range represented on the node.
When all pods have exited or reached their grace periods, the Kubelet will release
the shutdown inhibit lock.
Requires the GracefulNodeShutdown feature gate to be enabled.
This configuration must be empty if either ShutdownGracePeriod or ShutdownGracePeriodCriticalPods is set.
Default: nil
-->
   <p>在退出之前，kubelet 要等待的时间上限为节点上所有优先级类的
<code>shutdownGracePeriodSeconds</code> 的最大值。
当所有 Pod 都退出或者到达其宽限期限时，kubelet 会释放关闭防护锁。
此功能要求 <code>GracefulNodeShutdown</code> 特性门控被启用。</p>
   <p>当 <code>shutdownGracePeriod</code> 或 <code>shutdownGracePeriodCriticalPods</code>
被设置时，此配置字段必须为空。</p>
   <p>默认值：nil</p>
</td>
</tr>

<tr><td><code>crashLoopBackOff</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-CrashLoopBackOffConfig"><code>CrashLoopBackOffConfig</code></a>
</td>
<td>
   <p>
   <!--
   CrashLoopBackOff contains config to modify node-level parameters for
container restart behavior
-->
   <code>crashLoopBackOff</code> 包含修改节点级别参数的配置，用于容器重启行为。
   </p>
</td>
</tr>

<tr><td><code>reservedMemory</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-MemoryReservation"><code>[]MemoryReservation</code></a>
</td>
<td>
   <p>
   <!--
   reservedMemory specifies a comma-separated list of memory reservations for NUMA nodes.
The parameter makes sense only in the context of the memory manager feature.
The memory manager will not allocate reserved memory for container workloads.
For example, if you have a NUMA0 with 10Gi of memory and the reservedMemory was
specified to reserve 1Gi of memory at NUMA0, the memory manager will assume that
only 9Gi is available for allocation.
You can specify a different amount of NUMA node and memory types.
You can omit this parameter at all, but you should be aware that the amount of
reserved memory from all NUMA nodes should be equal to the amount of memory specified
by the <a href="https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable">node allocatable</a>.
If at least one node allocatable parameter has a non-zero value, you will need
to specify at least one NUMA node.
Also, avoid specifying:
-->
   <code>reservedMemory</code> 给出一个逗号分隔的列表，为 NUMA 节点预留内存。
   此参数仅在内存管理器功能特性语境下有意义。内存管理器不会为容器负载分配预留内存。
例如，如果你的 NUMA0 节点内存为 10Gi，<code>reservedMemory</code> 设置为在 NUMA0
上预留 1Gi 内存，内存管理器会认为其上只有 9Gi 内存可供分配。
   你可以设置不同数量的 NUMA 节点和内存类型。你也可以完全忽略这个字段，不过你要清楚，
所有 NUMA 节点上预留内存的总量要等于通过
<a href="https://kubernetes.io/zh-cn/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable">节点可分配资源</a>设置的内存量。
   如果至少有一个节点可分配参数设置值非零，则你需要设置至少一个 NUMA 节点。
   此外，避免如下设置：
</p>
   <ol>
   <!--
   <li>Duplicates, the same NUMA node, and memory type, but with a different value.</li>
   <li>zero limits for any memory type.</li>
   <li>NUMAs nodes IDs that do not exist under the machine.</li>
   <li>memory types except for memory and hugepages-&lt;size&gt;</li>
   </ol>
   -->
   <li>在配置值中存在重复项，NUMA 节点和内存类型相同，但配置值不同，这是不允许的。</li>
   <li>为任何内存类型设置限制值为零。</li>
   <li>NUMA 节点 ID 在宿主系统上不存在。/li>
   <li>除 <code>memory</code> 和 <code>hugepages-&lt;size&gt;</code> 之外的内存类型。</li>
   </ol>
   <p>
   <!--
   Default: nil
   -->
   默认值：nil
   </p>
</td>
</tr>

<tr><td><code>enableProfilingHandler</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   enableProfilingHandler enables profiling via web interface host:port/debug/pprof/
Default: true
   -->
   <p><code>enableProfilingHandler</code> 启用通过 <code>host:port/debug/pprof/</code> 接口来执行性能分析。</p>
   <p>默认值：true</p>
</td>
</tr>

<tr><td><code>enableDebugFlagsHandler</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   enableDebugFlagsHandler enables flags endpoint via web interface host:port/debug/flags/v
Default: true
   -->
   <p><code>enableDebugFlagsHandler</code> 启用通过 <code>host:port/debug/flags/v Web</code>
接口上的标志设置。</p>
   <p>默认值：true</p>
</td>
</tr>

<tr><td><code>seccompDefault</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   SeccompDefault enables the use of <code>RuntimeDefault</code> as the default seccomp profile for all workloads.
This requires the corresponding SeccompDefault feature gate to be enabled as well.
Default: false
   -->
   <p><code>seccompDefault</code> 字段允许针对所有负载将 <code>RuntimeDefault</code>
设置为默认的 seccomp 配置。这一设置要求对应的 <code>SeccompDefault</code> 特性门控被启用。</p>
   <p>默认值：false</p>
</td>
</tr>

<tr><td><code>memoryThrottlingFactor</code><br/>
<code>float64</code>
</td>
<td>
   <!--
   MemoryThrottlingFactor specifies the factor multiplied by the memory limit or node allocatable memory
when setting the cgroupv2 memory.high value to enforce MemoryQoS.
Decreasing this factor will set lower high limit for container cgroups and put heavier reclaim pressure
while increasing will put less reclaim pressure.
See https://kep.k8s.io/2570 for more details.
Default: 0.8
   -->
   <p>当设置 cgroupv2 <code>memory.high</code> 以实施 <code>MemoryQoS</code> 特性时，
<code>memoryThrottlingFactor</code> 用来作为内存限制或节点可分配内存的系数。</p>
   <p>减小此系数会为容器控制组设置较低的 high 限制值，从而增大回收压力；反之，
增大此系数会降低回收压力。更多细节参见 https://kep.k8s.io/2570。</p>
   <p>默认值：0.8</p>
</td>
</tr>

<tr><td><code>registerWithTaints</code><br/>
<a href="https://kubernetes.io/zh-cn/docs/reference/generated/kubernetes-api/v1.34/#taint-v1-core"><code>[]core/v1.Taint</code></a>
</td>
<td>
   <!--
   registerWithTaints are an array of taints to add to a node object when
the kubelet registers itself. This only takes effect when registerNode
is true and upon the initial registration of the node.
Default: nil
   -->
   <p><code>registerWithTaints</code> 是一个由污点组成的数组，包含 kubelet
注册自身时要向节点对象添加的污点。只有 <code>registerNode</code> 为 <code>true</code>
时才会起作用，并且仅在节点的最初注册时起作用。</p>
   <p>默认值：nil</p>
</td>
</tr>

<tr><td><code>registerNode</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   registerNode enables automatic registration with the apiserver.
Default: true
   -->
   <p><code>registerNode</code> 启用向 API 服务器的自动注册。</p>
   <p>默认值：true</p>
</td>
</tr>
<tr><td><code>tracing</code><br/>
<a href="#TracingConfiguration"><code>TracingConfiguration</code></a>
</td>
<td>
   <!--
   Tracing specifies the versioned configuration for OpenTelemetry tracing clients.
See https://kep.k8s.io/2832 for more details.
   -->
   <p>tracing 为 OpenTelemetry 追踪客户端设置版本化的配置信息。
参阅 https://kep.k8s.io/2832 了解更多细节。</p>
</td>
</tr>
<tr><td><code>localStorageCapacityIsolation</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   LocalStorageCapacityIsolation enables local ephemeral storage isolation feature. The default setting is true.
This feature allows users to set request/limit for container's ephemeral storage and manage it in a similar way
as cpu and memory. It also allows setting sizeLimit for emptyDir volume, which will trigger pod eviction if disk
usage from the volume exceeds the limit.
This feature depends on the capability of detecting correct root file system disk usage. For certain systems,
such as kind rootless, if this capability cannot be supported, the feature LocalStorageCapacityIsolation should be
disabled. Once disabled, user should not set request/limit for container's ephemeral storage, or sizeLimit for emptyDir.
Default: true
   -->
   <p>localStorageCapacityIsolation 启用本地临时存储隔离特性。默认设置为 true。
此特性允许用户为容器的临时存储设置请求/限制，并以类似的方式管理 cpu 和 memory 的请求/限制。
此特性还允许为 emptyDir 卷设置 sizeLimit，如果卷所用的磁盘超过此限制将触发 Pod 驱逐。
此特性取决于准确测定根文件系统磁盘用量的能力。对于 kind rootless 这类系统，
如果不支持此能力，则 LocalStorageCapacityIsolation 特性应被禁用。
一旦禁用，用户不应该为容器的临时存储设置请求/限制，也不应该为 emptyDir 设置 sizeLimit。
默认值：true</p>
</td>
</tr>
<tr><td><code>containerRuntimeEndpoint</code> <B><!-- [Required] -->[必需]</B><br/>
<code>string</code>
</td>
<td>
   <!--
   ContainerRuntimeEndpoint is the endpoint of container runtime.
Unix Domain Sockets are supported on Linux, while npipe and tcp endpoints are supported on Windows.
Examples:'unix:///path/to/runtime.sock', 'npipe:////./pipe/runtime'
   -->
   <p>containerRuntimeEndpoint 是容器运行时的端点。
Linux 支持 UNIX 域套接字，而 Windows 支持命名管道和 TCP 端点。
示例：'unix:///path/to/runtime.sock', 'npipe:////./pipe/runtime'。</p>
</td>
</tr>
<tr><td><code>imageServiceEndpoint</code><br/>
<code>string</code>
</td>
<td>
   <!--
   ImageServiceEndpoint is the endpoint of container image service.
Unix Domain Socket are supported on Linux, while npipe and tcp endpoints are supported on Windows.
Examples:'unix:///path/to/runtime.sock', 'npipe:////./pipe/runtime'.
If not specified, the value in containerRuntimeEndpoint is used.
   -->
   <p>imageServiceEndpoint 是容器镜像服务的端点。
Linux 支持 UNIX 域套接字，而 Windows 支持命名管道和 TCP 端点。
示例：'unix:///path/to/runtime.sock'、'npipe:////./pipe/runtime'。
如果未指定，则使用 containerRuntimeEndpoint 中的值。</p>
</td>
</tr>
<tr><td><code>failCgroupV1</code><br/>
<code>bool</code>
</td>
<td>
   <p>
   <!--
   FailCgroupV1 prevents the kubelet from starting on hosts
that use cgroup v1. By default, this is set to 'false', meaning
the kubelet is allowed to start on cgroup v1 hosts unless this
option is explicitly enabled.
Default: false
-->
  <code>failCgroupV1</code> 防止 kubelet 在使用 cgroup v1 的主机上启动。
默认情况下，此选项设置为 “false”，这意味着除非此选项被显式启用，
否则 kubelet 被允许在 cgroup v1 主机上启动。  
默认值：false
</p>
</td>
</tr>

<tr><td><code>userNamespaces</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-UserNamespaces"><code>UserNamespaces</code></a>
</td>
<td>
   <p>
   <!--
   UserNamespaces contains User Namespace configurations.
   -->
   <code>userNamespaces</code> 包含用户命名空间配置。
   </p>
</td>
</tr>

</tbody>
</table>

## `SerializedNodeConfigSource`     {#kubelet-config-k8s-io-v1beta1-SerializedNodeConfigSource}

<!--
SerializedNodeConfigSource allows us to serialize v1.NodeConfigSource.
This type is used internally by the Kubelet for tracking checkpointed dynamic configs.
It exists in the kubeletconfig API group because it is classified as a versioned input to the Kubelet.
-->
SerializedNodeConfigSource 允许对 `v1.NodeConfigSource` 执行序列化操作。
这一类型供 kubelet 内部使用，以便跟踪动态配置的检查点。
此资源存在于 kubeletconfig API 组是因为它被当做是对 kubelet 的一种版本化输入。

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>apiVersion</code><br/>string</td><td><code>kubelet.config.k8s.io/v1beta1</code></td></tr>
<tr><td><code>kind</code><br/>string</td><td><code>SerializedNodeConfigSource</code></td></tr>

<tr><td><code>source</code><br/>
<a href="https://kubernetes.io/zh-cn/docs/reference/generated/kubernetes-api/v1.34/#nodeconfigsource-v1-core"><code>core/v1.NodeConfigSource</code></a>
</td>
<td>
   <!--
   source is the source that we are serializing.
   -->
   <p><code>source</code>是我们执行序列化的数据源。</p>
</td>
</tr>

</tbody>
</table>

## `CrashLoopBackOffConfig`     {#kubelet-config-k8s-io-v1beta1-CrashLoopBackOffConfig}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>maxContainerRestartPeriod</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <p>
   <!--
   maxContainerRestartPeriod is the maximum duration the backoff delay can accrue
to for container restarts, minimum 1 second, maximum 300 seconds. If not set,
defaults to the internal crashloopbackoff maximum (300s).
-->
<code>maxContainerRestartPeriod</code> 是容器重启时回退延迟可以累积的最长持续时间，最短为 1 秒，最长为 300 秒。
如果不设置，则默认为内部 crashloopbackoff 的最大值（300 秒）。
</p>
</td>
</tr>
</tbody>
</table>

## `CredentialProvider`     {#kubelet-config-k8s-io-v1beta1-CredentialProvider}

<!--
**Appears in:**
-->
**出现在：**

- [CredentialProviderConfig](#kubelet-config-k8s-io-v1beta1-CredentialProviderConfig)

<!--
CredentialProvider represents an exec plugin to be invoked by the kubelet. The plugin is only
invoked when an image being pulled matches the images handled by the plugin (see matchImages).
-->
CredentialProvider 代表的是要被 kubelet 调用的一个 exec 插件。
这一插件只会在所拉取的镜像与该插件所处理的镜像匹配时才会被调用（参见 <code>matchImages</code>）。

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>name</code> <B><!--[Required]-->[必需]</B><br/>
<code>string</code>
</td>
<td>
<p>
<!--
name is the required name of the credential provider. It must match the name of the
provider executable as seen by the kubelet. The executable must be in the kubelet's
bin directory (set by the --image-credential-provider-bin-dir flag).
Required to be unique across all providers.
-->
<code>name</code> 是凭据提供者的名称（必需）。此名称必须与 kubelet
所看到的提供者可执行文件的名称匹配。可执行文件必须位于 kubelet 的 
<code>bin</code> 目录（通过 <code>--image-credential-provider-bin-dir</code> 设置）下。
在所有提供程序中，名称是唯一的。
</p>
</td>
</tr>
<tr><td><code>matchImages</code> <B><!--[Required]-->[必需]</B><br/>
<code>[]string</code>
</td>
<td>
<p>
<!--
matchImages is a required list of strings used to match against images in order to
determine if this provider should be invoked. If one of the strings matches the
requested image from the kubelet, the plugin will be invoked and given a chance
to provide credentials. Images are expected to contain the registry domain
and URL path.
-->
<code>matchImages</code> 是一个必须设置的字符串列表，用来匹配镜像以便确定是否要调用此提供者。
如果字符串之一与 kubelet 所请求的镜像匹配，则此插件会被调用并给予提供凭证的机会。
镜像应该包含镜像库域名和 URL 路径。
</p>
<p>
<!--
Each entry in matchImages is a pattern which can optionally contain a port and a path.
Globs can be used in the domain, but not in the port or the path. Globs are supported
as subdomains like '<em>.k8s.io' or 'k8s.</em>.io', and top-level-domains such as 'k8s.<em>'.
Matching partial subdomains like 'app</em>.k8s.io' is also supported. Each glob can only match
a single subdomain segment, so *.io does not match *.k8s.io.
-->
<code>matchImages</code> 中的每个条目都是一个模式字符串，其中可以包含端口号和路径。
域名部分可以包含统配符，但端口或路径部分不可以。通配符可以用作子域名，例如
<code>&ast;.k8s.io</code> 或 <code>k8s.&ast;.io</code>，以及顶级域名，如 <code>k8s.&ast;</code>。
对类似 <code>app&ast;.k8s.io</code> 这类部分子域名的匹配也是支持的。
每个通配符只能用来匹配一个子域名段，所以 <code>&ast;.io</code> 不会匹配 <code>&ast;.k8s.io</code>。
</p>
<p>
<!--
A match exists between an image and a matchImage when all of the below are true:
-->
镜像与 <code>matchImages</code> 之间存在匹配时，以下条件都要满足：
</p>
<ul>
<!--
<li>Both contain the same number of domain parts and each part matches.</li>
<li>The URL path of an imageMatch must be a prefix of the target image URL path.</li>
<li>If the imageMatch contains a port, then the port must match in the image as well.</li>
-->
<li>二者均包含相同个数的域名部分，并且每个域名部分都对应匹配；</li>
<li><code>matchImages</code> 条目中的 URL 路径部分必须是目标镜像的 URL 路径的前缀；</li>
<li>如果 <code>matchImages</code> 条目中包含端口号，则端口号也必须与镜像端口号匹配。</li>
</ul>
<p>
<!--
Example values of matchImages:
-->
<code>matchImages</code> 的一些示例如下：
</p>
<ul>
<li>123456789.dkr.ecr.us-east-1.amazonaws.com</li>
<li>&ast;.azurecr.io</li>
<li>gcr.io</li>
<li>&ast;.&ast;.registry.io</li>
<li>registry.io:8080/path</li>
</ul>
</td>
</tr>
<tr><td><code>defaultCacheDuration</code> <B><!--[Required]-->[必需]</B><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <p>
<!--
defaultCacheDuration is the default duration the plugin will cache credentials in-memory
if a cache duration is not provided in the plugin response. This field is required.
-->
<code>defaultCacheDuration</code> 是插件在内存中缓存凭据的默认时长，
在插件响应中没有给出缓存时长时，使用这里设置的值。此字段是必需的。
</p>
</td>
</tr>
<tr><td><code>apiVersion</code> <B><!--[Required]-->[必需]</B><br/>
<code>string</code>
</td>
<td>
<p>
<!--
Required input version of the exec CredentialProviderRequest. The returned CredentialProviderResponse
MUST use the same encoding version as the input. Current supported values are:
-->
要求 exec 插件 CredentialProviderRequest 请求的输入版本。
所返回的 CredentialProviderResponse 必须使用与输入相同的编码版本。当前支持的值有：
</p>
<ul>
<li>credentialprovider.kubelet.k8s.io/v1beta1</li>
</ul>
</td>
</tr>
<tr><td><code>args</code><br/>
<code>[]string</code>
</td>
<td>
<p>
<!--
Arguments to pass to the command when executing it.
-->
在执行插件可执行文件时要传递给命令的参数。
</p>
</td>
</tr>
<tr><td><code>env</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-ExecEnvVar"><code>[]ExecEnvVar</code></a>
</td>
<td>
<p>
<!--
Env defines additional environment variables to expose to the process. These
are unioned with the host's environment, as well as variables client-go uses
to pass argument to the plugin.
-->
<code>env</code> 定义要提供给插件进程的额外的环境变量。
这些环境变量会与主机上的其他环境变量以及 client-go 所使用的环境变量组合起来，
一起传递给插件。
</p>
</td>
</tr>
</tbody>
</table>

## `ExecEnvVar`     {#kubelet-config-k8s-io-v1beta1-ExecEnvVar}

<!--
**Appears in:**
-->
**出现在：**

- [CredentialProvider](#kubelet-config-k8s-io-v1beta1-CredentialProvider)

<!--
ExecEnvVar is used for setting environment variables when executing an exec-based
credential plugin.
-->
ExecEnvVar 用来在执行基于 exec 的凭据插件时设置环境变量。

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>name</code> <B><!--[Required]-->[必需]</B><br/>
<code>string</code>
</td>
<td>
   <span class="text-muted">
   <!--
   No description provided.
   -->
   环境变量的名称。
   </span>
</td>
</tr>
<tr><td><code>value</code> <B><!--[Required]-->[必需]</B><br/>
<code>string</code>
</td>
<td>
   <span class="text-muted">
   <!--
   No description provided.
   -->
   环境变量的取值。
   </span>
</td>
</tr>
</tbody>
</table>

## `ImagePullCredentialsVerificationPolicy`     {#kubelet-config-k8s-io-v1beta1-ImagePullCredentialsVerificationPolicy}
    
<!--
(Alias of `string`)

**Appears in:**
-->
（`string` 的别名）

**出现在：**

- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)

<p>
<!--
ImagePullCredentialsVerificationPolicy is an enum for the policy that is enforced
when pod is requesting an image that appears on the system
-->
ImagePullCredentialsVerificationPolicy 是一个枚举类型，用于指定在 Pod 请求系统上已存在的镜像时所强制执行的策略。
</p>

## `KubeletAnonymousAuthentication`     {#kubelet-config-k8s-io-v1beta1-KubeletAnonymousAuthentication}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletAuthentication](#kubelet-config-k8s-io-v1beta1-KubeletAuthentication)

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>enabled</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   <p>enabled allows anonymous requests to the kubelet server.
Requests that are not rejected by another authentication method are treated as
anonymous requests.
Anonymous requests have a username of <code>system:anonymous</code>, and a group name of
<code>system:unauthenticated</code>.</p>
   -->
   <p><code>enabled</code> 允许匿名用户向 kubelet 服务器发送请求。
未被其他身份认证方法拒绝的请求都会被当做匿名请求。
匿名请求对应的用户名为 <code>system:anonymous</code>，对应的用户组名为
<code>system:unauthenticated</code>。</p>
</td>
</tr>
</tbody>
</table>

## `KubeletAuthentication`     {#kubelet-config-k8s-io-v1beta1-KubeletAuthentication}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>x509</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-KubeletX509Authentication"><code>KubeletX509Authentication</code></a>
</td>
<td>
   <!--
   x509 contains settings related to x509 client certificate authentication.
   -->
   <p><code>x509</code> 包含与 x509 客户端证书认证相关的配置。</p>
</td>
</tr>

<tr><td><code>webhook</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-KubeletWebhookAuthentication"><code>KubeletWebhookAuthentication</code></a>
</td>
<td>
   <!--
   webhook contains settings related to webhook bearer token authentication.
   -->
   <p><code>webhook</code> 包含与 Webhook 持有者令牌认证相关的配置。</p>
</td>
</tr>

<tr><td><code>anonymous</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-KubeletAnonymousAuthentication"><code>KubeletAnonymousAuthentication</code></a>
</td>
<td>
   <!--
   anonymous contains settings related to anonymous authentication.
   -->
   <p><code>anonymous</code> 包含与匿名身份认证相关的配置信息。</p>
</td>
</tr>
</tbody>
</table>

## `KubeletAuthorization`     {#kubelet-config-k8s-io-v1beta1-KubeletAuthorization}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>mode</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-KubeletAuthorizationMode"><code>KubeletAuthorizationMode</code></a>
</td>
<td>
   <!--
   mode is the authorization mode to apply to requests to the kubelet server.
Valid values are <code>AlwaysAllow</code> and <code>Webhook</code>.
Webhook mode uses the SubjectAccessReview API to determine authorization.</p>
   -->
   <p><code>mode</code> 是应用到 kubelet 服务器所接收到的请求上的鉴权模式。合法值包括
<code>AlwaysAllow</code> 和 <code>Webhook</code>。
Webhook 模式使用 <code>SubjectAccessReview</code> API 来确定鉴权。</p>
</td>
</tr>

<tr><td><code>webhook</code><br/>
<a href="#kubelet-config-k8s-io-v1beta1-KubeletWebhookAuthorization"><code>KubeletWebhookAuthorization</code></a>
</td>
<td>
   <!--
   webhook contains settings related to Webhook authorization.
   -->
   <p><code>webhook</code>包含与 Webhook 鉴权相关的配置信息。</p>
</td>
</tr>
</tbody>
</table>

## `KubeletAuthorizationMode`     {#kubelet-config-k8s-io-v1beta1-KubeletAuthorizationMode}

<!--
(Alias of `string`)
-->
（`string` 类型的别名）

<!--
**Appears in:**
-->
**出现在：**

- [KubeletAuthorization](#kubelet-config-k8s-io-v1beta1-KubeletAuthorization)

## `KubeletWebhookAuthentication`     {#kubelet-config-k8s-io-v1beta1-KubeletWebhookAuthentication}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletAuthentication](#kubelet-config-k8s-io-v1beta1-KubeletAuthentication)

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>enabled</code><br/>
<code>bool</code>
</td>
<td>
   <!--
   enabled allows bearer token authentication backed by the
tokenreviews.authentication.k8s.io API.
   -->
   <p><code>enabled</code> 允许使用 <code>tokenreviews.authentication.k8s.io</code>
API 来提供持有者令牌身份认证。</p>
</td>
</tr>

<tr><td><code>cacheTTL</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   cacheTTL enables caching of authentication results
   -->
   <p><code>cacheTTL</code> 启用对身份认证结果的缓存。</p>
</td>
</tr>
</tbody>
</table>

## `KubeletWebhookAuthorization`     {#kubelet-config-k8s-io-v1beta1-KubeletWebhookAuthorization}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletAuthorization](#kubelet-config-k8s-io-v1beta1-KubeletAuthorization)

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>cacheAuthorizedTTL</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   cacheAuthorizedTTL is the duration to cache 'authorized' responses from the
webhook authorizer.
   -->
   <p><code>cacheAuthorizedTTL</code> 设置来自 Webhook 鉴权组件的 'authorized'
响应的缓存时长。</p>
</td>
</tr>
<tr><td><code>cacheUnauthorizedTTL</code><br/>
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
</td>
<td>
   <!--
   cacheUnauthorizedTTL is the duration to cache 'unauthorized' responses from
the webhook authorizer.
   -->
   <p><code>cacheUnauthorizedTTL</code> 设置来自 Webhook 鉴权组件的 'unauthorized'
响应的缓存时长。</p>
</td>
</tr>
</tbody>
</table>

## `KubeletX509Authentication`     {#kubelet-config-k8s-io-v1beta1-KubeletX509Authentication}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletAuthentication](#kubelet-config-k8s-io-v1beta1-KubeletAuthentication)

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>clientCAFile</code><br/>
<code>string</code>
</td>
<td>
   <!--
   clientCAFile is the path to a PEM-encoded certificate bundle. If set, any request
presenting a client certificate signed by one of the authorities in the bundle
is authenticated with a username corresponding to the CommonName,
and groups corresponding to the Organization in the client certificate.
   -->
   <p><code>clientCAFile</code> 是一个指向 PEM 编码的证书包的路径。
如果设置了此字段，则能够提供由此证书包中机构之一所签名的客户端证书的请求会被成功认证，
并且其用户名对应于客户端证书的 <code>CommonName</code>、组名对应于客户端证书的
<code>Organization</code>。</p>
</td>
</tr>
</tbody>
</table>

## `MemoryReservation`     {#kubelet-config-k8s-io-v1beta1-MemoryReservation}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)

<!--
MemoryReservation specifies the memory reservation of different types for each NUMA node
-->
MemoryReservation 为每个 NUMA 节点设置不同类型的内存预留。

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>numaNode</code> <B><!-- [Required] -->[必需]</B><br/>
<code>int32</code>
</td>
<td>
   <!--span class="text-muted">No description provided.</span-->
   <p>NUMA 节点</p>
</td>
</tr>

<tr><td><code>limits</code> <B><!-- [Required] -->[必需]</B><br/>
<a href="https://kubernetes.io/zh-cn/docs/reference/generated/kubernetes-api/v1.34/#resourcelist-v1-core"><code>core/v1.ResourceList</code></a>
</td>
<td>
   <!--span class="text-muted">No description provided.</span-->
   <p>资源列表</p>
</td>
</tr>
</tbody>
</table>

## `MemorySwapConfiguration`     {#kubelet-config-k8s-io-v1beta1-MemorySwapConfiguration}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>swapBehavior</code><br/>
<code>string</code>
</td>
<td>
   <!--
   swapBehavior configures swap memory available to container workloads. May be one of
&quot;&quot;, &quot;LimitedSwap&quot;: workload combined memory and swap usage cannot exceed pod memory limit
&quot;UnlimitedSwap&quot;: workloads can use unlimited swap, up to the allocatable limit.
   -->
   <p><code>swapBehavior</code>配置容器负载可以使用的交换内存。可以是：
   <ul>
    <li>&quot;&quot;、&quot;LimitedSwap&quot;：工作负载的内存和交换分区总用量不能超过 Pod 的内存限制；</li>
    <li>&quot;UnlimitedSwap&quot;：工作负载可以无限制地使用交换分区，上限是可分配的约束。</li>
   </ul>
</td>
</tr>
</tbody>
</table>

## `ResourceChangeDetectionStrategy`     {#kubelet-config-k8s-io-v1beta1-ResourceChangeDetectionStrategy}

<!--
(Alias of `string`)
-->
（`string` 类型的别名）

<!--
**Appears in:**
-->
**出现在：**

- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)

<!--
ResourceChangeDetectionStrategy denotes a mode in which internal
managers (secret, configmap) are discovering object changes.
-->
ResourceChangeDetectionStrategy 给出的是内部管理器（Secret、ConfigMap）
用来发现对象变化的模式。

## `ShutdownGracePeriodByPodPriority`     {#kubelet-config-k8s-io-v1beta1-ShutdownGracePeriodByPodPriority}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)

<!--
ShutdownGracePeriodByPodPriority specifies the shutdown grace period for Pods based on their associated priority class value
-->
ShutdownGracePeriodByPodPriority 基于 Pod 关联的优先级类数值来为其设置关闭宽限时间。

<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>

<tr><td><code>priority</code> <B><!-- [Required] -->[必需]</B><br/>
<code>int32</code>
</td>
<td>
   <!--
   priority is the priority value associated with the shutdown grace period
   -->
   <p><code>priority</code> 是与关闭宽限期限相关联的优先级值。</p>
</td>
</tr>

<tr><td><code>shutdownGracePeriodSeconds</code> <B><!-- [Required] -->[必需]</B><br/>
<code>int64</code>
</td>
<td>
   <!--
   shutdownGracePeriodSeconds is the shutdown grace period in seconds
   -->
   <p><code>shutdownGracePeriodSeconds</code> 是按秒数给出的关闭宽限期限。
</td>
</tr>
</tbody>
</table>

## `UserNamespaces`     {#kubelet-config-k8s-io-v1beta1-UserNamespaces}

<!--
**Appears in:**
-->
**出现在：**

- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)

<p>
<!--
UserNamespaces contains User Namespace configurations.
-->
<code>UserNamespaces</code> 包含用户命名空间配置。
</p>


<table class="table">
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
<tbody>
    
  
<tr><td><code>idsPerPod</code><br/>
<code>int64</code>
</td>
<td>
   <!--
   <p>IDsPerPod is the mapping length of UIDs and GIDs.
The length must be a multiple of 65536, and must be less than 1&lt;&lt;32.
On non-linux such as windows, only null / absent is allowed.</p>
<p>Changing the value may require recreating all containers on the node.</p>
<p>Default: 65536</p>
-->
<p><code>idsPerPod</code> 是 UID 和 GID 的映射长度。
长度值必须是 65536 的倍数，且必须小于 1&lt;&lt;32。
在非 Linux 系统（如 Windows）上，仅允许空或不设置。</p>
<p>更改此值可能需要重新创建节点上的所有容器。</p>
<p>默认值：65536</p>
</td>
</tr>
</tbody>
</table>