Skip to content

Commit 0ec99a3

Browse files
k8s-ci-robotk8s-ci-robot
authored
Merge pull request #36588 from Michelle951/michelle004
[zh]sync kube-proxy-config.v1alpha1.md
2 parents 7ed1f6d + 39ab93b commit 0ec99a3

File tree

1 file changed

+6
-188
lines changed

1 file changed

+6
-188
lines changed

‎content/zh-cn/docs/reference/config-api/kube-proxy-config.v1alpha1.md

Lines changed: 6 additions & 188 deletions
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ Profiling handlers will be handled by metrics server.
112112
bridge traffic coming from outside of the cluster. If not provided,
113113
no off-cluster bridging will be performed.
114114
-->
115-
<p><code>clusterCIDR</code> 字段是集群中 Pods 所使用的 CIDR 范围。
115+
<p><code>clusterCIDR</code> 字段是集群中 Pod 所使用的 CIDR 范围。
116116
这一地址范围用于对来自集群外的请求流量进行桥接。
117117
如果未设置，则 kube-proxy 不会对非集群内部的流量做桥接。</p>
118118
</td>
@@ -755,10 +755,10 @@ this always falls back to the userspace proxy.
755755

756756
- [KubeProxyConfiguration](#kubeproxy-config-k8s-io-v1alpha1-KubeProxyConfiguration)
757757

758-
- [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta2-KubeSchedulerConfiguration)
759-
760758
- [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta3-KubeSchedulerConfiguration)
761759

760+
- [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta2-KubeSchedulerConfiguration)
761+
762762
- [GenericControllerManagerConfiguration](#controllermanager-config-k8s-io-v1alpha1-GenericControllerManagerConfiguration)
763763

764764
<!--
@@ -833,10 +833,10 @@ default value of 'application/json'. This field will control all connections to
833833
-->
834834
**出现在：**
835835

836-
- [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta2-KubeSchedulerConfiguration)
837-
838836
- [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta3-KubeSchedulerConfiguration)
839837

838+
- [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta2-KubeSchedulerConfiguration)
839+
840840
- [GenericControllerManagerConfiguration](#controllermanager-config-k8s-io-v1alpha1-GenericControllerManagerConfiguration)
841841

842842
<!--
@@ -874,82 +874,6 @@ enableProfiling is true.
874874
</tbody>
875875
</table>
876876

877-
## `FormatOptions` {#FormatOptions}
878-
879-
<!--
880-
**Appears in:**
881-
-->
882-
883-
<!--
884-
FormatOptions contains options for the different logging formats.
885-
-->
886-
FormatOptions 包含不同日志记录格式的配置选项。
887-
888-
889-
<table class="table">
890-
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
891-
<tbody>
892-
893-
894-
<tr><td><code>json</code> <B><!--[Required]-->[必需]</B><br/>
895-
<a href="#JSONOptions"><code>JSONOptions</code></a>
896-
</td>
897-
<td>
898-
<!--
899-
[Experimental] JSON contains options for logging format "json".
900-
-->
901-
<p>[实验特性] <code>json</code> 字段包含 &quot;JSON&quot; 日志格式的配置选项。</p>
902-
</td>
903-
</tr>
904-
</tbody>
905-
</table>
906-
907-
## `JSONOptions` {#JSONOptions}
908-
909-
<!--
910-
**Appears in:**
911-
-->
912-
**出现在：**
913-
914-
- [FormatOptions](#FormatOptions)
915-
916-
<!--
917-
JSONOptions contains options for logging format "json".
918-
-->
919-
JSONOptions 包含 &quot;json&quot; 日志格式的配置选项。
920-
921-
<table class="table">
922-
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
923-
<tbody>
924-
925-
926-
<tr><td><code>splitStream</code> <B><!--[Required]-->[必需]</B><br/>
927-
<code>bool</code>
928-
</td>
929-
<td>
930-
<!--
931-
[Experimental] SplitStream redirects error messages to stderr while
932-
info messages go to stdout, with buffering. The default is to write
933-
both to stdout, without buffering.
934-
-->
935-
<p>[实验特性] <code>splitStream</code> 字段将信息类型的信息输出到标准输出，错误信息重定向到标准
936-
错误输出，并提供缓存。默认行为是将二者都输出到标准输出且不提供缓存。</p>
937-
</td>
938-
</tr>
939-
<tr><td><code>infoBufferSize</code> <B><!--[Required]-->[必需]</B><br/>
940-
<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/api/resource#QuantityValue"><code>k8s.io/apimachinery/pkg/api/resource.QuantityValue</code></a>
941-
</td>
942-
<td>
943-
<!--
944-
[Experimental] InfoBufferSize sets the size of the info stream when
945-
using split streams. The default is zero, which disables buffering.
946-
-->
947-
<p>[实验特性] <code>infoBufferSize</code> 字段设置在使用分离数据流时 info 数据流的缓冲区大小。
948-
默认值为 0，意味着不提供缓存。</p>
949-
</td>
950-
</tr>
951-
</tbody>
952-
</table>
953877

954878
## `LeaderElectionConfiguration` {#LeaderElectionConfiguration}
955879

@@ -1074,110 +998,4 @@ during leader election cycles.
1074998
</td>
1075999
</tr>
10761000
</tbody>
1077-
</table>
1078-
1079-
## `LoggingConfiguration` {#LoggingConfiguration}
1080-
1081-
<!--
1082-
**Appears in:**
1083-
-->
1084-
**出现在：**
1085-
1086-
- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)
1087-
1088-
<!--
1089-
LoggingConfiguration contains logging options
1090-
Refer <a href="https://git.k8s.io/component-base/logs/api/v1/options.go">Logs Options</a> for more information.
1091-
-->
1092-
LoggingConfiguration 包含日志选项。
1093-
参考 [Logs Options](https://git.k8s.io/component-base/logs/api/v1/options.go) 以了解更多信息。
1094-
1095-
<table class="table">
1096-
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
1097-
<tbody>
1098-
1099-
<tr><td><code>format</code> <B><!--[Required]-->[必需]</B><br/>
1100-
<code>string</code>
1101-
</td>
1102-
<td>
1103-
<!--
1104-
Format Flag specifies the structure of log messages.
1105-
default value of format is <code>text</code>
1106-
-->
1107-
<p><code>format</code> 字段设置日志消息的结构。默认的格式取值为 <code>text</code>。</p>
1108-
</td>
1109-
</tr>
1110-
<tr><td><code>flushFrequency</code> <B><!--[Required]-->[必需]</B><br/>
1111-
<a href="https://pkg.go.dev/time#Duration"><code>time.Duration</code></a>
1112-
</td>
1113-
<td>
1114-
<!--
1115-
Maximum number of nanoseconds (i.e. 1s = 1000000000) between log
1116-
flushes. Ignored if the selected logging backend writes log
1117-
messages without buffering.
1118-
-->
1119-
<p>对日志进行清洗的最大间隔纳秒数（例如，1s = 1000000000）。
1120-
如果所选的日志后端在写入日志消息时不提供缓存，则此配置会被忽略。</p>
1121-
</td>
1122-
</tr>
1123-
<tr><td><code>verbosity</code> <B><!--[Required]-->[必需]</B><br/>
1124-
<code>uint32</code>
1125-
</td>
1126-
<td>
1127-
<!--
1128-
Verbosity is the threshold that determines which log messages are
1129-
logged. Default is zero which logs only the most important
1130-
messages. Higher values enable additional messages. Error messages
1131-
are always logged.
1132-
-->
1133-
<p><code>verbosity</code> 字段用来确定日志消息记录的详细程度阈值。
1134-
默认值为 0，意味着仅记录最重要的消息。
1135-
数值越大，额外的消息越多。错误消息总是被记录下来。</p>
1136-
</td>
1137-
</tr>
1138-
<tr><td><code>vmodule</code> <B><!--[Required]-->[必需]</B><br/>
1139-
<a href="#VModuleConfiguration"><code>VModuleConfiguration</code></a>
1140-
</td>
1141-
<td>
1142-
<!--
1143-
VModule overrides the verbosity threshold for individual files.
1144-
Only supported for &quot;text&quot; log format.
1145-
-->
1146-
<p><code>vmodule</code> 字段会在单个文件层面重载 verbosity 阈值的设置。
1147-
这一选项仅支持 &quot;text&quot; 日志格式。</p>
1148-
</td>
1149-
</tr>
1150-
<tr><td><code>options</code> <B>[Required]</B><br/>
1151-
<a href="#FormatOptions"><code>FormatOptions</code></a>
1152-
</td>
1153-
<td>
1154-
<!--
1155-
[Experimental] Options holds additional parameters that are specific
1156-
to the different logging formats. Only the options for the selected
1157-
format get used, but all of them get validated.
1158-
-->
1159-
<p>[实验特性] <code>options</code> 字段中包含特定于不同日志格式的配置参数。
1160-
只有针对所选格式的选项会被使用，但是合法性检查时会查看所有选项配置。</p>
1161-
</td>
1162-
</tr>
1163-
</tbody>
1164-
</table>
1165-
1166-
## `VModuleConfiguration` {#VModuleConfiguration}
1167-
1168-
<!--
1169-
(Alias of `[]k8s.io/component-base/config/v1alpha1.VModuleItem`)
1170-
1171-
**Appears in:**
1172-
-->
1173-
（`[]k8s.io/component-base/config/v1alpha1.VModuleItem` 的别名）
1174-
1175-
**出现在：**
1176-
1177-
- [LoggingConfiguration](#LoggingConfiguration)
1178-
1179-
<!--
1180-
VModuleConfiguration is a collection of individual file names or patterns
1181-
and the corresponding verbosity threshold.
1182-
-->
1183-
VModuleConfiguration 是一组文件名或文件名模式，及其对应的日志详尽程度阈值配置。
1001+
</table>

0 commit comments

Comments
 (0)