mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
translate 08 chapter 03&04 and delete routes
Signed-off-by: zhuxiujuan28 <562873187@qq.com>
This commit is contained in:
zhuxiujuan28
parent
a00c1035ac
commit
10333bc5cb
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: ac11303d404249078087f1c605445e15
|
||||
. Log in to the {ks_product-en} web console with a user who has pass:a,q[{ks_permission}] permissions, and access your cluster.
|
||||
. Log in to the {ks_product-en} web console with a user who has the pass:a,q[{ks_permission}] permission, and access your cluster.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 7f14023bc6974772b201bc6c0b92e13b
|
||||
本节介绍如何创建任务。
|
||||
This section explains how to create jobs.
|
||||
|
|
@ -1,8 +1,11 @@
|
|||
// :ks_include_id: 53cddf67368844919fec7ab2ca897ef6
|
||||
本节介绍如何删除任务。
|
||||
This section explains how to delete a job.
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/warning.adoc[]
|
||||
//warning
|
||||
[.admon.warning,cols="a"]
|
||||
|===
|
||||
| Warning
|
||||
|
||||
此操作将删除任务及其管理的所有容器组，如果任务正在运行，运行中的业务将中断，请谨慎执行此操作。
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
||||
This operation will delete the job and all pods managed by it. If the job is running, the business running in it will be interrupted. Please proceed with caution.
|
||||
|===
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: b4a8007c076840f1aaef0251117dd232
|
||||
本节介绍如何编辑任务信息。
|
||||
This section explains how to edit job information.
|
||||
|
||||
您可以编辑任务的别名和描述。{ks_product-en}不支持编辑已创建任务的名称。
|
||||
You can edit the alias and description of the job. KubeSphere does not support editing the name of an already created job.
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
// :ks_include_id: 3965f0c407e24d6dae5c945b45abbd6e
|
||||
本节介绍如何管理任务。
|
||||
This section explains how to manage jobs.
|
||||
|
||||
在{ks_product-en}平台上，应用程序运行在容器组中。任务用于管理仅运行一次或周期性运行的容器组。{ks_product-en}平台支持以下任务类型：
|
||||
In KubeSphere, applications run in pods. Jobs are used to manage pods that run either once or periodically. KubeSphere supports the following types of jobs:
|
||||
|
||||
* 普通任务：用于管理仅运行一次的容器组。如果容器组运行失败，系统将根据任务中设置的策略重启容器组，直到满足特定条件。
|
||||
* Jobs: Used to manage pods that run only once. If a pod runs failed, the system will restart the pod according to the policies set in the job until specific conditions are met.
|
||||
|
||||
* 定时任务：用于管理周期性运行的容器组。系统根据定时任务中设置的周期创建普通任务并运行。每次运行容器组时，如果容器组运行失败，定时任务都将根据用户设置的策略重启容器组，直到满足特定条件。
|
||||
* CronJobs: Used to manage pods that run periodically. The system creates regular jobs based on the schedule set in the CronJob and runs them accordingly. Each time when the pod runs, if it fails, the CronJob will restart the pod according to the policies set by the user until specific conditions are met.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: a773823d564e4c93b67e89f11ac3bc64
|
||||
本节介绍如何暂停定时任务。
|
||||
This section explains how to pause a CronJob.
|
||||
|
||||
定时任务暂停后，系统将不会在未来计划的时间点创建任务并运行，正在运行的任务不受影响。此操作仅对定时任务可用。
|
||||
After pausing a CronJob, the system will not create and run jobs at the scheduled time in the future. Running jobs are not affected. This operation is only available for CronJobs.
|
||||
|
|
@ -1,9 +1,11 @@
|
|||
// :ks_include_id: 81c337c82d7743cba51347779b603d00
|
||||
本节介绍如何重新运行任务。此操作仅对普通任务可用。
|
||||
This section explains how to re-run a job. This operation is only available for regular jobs.
|
||||
|
||||
// Note
|
||||
include::../../../../_ks_components-en/admonitions/note.adoc[]
|
||||
//note
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|Note
|
||||
|
||||
{ks_product-en}仅允许重新运行已结束的任务。正在运行中的任务不支持此操作。
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
||||
KubeSphere only supports re-running jobs that have already completed, rather than jobs that are currently running.
|
||||
|===
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 941b85f6a2d149249751ac5843925f97
|
||||
设置任务的标签和注解。
|
||||
Configure labels and annotations for the job.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: d134e4938b2447beadf1dfb8261c70a1
|
||||
本节介绍如何查看任务列表。
|
||||
This section explains how to view the job list.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 3d8cf6ff7e434f25b6e0854742aaf84d
|
||||
本节介绍如何查看任务详情。
|
||||
This section explains how to view job details.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,12 @@
|
|||
// :ks_include_id: ade6d86d1f0d4f1db635fb9dd96b2348
|
||||
. 在**基本信息**页签，设置任务的基本信息，以及定时任务策略，然后点击**下一步**。
|
||||
. On the **Basic Information** tab, configure the basic information of the job, as well as the scheduling strategy for a CronJob. Then click **Next**.
|
||||
|
||||
. 在**策略设置**页签，设置单次任务的策略，然后点击**下一步**。
|
||||
. On the **Strategy Settings** tab, configure the strategy for a one-time job, and then click **Next**.
|
||||
|
||||
. 在**容器组设置**页签，为任务管理的容器组设置重启策略和容器，然后点击**下一步**。
|
||||
. On the **Pod Settings** tab, set restart policies and containers for the pods managed by the job. Then click **Next**.
|
||||
|
||||
. 在**存储设置**页签，为任务管理的容器挂载卷，然后点击**下一步**。
|
||||
. On the **Storage Settings** tab, mount volumes for the containers managed by the job. Then click **Next**.
|
||||
|
||||
. 在**高级设置**页签，为任务管理的容器组指定 IP 池和节点，并设置任务的元数据，然后点击**创建**。任务创建完成后将显示在任务列表中。
|
||||
. On the **Advanced Settings** tab, specify nodes for the pods managed by the job, and set metadata for the job. Then click **Create**.
|
||||
+
|
||||
Once the job is created, it will be displayed in the job list.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: 3e648f1c3f8d41a0a4ff221ad9efd72d
|
||||
. 在需要删除的任务右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**删除**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right of the job you want to delete, then choose **Delete** from the dropdown list.
|
||||
|
||||
. 在**删除任务**对话框，输入任务的名称，然后点击**确定**。
|
||||
. In the **Delete Job** dialog, enter the name of the job, then click **OK**.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
// :ks_include_id: ae8fc7f6ef7a43999d61c74c6fa39fe5
|
||||
. 选择需要删除的任务左侧的复选框，然后在任务列表上方点击**删除**。
|
||||
. Select the checkbox on the left of the jobs you want to delete, then click **Delete** above the job list.
|
||||
|
||||
. 在**批量删除任务**对话框，输入任务的名称，然后点击**确定**。
|
||||
. In the **Delete Multiple Jobs** dialog, enter the name of the jobs, then click **OK**.
|
||||
+
|
||||
--
|
||||
include::../../note-separateNamesByComma.adoc[]
|
||||
|
|
|
|||
|
|
@ -1,17 +1,17 @@
|
|||
// :ks_include_id: 71ed2df8398646ea982d8084536b45d9
|
||||
. 在需要操作的任务右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**编辑信息**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right of the job you want to edit, then choose **Edit Information** from the dropdown list.
|
||||
|
||||
. 在**编辑信息**对话框，设置任务的别名和描述，然后点击**确定**。
|
||||
. In the **Edit Information** dialog, set the alias and description for the job, then click **OK**.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|别名
|
||||
|任务的别名。不同任务的别名可以相同。别名只能包含中文、字母、数字和连字符（-），不得以连字符（-）开头或结尾，最长 63 个字符。
|
||||
| Alias
|
||||
| The alias of the job. Aliases can be the same for different jobs. An alias can only contain Chinese characters, letters, numbers, and hyphens (-). It cannot start or end with a hyphen (-) and has a maximum length of 63 characters.
|
||||
|
||||
|描述
|
||||
|任务的描述信息。描述可包含任意字符，最多包含 256 个字符。
|
||||
| Description
|
||||
| The description for the job. The description can contain any characters, with a maximum length of 256 characters.
|
||||
|===
|
||||
--
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: ca11e2b37deb4d04aa5fa7241ff673c9
|
||||
. 在**任务**页面，点击**任务**或**定时任务**，然后在列表中点击一个任务的名称打开其详情页面。
|
||||
. On the **Job** page, click either **Job** or **CronJob**, then click the name of a job in the list to open its details page.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 8619d925ec5a486cae57b4b228b668b2
|
||||
. 在**任务**页面，点击**任务**或**定时任务**打开任务列表。
|
||||
. On the **Jobs** page, click either **Jobs** or **CronJobs** to open the list of jobs.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: eae4a035080a4f1bb09cb87fc6034aed
|
||||
. 在需要操作的定时任务右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**暂停**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right of the CronJob you want to pause, then choose **Pause** from the dropdown list.
|
||||
|
||||
. 如需恢复定时任务运行，在需要操作的定时任务右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**启动**。
|
||||
. To resume the CronJob, Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right side of the CronJob you want to start, then choose **Start** from the dropdown list.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 24f7afe576124e6396922b7bd7234929
|
||||
. 在需要操作的任务右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**重新运行**。任务将重新按照用户设置的策略重新开始运行。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right of the job you want to re-run, then choose **Rerun** from the dropdown list. The job will restart according to the defined policy.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: cc4f326315a24232ba3df5a314ef63f3
|
||||
* 在列表上方点击搜索框并设置搜索条件，可按名称或状态搜索任务。
|
||||
* Click the search box at the top of the list and search for jobs by name or status.
|
||||
|
|
@ -1,144 +0,0 @@
|
|||
// :ks_include_id: ae48f9c2af1e46bca4bede49d4447413
|
||||
. 在任务详情页面左侧的**属性**区域查看任务的资源属性。
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|集群
|
||||
|任务所属的集群。
|
||||
|
||||
|项目
|
||||
|任务所属的项目。
|
||||
|
||||
|状态
|
||||
|
|
||||
任务当前的状态。
|
||||
|
||||
include::jobs-para-jobStatus.adoc[]
|
||||
|
||||
|最大重试次数
|
||||
|任务中的容器组可以重启的最大次数。如果达到最大重试次数仍未满足任务完成条件，任务将被标记为失败。仅对普通任务显示。
|
||||
|
||||
|容器组完成数量
|
||||
|将任务标记为完成所需成功完成的容器组数量。仅对普通任务显示。
|
||||
|
||||
|并行容器组数量
|
||||
|任务中并行运行的容器组副本数量。仅对普通任务显示。
|
||||
|
||||
|最大运行时间
|
||||
|任务的最大运行时间，单位为秒。如果达到最大运行时间仍未满足任务完成条件，任务将被终止并被标记为失败。仅对普通任务显示。
|
||||
|
||||
|定时计划
|
||||
|定时任务运行周期的 CRON 表达式。仅对定时任务显示。
|
||||
|
||||
|最大启动延后时间
|
||||
|由于某种原因未能按计划启动任务时，任务启动的最大延后时间。仅对定时任务显示。
|
||||
|
||||
|成功任务保留数量
|
||||
|允许保留的成功任务的个数。默认值为 3。仅对定时任务显示。
|
||||
|
||||
|失败任务保留数量
|
||||
|允许保留的失败任务的个数。默认值为 1。仅对定时任务显示。
|
||||
|
||||
|并发策略
|
||||
|定时任务创建的多个任务发生重叠时系统采取的策略。
|
||||
|
||||
* **同时运行任务**：新任务和旧任务并发运行。
|
||||
|
||||
* **跳过新任务**：不运行新任务。
|
||||
|
||||
* **跳过旧任务**：立即终止旧任务然后运行新任务。
|
||||
|
||||
仅对定时任务显示。
|
||||
|
||||
|创建时间
|
||||
|任务的创建时间。
|
||||
|
||||
|创建者
|
||||
|创建任务的用户。
|
||||
|===
|
||||
--
|
||||
|
||||
. 在任务详情页面右侧的**运行记录**页签查看任务的运行记录。
|
||||
+
|
||||
--
|
||||
用户手动重新运行普通任务或定时任务按照定时计划运行时，系统将生成运行记录。
|
||||
|
||||
对于定时任务，**运行记录**页签显示以下信息：
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|序号
|
||||
|任务运行的序号，表示每条记录是任务第几次运行。
|
||||
|
||||
|状态
|
||||
|每次运行任务的状态结果。
|
||||
|
||||
include::jobs-para-jobStatus.adoc[]
|
||||
|
||||
* **未完成**：任务运行过程中用户手动重新运行任务。
|
||||
|
||||
|消息
|
||||
|任务运行返回的消息。
|
||||
|
||||
|开始时间
|
||||
|任务运行开始运行的时间。
|
||||
|
||||
|结束时间
|
||||
|任务运行结束的时间。
|
||||
|===
|
||||
|
||||
对于普通任务，**运行记录**页签显示以下信息：
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|任务
|
||||
|定时任务创建的普通任务的名称。
|
||||
|
||||
|状态
|
||||
|定时任务创建的普通任务的状态。
|
||||
|
||||
include::jobs-para-jobStatus.adoc[]
|
||||
|
||||
|开始时间
|
||||
|定时任务的普通任务开始运行的创建时间。
|
||||
|
||||
|结束时间
|
||||
|任务运行结束的时间。
|
||||
|===
|
||||
--
|
||||
|
||||
. 对于普通任务，在任务详情页面右侧点击**资源状态**页签查看任务中的容器端口和容器组。
|
||||
+
|
||||
--
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|端口
|
||||
|任务中的容器的端口名称、协议和端口号。
|
||||
|
||||
|容器组
|
||||
|
|
||||
任务中的容器组。
|
||||
|
||||
include::../nodes/nodes-para-podList.adoc[]
|
||||
|===
|
||||
--
|
||||
|
||||
. 在任务详情页面右侧点击**元数据**页签查看任务的标签和注解。
|
||||
|
||||
. 对于普通任务，在任务详情页面右侧点击**环境变量**页签查看任务中的所有容器的环境变量。
|
||||
|
||||
. 在任务详情页面右侧点击**事件**页签查看任务相关的事件。
|
||||
+
|
||||
--
|
||||
include::../clusterManagement-para-eventsTab.adoc[]
|
||||
--
|
||||
|
|
@ -1,143 +1,140 @@
|
|||
// :ks_include_id: ae48f9c2af1e46bca4bede49d4447413
|
||||
. 在任务详情页面左侧的**属性**区域查看任务的资源属性。
|
||||
. In the left **Attributes** area on the job details page, view the resource attributes of the job.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|集群
|
||||
|任务所属的集群。
|
||||
| Cluster
|
||||
| The cluster to which the job belongs.
|
||||
|
||||
|项目
|
||||
|任务所属的项目。
|
||||
| Project
|
||||
| The project to which the job belongs.
|
||||
|
||||
|状态
|
||||
| Status
|
||||
|
|
||||
任务当前的状态。
|
||||
The current status of the job.
|
||||
|
||||
include::jobs-para-jobStatus.adoc[]
|
||||
|
||||
|最大重试次数
|
||||
|任务中的容器组可以重启的最大次数。如果达到最大重试次数仍未满足任务完成条件，任务将被标记为失败。仅对普通任务显示。
|
||||
| Maximum Retries
|
||||
| The maximum number of times the pods in the job can be restarted. If the maximum retries is reached but the job completion conditions are still not met, the job will be marked as failed. Available only for Jobs.
|
||||
|
||||
|容器组完成数量
|
||||
|将任务标记为完成所需成功完成的容器组数量。仅对普通任务显示。
|
||||
| Complete Pods
|
||||
| The number of completed pods required to mark the job as completed. Available only for Jobs.
|
||||
|
||||
|并行容器组数量
|
||||
|任务中并行运行的容器组副本数量。仅对普通任务显示。
|
||||
| Parallel Pods
|
||||
| The number of pods that run in parallel in the job. Available only for Jobs.
|
||||
|
||||
|最大运行时间
|
||||
|任务的最大运行时间，单位为秒。如果达到最大运行时间仍未满足任务完成条件，任务将被终止并被标记为失败。仅对普通任务显示。
|
||||
| Maximum Duration
|
||||
| The maximum running time for the job, in seconds. If the maximum duration is reached but the job completion conditions are still not met, the job will be terminated and marked as failed. Available only for Jobs.
|
||||
|
||||
|定时计划
|
||||
|定时任务运行周期的 CRON 表达式。仅对定时任务显示。
|
||||
| Schedule
|
||||
| The CRON expression specifying the runtime cycle for a CronJob. KubeSphere defaults to UTC time, and you may need to adjust it based on your time zone. Available only for CronJobs.
|
||||
|
||||
|最大启动延后时间
|
||||
|由于某种原因未能按计划启动任务时，任务启动的最大延后时间。仅对定时任务显示。
|
||||
| Maximum Startup Delay
|
||||
| The maximum delay before starting a job when it fails to start according to the schedule. Available only for CronJobs.
|
||||
|
||||
|成功任务保留数量
|
||||
|允许保留的成功任务的个数。默认值为 3。仅对定时任务显示。
|
||||
| Successful Jobs Retention
|
||||
| The number of successful jobs allowed to be retained, with a default value of **3**. Each time a CronJob runs, it creates a job, and you can specify the number of jobs to retain as a historical record. Available only for CronJobs.
|
||||
|
||||
|失败任务保留数量
|
||||
|允许保留的失败任务的个数。默认值为 1。仅对定时任务显示。
|
||||
| Failed Jobs Retention
|
||||
| The number of failed jobs allowed to be retained, with a default value of **1**. Each time a CronJob runs, it creates a job, and you can specify the number of jobs to retain as a historical record. Available only for CronJobs.
|
||||
|
||||
|并发策略
|
||||
|定时任务创建的多个任务发生重叠时系统采取的策略。
|
||||
| Concurrency Policy
|
||||
| The policy the system adopts when multiple jobs created by a CronJob overlap. Available only for CronJobs. It includes the following polices:
|
||||
|
||||
* **同时运行任务**：新任务和旧任务并发运行。
|
||||
* **Run jobs concurrently**: New and old jobs run concurrently.
|
||||
|
||||
* **跳过新任务**：不运行新任务。
|
||||
* **Skip new job**: Do not run new jobs.
|
||||
|
||||
* **跳过旧任务**：立即终止旧任务然后运行新任务。
|
||||
* **Skip old job**: Immediately terminates old jobs and then runs new jobs.
|
||||
|
||||
仅对定时任务显示。
|
||||
| Creation Time
|
||||
| The creation time of the job.
|
||||
|
||||
|创建时间
|
||||
|任务的创建时间。
|
||||
|
||||
|创建者
|
||||
|创建任务的用户。
|
||||
| Creator
|
||||
| The user who created the job.
|
||||
|===
|
||||
--
|
||||
|
||||
. 在任务详情页面右侧的**运行记录**页签查看任务的运行记录。
|
||||
. On the right **Run Records** tab on the job details page, view the run records of the job.
|
||||
+
|
||||
--
|
||||
用户手动重新运行普通任务或定时任务按照定时计划运行时，系统将生成运行记录。
|
||||
When users re-run a Job manually or run a CronJob according to the schedule, the system generates run records.
|
||||
|
||||
对于普通任务，**运行记录**页签显示以下信息：
|
||||
For Jobs, the **Run Records** tab displays the following information:
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|序号
|
||||
|任务运行的序号，表示每条记录是任务第几次运行。
|
||||
| No.
|
||||
| The serial number of the job, indicating the sequence of each run.
|
||||
|
||||
|状态
|
||||
|每次运行任务的状态结果。
|
||||
| Status
|
||||
| The status result of each run of the job.
|
||||
|
||||
include::jobs-para-jobStatus.adoc[]
|
||||
|
||||
* **未完成**：任务运行过程中用户手动重新运行任务。
|
||||
* **Incomplete**: Manually rerun the job during the job running.
|
||||
|
||||
|消息
|
||||
|任务运行返回的消息。
|
||||
| Message
|
||||
| The message returned by the run.
|
||||
|
||||
|开始时间
|
||||
|任务运行开始运行的时间。
|
||||
| Start Time
|
||||
| The time the run started.
|
||||
|
||||
|结束时间
|
||||
|任务运行结束的时间。
|
||||
| End Time
|
||||
| The time the run ended.
|
||||
|===
|
||||
|
||||
对于定时任务，**运行记录**页签显示以下信息：
|
||||
For CronJobs, the **Run Records** tab displays the following information:
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|任务
|
||||
|定时任务创建的普通任务的名称。
|
||||
| Job
|
||||
| The name of the job created by the CronJob.
|
||||
|
||||
|状态
|
||||
|定时任务创建的普通任务的状态。
|
||||
| Status
|
||||
| The status of the job created by the CronJob.
|
||||
|
||||
include::jobs-para-jobStatus.adoc[]
|
||||
|
||||
|开始时间
|
||||
|定时任务的普通任务开始运行的创建时间。
|
||||
| Start Time
|
||||
| The start time of the job created by the CronJob.
|
||||
|
||||
|结束时间
|
||||
|任务运行结束的时间。
|
||||
| End Time
|
||||
| The time the run ended.
|
||||
|===
|
||||
--
|
||||
|
||||
. 对于普通任务，在任务详情页面右侧点击**资源状态**页签查看任务中的容器组副本数和容器组。
|
||||
. For Jobs, Click the **Resource Status** tab on the right of the job details page to view the number of pod replicas and pods in the job.
|
||||
+
|
||||
--
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|副本
|
||||
|任务中的容器组副本数。
|
||||
| Replicas
|
||||
| The number of pod replicas in the job.
|
||||
|
||||
|容器组
|
||||
|
|
||||
任务中的容器组。
|
||||
| Pods
|
||||
| The pods running for the job.
|
||||
|
||||
include::../nodes/nodes-para-podList.adoc[]
|
||||
|===
|
||||
--
|
||||
|
||||
. 在任务详情页面右侧点击**元数据**页签查看任务的标签和注解。
|
||||
. Click the **Metadata** tab on the right of the job details page to view the labels and annotations of the job.
|
||||
|
||||
. 对于普通任务，在任务详情页面右侧点击**环境变量**页签查看任务中的所有容器的环境变量。
|
||||
. For Jobs, Click the **Environment Variables** tab on the right of the job details page to view the environment variables of all containers in the job.
|
||||
|
||||
. 在任务详情页面右侧点击**事件**页签查看任务相关的事件。
|
||||
. Click the **Events** tab on the right of the job details page to view events related to the job.
|
||||
+
|
||||
--
|
||||
include::../clusterManagement-para-eventsTab.adoc[]
|
||||
|
|
|
|||
|
|
@ -1,42 +1,41 @@
|
|||
// :ks_include_id: b3230b385e724f75b412f086ba00503e
|
||||
* 基本信息
|
||||
* Basic Information
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|名称
|
||||
|任务的名称。名称只能包含小写字母、数字和连字符（-），必须以小写字母或数字开头和结尾，最长 63 个字符。
|
||||
| Name
|
||||
| The name of the job. The name can only contain lowercase letters, numbers, and hyphens (-). It must start and end with a lowercase letter or number, with a maximum length of 63 characters.
|
||||
|
||||
|别名
|
||||
|任务的别名。不同任务的别名可以相同。别名只能包含中文、字母、数字和连字符（-），不得以连字符（-）开头或结尾，最长 63 个字符。
|
||||
| Alias
|
||||
| The alias of the job. Aliases can be the same for different jobs. The alias can only contain Chinese characters, letters, numbers, and hyphens (-). It must not start or end with a hyphen (-), with a maximum length of 63 characters.
|
||||
|
||||
|项目
|
||||
|任务所属的项目。系统项目通常用于管理系统资源，建议选择用户项目。
|
||||
| Project
|
||||
| The project to which the job belongs. It is recommended to choose a user project, as system projects are typically used for managing system resources.
|
||||
|
||||
|描述
|
||||
|任务的描述信息。描述可包含任意字符，最长 256 个字符。
|
||||
| Description
|
||||
| The description of the job. The description can contain any characters, with a maximum length of 256 characters.
|
||||
|
||||
|定时计划
|
||||
|定时任务的运行周期的 CRON 表达式。{ks_product-en}默认使用 UTC 时间，您需要根据您所在的时区进行调整。仅对**定时任务**可用。
|
||||
| Schedule
|
||||
| The CRON expression specifying the runtime cycle for a CronJob. KubeSphere defaults to UTC time, and you may need to adjust it based on your time zone. Available only for CronJobs.
|
||||
|
||||
|最大启动延后时间
|
||||
|由于某种原因未能按计划启动任务时，任务启动的最大延后时间。仅对**定时任务**可用。
|
||||
| Maximum Startup Delay
|
||||
| The maximum delay before starting a job when it fails to start according to the schedule. Available only for CronJobs.
|
||||
|
||||
|成功任务保留数量
|
||||
|允许保留的成功任务的个数，默认值为 **3**。定时任务每次运行都会创建任务，您可以指定保留一定数量的任务作为历史记录。仅对**定时任务**可用。
|
||||
| Successful Jobs Retention
|
||||
| The number of successful jobs allowed to be retained, with a default value of **3**. Each time a CronJob runs, it creates a job, and you can specify the number of jobs to retain as a historical record. Available only for CronJobs.
|
||||
|
||||
|失败任务保留数量
|
||||
|允许保留的失败任务的个数，默认值为 **1**。定时任务每次运行都会创建任务，您可以指定保留一定数量的任务作为历史记录。仅对**定时任务**可用。
|
||||
| Failed Jobs Retention
|
||||
| The number of failed jobs allowed to be retained, with a default value of **1**. Each time a CronJob runs, it creates a job, and you can specify the number of jobs to retain as a historical record. Available only for CronJobs.
|
||||
|
||||
|并发策略
|
||||
|定时任务创建的多个任务发生重叠时，系统采取的策略。仅对**定时任务**可用。包括以下策略类型：
|
||||
| Concurrency Policy
|
||||
| The policy the system adopts when multiple jobs created by a CronJob overlap. Available only for CronJobs. It includes the following policies:
|
||||
|
||||
* **同时运行任务**：新任务和旧任务并发运行。
|
||||
* **Run jobs concurrently**: New and old jobs run concurrently.
|
||||
|
||||
* **跳过新任务**：不运行新任务。
|
||||
* **Skip new job**: Do not run new jobs.
|
||||
|
||||
* **跳过旧任务**：立即终止旧任务然后运行新任务。
|
||||
* **Skip old job**: Immediately terminates old jobs and then runs new jobs.
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,28 +1,27 @@
|
|||
// :ks_include_id: f4fbda985b234075830531d6835efefe
|
||||
* 任务列表提供以下信息：
|
||||
* The job list provides the following information:
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|名称
|
||||
|任务的名称和描述信息。
|
||||
| Name
|
||||
| The name and description of the job.
|
||||
|
||||
|状态
|
||||
| Status
|
||||
|
|
||||
任务当前的状态。
|
||||
The current status of the job.
|
||||
|
||||
* **运行中**：任务正在运行中。
|
||||
* **Running**: The job is running.
|
||||
|
||||
* **已完成**：任务运行成功并且已完成。
|
||||
* **Completed**: The job has run successfully and is completed.
|
||||
|
||||
* **失败**：任务运行失败。
|
||||
* **Failed**: The job has failed.
|
||||
|
||||
|项目
|
||||
|任务所属的项目。
|
||||
| Project
|
||||
| The project to which the job belongs.
|
||||
|
||||
|上次运行时间
|
||||
|任务上一次运行的时间。
|
||||
| Last Run Time
|
||||
| The time of the last run for the job.
|
||||
|===
|
||||
--
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
// :ks_include_id: 88bc02980e93473eaec099d0e0f6b2c4
|
||||
* **运行中**：任务正在运行中。
|
||||
* **Running**: The job is running.
|
||||
|
||||
* **已完成**：任务运行成功并且已完成。
|
||||
* **Completed**: The job has run successfully and is completed.
|
||||
|
||||
* **失败**：任务运行失败。
|
||||
* **Failed**: The job has failed.
|
||||
|
|
@ -1,17 +1,16 @@
|
|||
// :ks_include_id: e492eb63e19b4c8d88cb2d2a4b800815
|
||||
* 容器组设置 > 重启策略
|
||||
* Pod Settings > Restart Policy
|
||||
+
|
||||
--
|
||||
设置容器运行失败时系统采取的策略。
|
||||
Select the policy the system adopts when a container in the pod fails to run.
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|重新创建容器组
|
||||
|系统将重新创建整个容器组。
|
||||
| Re-create pod
|
||||
| The system will recreate the entire pod.
|
||||
|
||||
|重启容器
|
||||
|系统将重启容器。
|
||||
| Restart container
|
||||
| The system will restart the container.
|
||||
|===
|
||||
--
|
||||
|
|
@ -1,23 +1,22 @@
|
|||
// :ks_include_id: fefe006cd58c414c825a62b8b3066867
|
||||
* 策略设置
|
||||
* Strategy Settings
|
||||
+
|
||||
--
|
||||
设置每次运行任务的策略。
|
||||
Configure the strategy for each job.
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|最大重试次数
|
||||
|任务中的容器组可以重启的最大次数。如果达到最大重试次数仍未满足任务完成条件，任务将被标记为失败。
|
||||
| Maximum Retries
|
||||
| The maximum number of times the pods in the job can be restarted. If the maximum retries is reached but the job completion conditions are still not met, the job will be marked as failed.
|
||||
|
||||
|容器组完成数量
|
||||
|将任务标记为完成所需成功完成的容器组数量。
|
||||
| Complete Pods
|
||||
| The number of completed pods required to mark the job as completed.
|
||||
|
||||
|并行容器组数量
|
||||
|任务中并行运行的容器组副本数量。
|
||||
| Parallel Pods
|
||||
| The number of pods that run in parallel in the job.
|
||||
|
||||
|最大运行时间
|
||||
|任务的最大运行时间，单位为秒。如果达到最大运行时间仍未满足任务完成条件，任务将被终止并被标记为失败。
|
||||
| Maximum Duration
|
||||
| The maximum running time for the job, in seconds. If the maximum duration is reached but the job completion conditions are still not met, the job will be terminated and marked as failed.
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
// :ks_include_id: 03868826ceca4baea8a9365de6974f02
|
||||
持久卷的读写模式。
|
||||
The access modes of Persistent Volumes.
|
||||
|
||||
* **RWO**（ReadWriteOnce）：允许单个节点读取持久卷中的数据并向其中写入数据。
|
||||
* **RWO** (ReadWriteOnce): Allows a single node to read from and write to the Persistent Volume.
|
||||
|
||||
* **ROX**（ReadOnlyMany）：允许多个节点读取持久卷中的数据。
|
||||
* **ROX** (ReadOnlyMany): Allows multiple nodes to read from the Persistent Volume.
|
||||
|
||||
* **RWX**（ReadWriteMany）：允许多个节点读取持久卷中的数据并向其中写入数据。
|
||||
* **RWX** (ReadWriteMany): Allows multiple nodes to read from and write to the Persistent Volume.
|
||||
|
|
@ -1,9 +1,11 @@
|
|||
// :ks_include_id: 3bb6ac8d7b114854992775f89ab8debb
|
||||
本节介绍如何访问容器终端。
|
||||
This section introduces how to access the container terminal.
|
||||
|
||||
// Note
|
||||
include::../../../../_ks_components-en/admonitions/note.adoc[]
|
||||
//note
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|Note
|
||||
|
||||
{ks_product-en}仅支持访问正在运行中容器的终端。
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
||||
KubeSphere only supports accessing the terminal of running containers.
|
||||
|===
|
||||
|
|
@ -1,18 +1,22 @@
|
|||
// :ks_include_id: 12077b1940064dbc91b46df1bb4d2390
|
||||
本节介绍如何删除容器组。
|
||||
This section explains how to delete a pod.
|
||||
|
||||
// Note
|
||||
include::../../../../_ks_components-en/admonitions/note.adoc[]
|
||||
//note
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|Note
|
||||
|
||||
* 建议通过删除容器组的管理资源（例如工作负载或任务）来删除容器组，而不是直接删除容器组。
|
||||
|
|
||||
* It is recommended to delete a pod by removing its managing resources (e.g., workloads or jobs) rather than directly deleting the pod.
|
||||
|
||||
* 如果您直接删除容器组，取决于容器组管理资源的策略，系统可能会重新创建容器组。
|
||||
* If you directly delete the pod, depending on the policy of the managing resources, the system may recreate the pod.
|
||||
|===
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
//warning
|
||||
[.admon.warning,cols="a"]
|
||||
|===
|
||||
|Warning
|
||||
|
||||
// Warning
|
||||
include::../../../../_ks_components-en/admonitions/warning.adoc[]
|
||||
|
||||
删除正在运行的容器组可能会导致业务中断，请谨慎执行此操作。
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
||||
Deleting a running pod may cause a service interruption. Please proceed with caution.
|
||||
|===
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
// :ks_include_id: 6a773c6c880441b0b453c3426a19cc8e
|
||||
本节介绍如何管理容器组。
|
||||
This section explains how to manage pods.
|
||||
|
||||
在{ks_product-en}平台上，容器组是应用程序的最小管理单元。每个容器组包含一个或多个容器。同一个容器组的多个容器紧密耦合在一起，一同调度并且共享网络。容器组相当于应用程序的逻辑主机。
|
||||
In KubeSphere, a pod is the smallest management unit of an application. Each pod contains one or more containers. Multiple containers within the same pod are tightly coupled, scheduled, and share the same network. A pod is equivalent to the logical host of an application.
|
||||
|
||||
{ks_product-en} Web 控制台不支持单独创建容器组。您可以通过创建工作负载或任务间接创建容器组并对多个容器组副本进行管理。
|
||||
The {ks_product-en} web console does not support creating pods directly, but you can indirectly create pods and manage pod replicas by creating workloads or jobs.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 28a0c6fdb89548bb9027842de7697721
|
||||
本节介绍如何查看容器组列表。
|
||||
This section explains how to view the list of pods.
|
||||
|
|
@ -1,9 +1,11 @@
|
|||
// :ks_include_id: 25f413cc757b4a79b6dd8d953602f1e9
|
||||
本节介绍如何查看容器详情。
|
||||
This section explains how to view container details.
|
||||
|
||||
// Note
|
||||
include::../../../../_ks_components-en/admonitions/note.adoc[]
|
||||
//note
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|Note
|
||||
|
||||
{ks_product-en}仅支持查看运行中的容器的详情，不支持查看已停止运行的容器的详情。
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
||||
KubeSphere only supports viewing details of running containers, rather than containers that have already stopped running.
|
||||
|===
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 48b9b884c6114c8d9481866c41eda79c
|
||||
本节介绍如何查看容器组详情。
|
||||
This section explains how to view pod details.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: 1d8e328225714a61970419e6ff20593a
|
||||
. 在**资源状态**页签的**容器**区域，在容器名称右侧点击image:/images/ks-qkcp/zh/icons/terminal.svg[terminal,18,18]打开容器终端。您可以使用容器终端在容器内部执行命令。
|
||||
. On the **Resource Status** tab, in the **Containers** section, click image:/images/ks-qkcp/zh/icons/terminal.svg[terminal,18,18] on the right side of the container name to open the container terminal . You can use the terminal to run commands inside the container.
|
||||
|
||||
. 在容器终端页面右上角的下拉列表中选择容器，可快速访问同一个容器组中其他容器的终端。
|
||||
. In the dropdown list at the top right corner of the container terminal page, select a container to quickly access the terminal of other containers in the same pod.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: 2a8675daa13541ae83846c5eb87d5ed7
|
||||
. 在需要删除的容器组右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**删除**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right of the pod you want to delete, then choose **Delete** from the dropdown list.
|
||||
|
||||
. 在**删除容器组**对话框，输入容器组的名称，然后点击**确定**。
|
||||
. In the **Delete Pod** dialog, enter the name of the pod, then click **OK**.
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
// :ks_include_id: c221a68eab6c49a89248bbc09f41a6f6
|
||||
. 选择需要删除的容器组左侧的复选框，然后在容器组列表上方点击**删除**。
|
||||
. Select the checkbox on the left of the pods you want to delete, then click **Delete** above the pod list.
|
||||
|
||||
. 在**批量删除容器组**对话框，输入容器组的名称，然后点击**确定**。
|
||||
. In the **Delete Multiple Pods** dialog, enter the name of the pods, then click **OK**.
|
||||
+
|
||||
--
|
||||
include::../../note-separateNamesByComma.adoc[]
|
||||
--
|
||||
--
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 30ad6c73ec764c0bab8d3e7638696a4a
|
||||
. 在容器组列表中点击一个容器组的名称打开其详情页面。
|
||||
. Click the name of a pod in the pod list to open its details page.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 991e787c19f9470cbc29655c78ddda5d
|
||||
* 在列表上方点击搜索框并设置搜索条件，可按名称、状态或容器组 IP 地址搜索容器组。
|
||||
* Click the search box at the top of the list and search for pods by name, status or pod IP address.
|
||||
|
|
|
|||
|
|
@ -1,70 +1,59 @@
|
|||
// :ks_include_id: 8517e102a81e4402a8f9784a7931ff0c
|
||||
. 在容器组详情页面右侧的**资源状态**页签，在**容器**区域点击一个容器的名称打开容器详情页面。
|
||||
. On the right side of the pod details page, click the **Resource Status** tab, and in the **Containers** section, click the name of a container to open the container details page.
|
||||
|
||||
. 在容器详情页面左侧的**属性**区域查看容器的资源属性。
|
||||
. On the left side of the container details page, in the **Attributes** section, view the container's resource attributes.
|
||||
+
|
||||
--
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|集群
|
||||
|容器所属的集群。
|
||||
|Cluster
|
||||
|The cluster to which the container belongs.
|
||||
|
||||
|项目
|
||||
|容器所属的项目。
|
||||
|Project
|
||||
|The project to which the container belongs.
|
||||
|
||||
|应用
|
||||
|容器所属的应用。
|
||||
|Application
|
||||
|The application to which the container belongs.
|
||||
|
||||
|状态
|
||||
|容器的状态。
|
||||
|Status
|
||||
|The status of the container.
|
||||
|
||||
include::../workloads/workloads-para-containerStatus.adoc[]
|
||||
|
||||
|镜像
|
||||
|容器使用的镜像。
|
||||
|Image
|
||||
|The image used by the container.
|
||||
|
||||
|镜像 ID
|
||||
|容器使用的镜像的 ID。
|
||||
|Image ID
|
||||
|The ID of the image used by the container.
|
||||
|
||||
|端口
|
||||
|容器的端口。
|
||||
|Ports
|
||||
|The ports of the container.
|
||||
|
||||
|命令
|
||||
|容器启动时在容器内部执行的命令。
|
||||
|Command
|
||||
|The command executed within the container at startup.
|
||||
|
||||
|资源预留
|
||||
|系统为容器预留的 CPU 和内存资源。
|
||||
|Resource Requests
|
||||
|CPU and memory resources reserved by the system for the container.
|
||||
|
||||
|资源上限
|
||||
|容器可以使用的 CPU 和内存资源上限。
|
||||
|Resource Limits
|
||||
|The upper limits of CPU and memory resources that the container can use.
|
||||
|
||||
|镜像拉取策略
|
||||
|容器的镜像拉取策略。
|
||||
|Image Pull Policy
|
||||
|The image pull policy for the container.
|
||||
|
||||
* **优先使用本地镜像**：容器组创建或更新时，优先使用容器运行时存储在节点的镜像文件。
|
||||
* **Use Local Image First**: When creating or updating a pod, prioritize using the images stored by the container runtime on the node.
|
||||
|
||||
* **每次都拉取镜像**：容器组创建或更新时，每次都尝试从镜像服务拉取镜像。
|
||||
* **Pull Image Always**: When creating or updating a pod, pull the image from the image registry every time.
|
||||
|
||||
* **仅使用本地镜像**：容器组创建或更新时，仅使用容器运行时存储在节点的镜像。如果本地不存在所需的镜像，容器创建将出现异常。
|
||||
* **Use Local Image Only**: When creating or updating a pod, only use the images stored by the container runtime on the node. If the required image is not available locally, the pod may be created with an exception.
|
||||
|
||||
|重启次数
|
||||
|容器的重启次数。
|
||||
|Restarts
|
||||
|The restart times of the container.
|
||||
|===
|
||||
--
|
||||
|
||||
. 在容器详情页面右侧的**资源状态**页签查看容器中挂载卷、卷的挂载路径和访问模式。
|
||||
. On the right side of the container details page, click the **Resource Status** tab to view mounted volumes, the mount paths of volumes, and their access modes.
|
||||
|
||||
. 在容器详情页面右侧的**环境变量**页签查看容器的环境变量。
|
||||
|
||||
// . 在容器详情页面右侧点击**容器日志**页签查看容器的标准输出日志。
|
||||
// +
|
||||
// --
|
||||
// * 在右上角点击image:/images/ks-qkcp/zh/icons/start-dark.svg[start-dark,18,18]/image:/images/ks-qkcp/zh/icons/stop-dark-white.svg[stop-dark-white,18,18]可开启/停止实时数据刷新。
|
||||
|
||||
// * 在右上角点击image:/images/ks-qkcp/zh/icons/refresh-dark-white.svg[refresh-dark-white,18,18]可手动刷新数据。
|
||||
|
||||
// * 在右上角点击image:/images/ks-qkcp/zh/icons/download-dark-white.svg[download-dark-white,18,18]可下载日志文件。
|
||||
// --
|
||||
. On the right side of the container details page, click the **Environment Variables** tab to view the environment variables of the container.
|
||||
|
|
@ -1,98 +1,98 @@
|
|||
// :ks_include_id: cb41056b42b540b999804717abfd497a
|
||||
. 在容器组详情页面左侧的**属性**区域查看容器组的资源属性。
|
||||
. View the resource attributes of the pod in the **Attributes** section on the left side of the pod details page.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|集群
|
||||
|容器组所属的集群。
|
||||
|Cluster
|
||||
|The cluster to which the pod belongs.
|
||||
|
||||
|项目
|
||||
|容器组所属的项目。
|
||||
|Project
|
||||
|The project to which the pod belongs.
|
||||
|
||||
|应用
|
||||
|容器组所属的应用。
|
||||
|Application
|
||||
|The application to which the pod belongs.
|
||||
|
||||
|状态
|
||||
|容器组的状态。
|
||||
|Status
|
||||
|The status of the pod.
|
||||
|
||||
include::pods-para-podStatus.adoc[]
|
||||
|
||||
include::pods-para-podIpPool.adoc[]
|
||||
|
||||
|节点名称
|
||||
|容器组所在节点的名称。
|
||||
|Node Name
|
||||
|The name of the node where the pod is located.
|
||||
|
||||
|节点 IP 地址
|
||||
|容器组所在节点的 IP 地址。
|
||||
|Node IP Address
|
||||
|The IP address of the node where the pod is located.
|
||||
|
||||
|重启次数
|
||||
|容器组的重启次数。
|
||||
|Restarts
|
||||
|The number of times the pod has been restarted.
|
||||
|
||||
|QoS 类型
|
||||
|容器组的服务质量类型（Quality of Service），由用户设置的容器内存上限、内存请求、CPU 上限和 CPU 请求决定。
|
||||
|QoS Type
|
||||
|The Quality of Service (QoS) type of the pod, determined by user-defined memory limits, memory requests, CPU limits, and CPU requests.
|
||||
|
||||
include::pods-para-qosTypes.adoc[]
|
||||
|
||||
|创建时间
|
||||
|容器组的创建时间。
|
||||
|Creation Time
|
||||
|The creation time of the pod.
|
||||
|
||||
|创建者
|
||||
|容器组的创建者。
|
||||
|Creator
|
||||
|The creator of the pod.
|
||||
|===
|
||||
--
|
||||
|
||||
. 在容器组详情页面右侧的**资源状态**页签查看容器组中的容器和卷。
|
||||
. On the right side of the pod details page, click the **Resource Status** tab to view the containers and volumes in the pod.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|容器
|
||||
|显示容器组运行的容器的名称、状态、重启次数和容器端口。容器状态类型包括：
|
||||
|Containers
|
||||
|Displays the names, status, restarts, and container ports of the containers running in the pod. Container statuses include:
|
||||
|
||||
include::../workloads/workloads-para-containerStatus.adoc[]
|
||||
|
||||
在容器名称右侧点击image:/images/ks-qkcp/zh/icons/log.svg[log,18,18]可查看容器日志。将光标悬停在**探针**可查看容器上配置的探针。
|
||||
Click image:/images/ks-qkcp/zh/icons/log.svg[log,18,18] next to the container name to view the container logs. Hover over **Probes** to view the configured probes in the container.
|
||||
|
||||
|卷
|
||||
|显示容器组中所有卷的名称、已挂载卷的容器以及卷在容器上的挂载路径。
|
||||
|Volumes
|
||||
|Displays the names of all volumes for the pod, the containers to which volumes are mounted, and the mount paths of volumes on containers.
|
||||
|===
|
||||
--
|
||||
|
||||
. 在容器组详情页面右侧点击**调度信息**页签查看容器组的调度结果和状态信息。
|
||||
. On the right side of the pod details page, click the **Scheduling Information** tab to view the scheduling results and status information of the pod.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|调度结果
|
||||
|显示接收容器组的节点的名称。
|
||||
|Scheduling Result
|
||||
|Displays the name of node that accepted the pod.
|
||||
|
||||
|状态信息
|
||||
|显示容器组是否成功完成所有启动步骤。如果显示image:/images/ks-qkcp/zh/icons/success.svg[success,18,18]则表明容器组已完成启动步骤，如果显示image:/images/ks-qkcp/zh/icons/error.svg[error,18,18]则表明尚未完成启动步骤。
|
||||
|Status Information
|
||||
|Shows whether the pod has successfully completed all startup steps. If image:/images/ks-qkcp/zh/icons/success.svg[success,18,18] is displayed, the pod has completed the startup steps; if image:/images/ks-qkcp/zh/icons/error.svg[error,18,18] is displayed, the startup steps are not yet completed.
|
||||
|
||||
* **运行中**：容器组当前的状态是否为**运行中**。
|
||||
* **Running**: Whether the pod is in the **Running** state.
|
||||
|
||||
* **容器组调度完成**：容器组是否已调度到节点。
|
||||
* **Pod Scheduled**: Whether the pod has been scheduled to a node.
|
||||
|
||||
* **容器组初始化完成**：容器组中的所有初始化容器是否已启动完成。
|
||||
* **Initialized**: Whether all init containers in the pod have started.
|
||||
|
||||
* **所有容器就绪**：容器组中的所有容器是否已启动完成。
|
||||
* **Containers Ready**: Whether all containers in the pod have started.
|
||||
|
||||
* **容器组就绪**：容器组是否已就绪。
|
||||
* **Pod Ready**: Whether the pod is ready.
|
||||
|===
|
||||
--
|
||||
|
||||
. 在容器组详情页面右侧点击**元数据**页签查看容器组的标签和注解。
|
||||
. On the right side of the pod details page, click the **Metadata** tab to view the labels and annotations of the pod.
|
||||
|
||||
. 在容器组详情页面右侧点击**环境变量**页签查看容器组中的所有容器的环境变量。
|
||||
. On the right side of the pod details page, click the **Environment Variables** tab to view the environment variables of all containers in the pod.
|
||||
|
||||
. 在容器组详情页面右侧点击**事件**页签查看容器组相关的事件。
|
||||
. On the right side of the pod details page, click the **Events** tab to view events related to the pod.
|
||||
+
|
||||
--
|
||||
include::../clusterManagement-para-eventsTab.adoc[]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: 279e5268acd74e4bb37c530cc08cc373
|
||||
|容器组 IP 地址
|
||||
|容器组在集群内部的虚拟 IP 地址。
|
||||
| Pod IP Address
|
||||
| The virtual IP address of the pod within the cluster.
|
||||
|
|
@ -1,28 +1,28 @@
|
|||
// :ks_include_id: 9b12ede280884331985685925cf5dfc4
|
||||
* 容器组列表提供以下信息：
|
||||
* The pod list provides the following information:
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|名称
|
||||
|容器组的名称。
|
||||
| Name
|
||||
| The name of the pod.
|
||||
|
||||
|状态
|
||||
|容器组的状态。
|
||||
| Status
|
||||
| The status of the pod.
|
||||
|
||||
include::pods-para-podStatus.adoc[]
|
||||
|
||||
|节点
|
||||
|容器组所在的节点和节点的 IP 地址。
|
||||
| Node
|
||||
| The node where the pod is located and the IP address of the node.
|
||||
|
||||
include::pods-para-podIpPool.adoc[]
|
||||
|
||||
|应用
|
||||
|容器组所属的应用。
|
||||
| Application
|
||||
| The application to which the pod belongs.
|
||||
|
||||
|更新时间
|
||||
|容器组的更新时间。
|
||||
| Update Time
|
||||
| The update time of the pod.
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,11 +1,10 @@
|
|||
// :ks_include_id: 8cc83a9c58b8460cbcf369b1a07288b1
|
||||
* **Running**: The pod has been assigned to a node, all containers in the pod have been created, and at least one container is running, starting, or restarting.
|
||||
|
||||
* **运行中**：容器组已分配给某个节点，容器组中的所有容器都已被创建，至少有一个容器正在运行、启动或重启。
|
||||
* **Waiting**: The pod has been accepted by the system, but at least one container has not been created or is not running. In this state, the pod may be waiting for scheduling or waiting for the container image to finish downloading.
|
||||
|
||||
* **等待中**：容组器已被系统接受，但有至少一个容器尚未创建也未运行。此状态下，容器组可能正在等待调度，或等待容器镜像下载完成。
|
||||
* **Completed**: All containers in the pod have successfully terminated (terminated with an exit code of 0), and no longer restart.
|
||||
|
||||
* **已完成**：容器组中的所有容器都成功终止（以 0 退出码终止），并且不再重启。
|
||||
* **Failed**: All containers in the pod have terminated, and at least one container terminated with a non-zero exit code.
|
||||
|
||||
* **失败**：容器组中的所有容器都已终止，并且至少有一个容器以非 0 退出码终止。
|
||||
|
||||
* **未知**：系统无法获取容器组状态。出现这种状态通常是由于系统与容器组所在的主机通信失败。
|
||||
* **Unknown**: The system cannot retrieve the pod's status, which usually occurs when communication fails between the system and the host where the pod is located.
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
// :ks_include_id: 6dc8492ff19d4f1bb83db24a36e18f07
|
||||
* **Guaranteed**：容器组中的每个容器都具有内存上限、内存请求、CPU 上限、CPU 请求，并且内存上限等于内存请求，CPU 上限等于 CPU 请求。
|
||||
* **Guaranteed**: Each container in the pod has memory limits, memory requests, CPU limits, and CPU requests, and the memory limit is equal to the memory request, and the CPU limit is equal to the CPU request.
|
||||
|
||||
* **Burstable**：容器组中至少有一个容器不满足 **Guaranteed** 类型的要求。
|
||||
* **Burstable**: At least one container in the pod does not meet the requirements of the **Guaranteed** type.
|
||||
|
||||
* **BestEffort**：容器组中的容器没有配置任何内存上限、内存请求、CPU 上限或CPU 请求。
|
||||
* **BestEffort**: Containers in the pod do not configured with any memory limits, memory requests, CPU limits, or CPU requests.
|
||||
|
||||
容器组的 QoS 类型将决定容器组运行的优先级。当系统中资源不足以运行所有容器组时，系统优先保证运行 QoS 类型为 **Guaranteed** 的容器组，其次保证运行 QoS 类型为 **Burstable** 的容器组，最后保证运行 QoS 类型为 **BestEffort** 的容器组。
|
||||
The QoS type of the pod determines the running priority of the pod. When resources in the system is insufficient to run all pods, the system gives priority to running pods of QoS type **Guaranteed** first, followed by pods of QoS type **Burstable**, and finally, pods of QoS type **BestEffort**.
|
||||
|
|
@ -1,9 +1,10 @@
|
|||
// :ks_include_id: 375914907c6948b08ccff616aa99831d
|
||||
本节介绍如何删除项目。
|
||||
This section explains how to delete projects.
|
||||
|
||||
// Warning
|
||||
include::../../../../_ks_components-en/admonitions/warning.adoc[]
|
||||
//warning
|
||||
[.admon.warning,cols="a"]
|
||||
|===
|
||||
|Warning
|
||||
|
||||
项目删除后不能恢复，同时项目中的所有的资源也将被删除，请谨慎执行此操作。
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|Once a project is deleted, it cannot be recovered, and all resources within the project will be deleted. Please proceed with caution.
|
||||
|===
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
// :ks_include_id: 61bf4ea84b3d4363b5a4ebfacd921138
|
||||
本节介绍如何编辑默认容器配额。
|
||||
This section explains how to edit default container quotas.
|
||||
|
||||
默认容器配额是项目中容器的资源预留和资源上限的默认值。在项目中创建容器时，如果用户未指定资源预留和资源限制，{ks_product-en}系统将自动使用默认容器配额。
|
||||
Default container quotas are the default values for resource request and resource limit for containers in the project. When creating containers in the project, if users do not specify resource request and limit, the containers will automatically use the default container quotas.
|
||||
|
||||
默认容器配额包括两类设置：
|
||||
Default container quotas include two types of settings:
|
||||
|
||||
* 资源预留：系统为容器预留的资源。
|
||||
* Resource Request: Resources reserved by the system for containers.
|
||||
|
||||
* 资源上限：容器可使用的资源上限。
|
||||
* Resource Limit: The upper limit of resources that containers can use.
|
||||
|
|
@ -1,12 +1,12 @@
|
|||
// :ks_include_id: c47c51f776564c1bba3cf7decf79a67d
|
||||
本节介绍如何编辑项目配额。
|
||||
This section explains how to edit project quotas.
|
||||
|
||||
项目配额包括以下设置：
|
||||
Project quotas include the following settings:
|
||||
|
||||
* 资源预留：容器的资源预留是系统为单个容器预留的资源，项目资源预留是项目中所有容器资源预留总和的最大值。{ks_product-en}平台目前支持为项目设置 CPU 预留和内存预留。
|
||||
* Resource Request: Container resource request is the system's reserved resources for a single container, and project resource request is the maximum value of the sum of all container resource requests in the project. KubeSphere currently supports setting CPU request and memory request for the project.
|
||||
|
||||
* 资源上限：容器的资源上限是单个容器可使用资源的上限，项目资源上限是项目中所有容器资源上限总和的最大值。{ks_product-en}平台目前支持为项目设置 CPU 上限、内存上限和 GPU 上限。
|
||||
* Resource Limit: Container resource limit is the upper limit of resources that a single container can use, and project resource limit is the maximum value of the sum of all container resource limits in the project. KubeSphere currently supports setting CPU limit, memory limit, and GPU limit for the project.
|
||||
|
||||
* 存储资源配额：可以对命名空间下的存储资源总量进行限制，包括存储资源总量和存储类关联资源。
|
||||
* Storage Resource Quota: Limitations on the total amount of storage resources in the project, including the total amount of storage resources and associated resources with storage classes.
|
||||
|
||||
* 应用资源配额：项目中可创建的容器组、部署、有状态副本集、守护进程集、任务、定时任务、持久卷声明、服务、应用路由、保密字典、配置字典的数量上限。
|
||||
* Application Resource Quota: Upper limits on the quantity of Pods, Deployments, StatefulSets, DaemonSets, Jobs, CronJobs, Persistent Volume Claims, Services, Ingresses, Secrets, and ConfigMaps that can be created in the project.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: 6f57a346768f432a9a776a26c0ab55b4
|
||||
. 在需要删除的项目右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**删除**。
|
||||
. On the right side of the project you want to delete, click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18], and then select **Delete** from the drop-down list.
|
||||
|
||||
. 在**删除项目**对话框，输入项目的名称，然后点击**确定**。
|
||||
. In the **Delete Project** dialog, enter the name of the project, then click **OK**.
|
||||
|
|
@ -1,7 +1,7 @@
|
|||
// :ks_include_id: c31e22ed93ad4f3fa0500c5bb67c80e3
|
||||
. 选择需要删除的项目左侧的复选框，然后在项目列表上方点击**删除**。
|
||||
. Select the checkbox on the left of the projects you want to delete, then click **Delete** above the project list.
|
||||
|
||||
. 在**批量删除项目**对话框，输入项目的名称，然后点击**确定**。
|
||||
. In the **Delete Multiple Projects** dialog, enter the name of the projects, then click **OK**.
|
||||
+
|
||||
--
|
||||
include::../../note-separateNamesByComma.adoc[]
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
// :ks_include_id: eae1dea548f94792b303903d436d1b25
|
||||
. 在**编辑默认容器配额**对话框，设置容器的默认资源预留和资源上限，然后点击**确定**。
|
||||
. In the **Edit Default Container Quotas** dialog, set the default resource request and resource limit for containers, then click **OK**.
|
||||
+
|
||||
--
|
||||
[options="header",cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
include::projects-para-containerQuotas.adoc[]
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,38 +1,36 @@
|
|||
// :ks_include_id: 5e0c07e44f1440999412a1ec7581f173
|
||||
. 在**编辑项目配额**对话框，设置项目资源预留和资源上限。
|
||||
. In the **Edit Project Quotas** dialog, set the project resource request and resource limit.
|
||||
+
|
||||
--
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|CPU 预留
|
||||
|项目中所有容器 CPU 预留总和的最大值，单位为核。
|
||||
|CPU Request
|
||||
|The maximum value of the sum of all container CPU requests in the project, measured in cores.
|
||||
|
||||
|CPU 上限
|
||||
|项目中所有容器 CPU 上限总和的最大值，单位为核。
|
||||
|CPU Limit
|
||||
|The maximum value of the sum of all container CPU limits in the project, measured in cores.
|
||||
|
||||
|内存预留
|
||||
|项目中所有容器内存预留总和的最大值，单位为 GiB。
|
||||
|Memory Request
|
||||
|The maximum value of the sum of all container memory requests in the project, measured in GiB.
|
||||
|
||||
|内存上限
|
||||
|项目中所有容器内存上限总和的最大值，单位为 GiB。
|
||||
|Memory Limit
|
||||
|The maximum value of the sum of all container memory limits in the project, measured in GiB.
|
||||
|
||||
|GPU 类型
|
||||
|项目中容器所能使用的 GPU 类型。目前仅支持设置 NVIDIA GPU。
|
||||
|GPU Type
|
||||
|The GPU type that containers in the project can use. Currently, only NVIDIA GPU is supported.
|
||||
|
||||
|GPU 上限
|
||||
|项目中所有容器可以使用的 GPU 数量上限，单位为 GPU。
|
||||
|GPU Limit
|
||||
|The maximum number of GPUs that all containers in the project can use, measured in GPUs.
|
||||
|===
|
||||
--
|
||||
|
||||
. 在**编辑项目配额**对话框的**存储资源配额**区域，设置存储资源总量和存储类关联资源。
|
||||
. In the **Storage Resource Quota** section of the **Edit Project Quotas** dialog, set the total storage resource quota and associated resource quota with storage classes.
|
||||
|
||||
. 在**编辑项目配额**对话框的**应用资源配额**区域，设置项目的应用资源数量上限，然后点击**确定**。
|
||||
. In the **Application Resource Quotas** section of the **Edit Project Quotas** dialog, set the upper limits on the quantity of application resources in the project, then click **OK**.
|
||||
+
|
||||
--
|
||||
* 您可以设置项目中容器组、部署、有状态副本集、守护进程集、任务、定时任务、持久卷声明、服务、应用路由、保密字典和配置字典的数量上限。
|
||||
* You can set upper limits on the quantity of Pods, Deployments, StatefulSets, DaemonSets, Jobs, CronJobs, Persistent Volume Claims, Services, Ingresses, Secrets, and ConfigMaps in the project.
|
||||
|
||||
* 点击**添加**可以设置多种应用资源的数量上限。
|
||||
--
|
||||
* Click **Add** to set upper limits on the quantity of more application resources.
|
||||
--
|
||||
|
|
@ -1,18 +1,18 @@
|
|||
// :ks_include_id: ed53650f20d543ee95f0aa14ff7b5f1e
|
||||
|CPU 预留
|
||||
|为容器预留的 CPU 资源，单位为核。
|
||||
|CPU Request
|
||||
|Reserved CPU resources for a container, measured in cores.
|
||||
|
||||
|CPU 上限
|
||||
|允许容器使用的 CPU 资源上限，单位为核。
|
||||
|CPU Limit
|
||||
|Upper limit of CPU resources that a container is allowed to use, measured in cores.
|
||||
|
||||
|内存预留
|
||||
|为容器预留的内存资源，单位为 MiB。
|
||||
|Memory Request
|
||||
|Reserved memory resources for a container, measured in MiB.
|
||||
|
||||
|内存上限
|
||||
|允许容器使用的内存资源上限，单位为 MiB。
|
||||
|Memory Limit
|
||||
|Upper limit of memory resources that a container is allowed to use, measured in MiB.
|
||||
|
||||
|GPU 类型
|
||||
|对容器上限使用量的 GPU 类型。目前仅支持设置 NVDIA GPU。
|
||||
|GPU Type
|
||||
|The GPU type that containers in the project can use. Currently, only NVIDIA GPU is supported.
|
||||
|
||||
|GPU 上限
|
||||
|允许容器使用的 GPU 数量上限，单位为 GPU。
|
||||
|GPU Limit
|
||||
|Upper limit on the number of GPUs that a container is allowed to use, measured in GPUs.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 778abc4b808a4ed796f46c0c8b12c68d
|
||||
本节介绍如何创建服务。
|
||||
This section explains how to create services.
|
||||
|
|
|
|||
|
|
@ -1,9 +1,11 @@
|
|||
// :ks_include_id: 5e2c112952a04a0a852f249edae6a04d
|
||||
本节介绍如何删除服务。
|
||||
This section explains how to delete a service.
|
||||
|
||||
// Warning
|
||||
include::../../../../_ks_components-en/admonitions/warning.adoc[]
|
||||
//warning
|
||||
[.admon.warning,cols="a"]
|
||||
|===
|
||||
| Warning
|
||||
|
||||
删除服务后将无法通过服务访问其后端的容器组，请谨慎执行此操作。
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
||||
Deleting a service will make it impossible to access the pods behind it through the service. Please proceed with caution.
|
||||
|===
|
||||
|
|
@ -1,9 +1,11 @@
|
|||
// :ks_include_id: 6153ebc95ef847adb6e6294e7b521d88
|
||||
本节介绍如何编辑服务外部访问设置。
|
||||
This section explains how to edit external access settings for services.
|
||||
|
||||
// Note
|
||||
include::../../../../_ks_components-en/admonitions/note.adoc[]
|
||||
//note
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
| Note
|
||||
|
||||
此操作仅支持内部访问模式为 VirtualIP 的服务，不支持内部访问模式为 Headless 或 ExternalName 的服务。
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
||||
This operation is only available for services with an internal access mode of VirtualIP, not available for services with internal access modes of Headless or ExternalName.
|
||||
|===
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: 0be7fc7e00d24083ac5d17ec7c4dd81b
|
||||
本节介绍如何编辑任务信息。
|
||||
This section explains how to edit service information.
|
||||
|
||||
您可以编辑任务的别名和描述。{ks_product-en}不支持编辑已创建任务的名称。
|
||||
You can edit the alias and description of the service. KubeSphere does not support editing the name of an already created service.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 0c171d40a4db48718db0c8fd91e031a8
|
||||
本节介绍如何编辑任务设置。
|
||||
This section explains how to edit service settings.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
// :ks_include_id: 9d67f68a071549aa94a7433420ef1f66
|
||||
本节介绍如何管理服务。
|
||||
This section explains how to manage services.
|
||||
|
||||
服务用于暴露应用程序供集群内部或集群外部访问。
|
||||
Services are used to expose applications for access either within or outside the cluster.
|
||||
|
||||
* 在{ks_product-en}平台上，应用程序运行在容器组中，同一个应用程序的多个容器组副本由工作负载或任务管理。虽然每个容器组都具有可在集群内部访问的虚拟 IP 地址，但容器组是非永久性的资源，可能会被删除或重新创建。当容器组被重新创建时，新容器组和旧容器组的虚拟 IP 地址一般不同，容器组原有的 IP 地址将失效。
|
||||
* In KubeSphere, applications run in pods, and multiple pod replicas of the same application are managed by workloads or jobs. While each pod has a virtual IP address accessible within the cluster, pods are non-permanent resources that may be deleted or recreated. When a pod is recreated, the new pod's virtual IP address is generally different from the old one, and the old pod's IP address becomes invalid.
|
||||
|
||||
* 服务提供了固定的地址（域名或 IP 地址）供客户端访问。服务将客户端的请求转发给某一个容器组，并为多个容器组副本提供负载均衡，从而解决了容器组被删除或重新创建时原有地址失效的问题。
|
||||
* Services provide a stable address (domain or IP address) for client access. Services route client requests to a specific pod and offer load balancing across multiple pod replicas, so as to solve the issue of the original address becoming invalid when a pod is deleted or recreated.
|
||||
|
||||
* 除为工作负载提供固定的访问地址外，服务还可以通过 NodePort 或 LoadBalancer 方式将工作负载暴露到集群外部。
|
||||
* In addition to providing a stable access address for workloads, services can expose workloads outside the cluster through NodePort or LoadBalancer methods.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 312a369c91ea4bc58e98f2d1989311cd
|
||||
本节介绍如何查看服务详情。
|
||||
This section explains how to view the service details.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: ef7bee4f35a44bbd891d4d160abdda30
|
||||
本节介绍如何查看服务列表。
|
||||
This section explains how to view the service list.
|
||||
|
|
|
|||
|
|
@ -1,28 +1,28 @@
|
|||
// :ks_include_id: 95f4759b32eb4061ae07cea32fd54ac8
|
||||
. 在**服务设置**页签，设置服务的内部访问模式、工作负载选择器和端口，然后点击**下一步**。
|
||||
. On the **Service Settings** tab, configure the service's internal access mode, workload selector, and ports, then click **Next**.
|
||||
+
|
||||
--
|
||||
include::services-para-serviceSettings.adoc[]
|
||||
--
|
||||
|
||||
. 在**高级设置**页签，设置服务的外部访问模式、会话保持设置和元数据，然后点击**创建**。
|
||||
. On the **Advanced Settings** tab, configure the service's external access mode, session persistence settings, and metadata, then click **Create**.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
include::services-para-externalAccess.adoc[]
|
||||
|
||||
include::services-para-sessionPersistence.adoc[]
|
||||
|
||||
|添加元数据
|
||||
|设置服务的标签。
|
||||
| Add Metadata
|
||||
| Set labels for the service.
|
||||
|
||||
* 点击**添加**可设置多条标签。
|
||||
* Click **Add** to set multiple labels.
|
||||
|
||||
* 在已创建的标签右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除标签。
|
||||
* Click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right side of a created label to delete it.
|
||||
|===
|
||||
|
||||
服务创建完成后将显示在服务列表中。
|
||||
--
|
||||
Services will be displayed in the service list after creation.
|
||||
--
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 03191d86a7474f0aa61513f52a671795
|
||||
. 在需要删除的服务右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**删除**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right of the service you want to delete, then choose **Delete** from the dropdown list.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
// :ks_include_id: 0497433d316e4c6e9a45cf29e12dbbd9
|
||||
. 选择需要删除的服务左侧的复选框，然后在服务列表上方点击**删除**。
|
||||
. Select the checkbox on the left side of the services you want to delete, then click **Delete** above the service list.
|
||||
|
||||
. 在**批量删除服务**对话框，确认并选择要删除的相关资源，然后点击**确定**。
|
||||
. In the **Delete Multiple Services** dialog, confirm and select the names of the resources related to the services to be deleted, then click **OK**.
|
||||
+
|
||||
--
|
||||
include::../../note-separateNamesByComma.adoc[]
|
||||
|
|
|
|||
|
|
@ -1,20 +1,18 @@
|
|||
// :ks_include_id: f59275b4c21c49c9983d211ee4b12b66
|
||||
. 在**编辑外部访问**对话框，设置服务的外部访问模式，然后点击**确定**。
|
||||
. In the **Edit External Access** dialog, set the external access mode for the service, then click **OK**.
|
||||
+
|
||||
--
|
||||
服务的外部访问模式包括以下类型：
|
||||
The external access modes for the service include the following types:
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|无
|
||||
|无法从集群外部访问服务。
|
||||
| None
|
||||
| The service cannot be accessed from outside the cluster.
|
||||
|
||||
|NodePort
|
||||
|系统将节点的端口映射到服务端口，可通过节点的 IP 地址和节点端口访问服务。
|
||||
* **NodePort**: The system maps the ports of nodes to the service ports, and the service can be accessed through the node IP address and node port.
|
||||
|
||||
|LoadBalancer
|
||||
|系统在 NodePort 服务的基础上为服务分配一个外部 IP 地址，并将外部 IP 地址与一个外部负载均衡器绑定。外部负载均衡器监听服务对应的节点端口，从而可以通过外部 IP 地址访问服务。为实现上述功能，LoadBalancer 类型的服务需要负载均衡器插件和基础设施环境提供支持，并且需要设置相关注解。有关更多信息，请联系您的基础设施环境提供商。
|
||||
* **LoadBalancer**: On the basis of a NodePort service, the system assigns an external IP address to the service and binds the external IP address to an external load balancer. The external load balancer listens on the node port corresponding to the service, allowing access to the service through the external IP address. To achieve this, LoadBalancer-type services need support from load balancer plugins and the infrastructure environment, and relevant annotations need to be set. For more information, please contact your infrastructure environment provider.
|
||||
|===
|
||||
--
|
||||
|
|
|
|||
|
|
@ -1,17 +1,17 @@
|
|||
// :ks_include_id: 1137d62e09344a798e172ba55bf7a205
|
||||
. 在需要操作的服务右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**编辑信息**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right of the service you want to edit, then choose **Edit Information** from the dropdown list.
|
||||
|
||||
. 在**编辑信息**对话框，设置服务的别名和描述，然后点击**确定**。
|
||||
. In the **Edit Information** dialog, set the alias and description for the service, then click **OK**.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|别名
|
||||
|服务的别名。不同服务的别名可以相同。别名只能包含中文、字母、数字和连字符（-），不得以连字符（-）开头或结尾，最长 63 个字符。
|
||||
| Alias
|
||||
| The alias of the service. Aliases can be the same for different services. An alias can only contain Chinese characters, letters, numbers, and hyphens (-). It cannot start or end with a hyphen (-) and has a maximum length of 63 characters.
|
||||
|
||||
|描述
|
||||
|服务的描述信息。描述可包含任意字符，最多包含 256 个字符。
|
||||
| Description
|
||||
| The description for the service. The description can contain any characters, with a maximum length of 256 characters.
|
||||
|===
|
||||
--
|
||||
|
|
@ -1,11 +1,11 @@
|
|||
// :ks_include_id: f0f32c026c8a44b7ac18acbadf465ea5
|
||||
. 在需要操作的服务右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**编辑服务**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right of the service you want to edit, then choose **Edit Service** from the dropdown list.
|
||||
|
||||
. 在**编辑服务**对话框修改服务的设置，然后点击**确定**。
|
||||
. In the **Edit Service** dialog, modify the service settings, then click **OK**.
|
||||
|
||||
* 对于内部访问模式为 ExternalName 的服务，您可以修改外部服务的地址。
|
||||
* For services with an internal access mode of ExternalName, you can modify the address of the external service.
|
||||
|
||||
* 对于其他服务，您可以修改服务的内部访问模式、工作负载选择器和端口。
|
||||
* For other services, you can modify the internal access mode, workload selector, and ports of the service.
|
||||
+
|
||||
--
|
||||
include::services-para-serviceSettings.adoc[]
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 9572433de70c4e3485289ea683e39c12
|
||||
. 在服务列表中点击一个服务的名称打开其详情页面。
|
||||
. Click the name of a service in the service list to open its details page.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: d085604adc244a4cbb580fb88485f275
|
||||
* 在列表上方点击搜索框并设置搜索条件，可按名称搜索服务。
|
||||
* Click the search box at the top of the list and search for services by name.
|
||||
|
|
|
|||
|
|
@ -1,19 +1,19 @@
|
|||
// :ks_include_id: ec83e4ff0eb74cdaa02d3a52062d9bc5
|
||||
. 在服务详情页面左侧的**属性**区域查看服务的资源属性。
|
||||
. In the **Attributes** section on the left side of the service details page, view the resource attributes of the service.
|
||||
+
|
||||
--
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|集群
|
||||
|服务所属的集群。
|
||||
| Cluster
|
||||
| The cluster to which the service belongs.
|
||||
|
||||
|项目
|
||||
|服务所属的项目。
|
||||
| Project
|
||||
| The project to which the service belongs.
|
||||
|
||||
|类型
|
||||
| Type
|
||||
|
|
||||
include::services-para-internalAccess.adoc[]
|
||||
|
||||
|
|
@ -21,70 +21,67 @@ include::services-para-virtualip-headless.adoc[]
|
|||
|
||||
include::services-para-externalName.adoc[]
|
||||
|
||||
|应用
|
||||
|服务所属的应用名称。您可以创建一个包含多个服务的应用，每个服务都对应一个工作负载。
|
||||
| App
|
||||
| The name of the application to which the service belongs. You can create an application that includes multiple services, with each service corresponding to a workload.
|
||||
|
||||
|虚拟 IP 地址
|
||||
|服务供集群内部访问的虚拟 IP 地址，仅对 VirtualIP 类型的服务显示。
|
||||
| Virtual IP Address
|
||||
| The virtual IP address for internal access within the cluster. Displayed only for services with the VirtualIP type.
|
||||
|
||||
|外部 IP 地址
|
||||
|服务供集群外部访问的 IP 地址，仅在服务启用外部访问时显示。
|
||||
| External IP Address
|
||||
| The IP address for external access outside the cluster. Displayed only when external access is enabled for the service.
|
||||
|
||||
|会话保持
|
||||
|是否已启用会话保持功能，取值可以为：
|
||||
| Session Affinity
|
||||
| Whether session affinity is enabled:
|
||||
|
||||
* **已启用**：已启用会话保持。如果服务有多个容器组，在一定时间内（默认值为 10800 秒），来自相同客户端 IP 地址的请求将被转发给同一个容器组。
|
||||
* **Enabled**: Session affinity is enabled. If the service has multiple pods, requests from the same client IP address within a certain period (default is 10800 seconds) will be forwarded to the same pod.
|
||||
|
||||
* **未启用**：未启用会话保持。如果服务有多个容器组，来自相同客户端 IP 地址的请求将被随机转发给不同的容器组。
|
||||
* **Disabled**: Session affinity is not enabled. If the service has multiple pods, requests from the same client IP address will be randomly forwarded to different pods.
|
||||
|
||||
|选择器
|
||||
|服务的容器组选择器。容器组选择器由一个多个容器组标签组成，服务会将客户端请求转发给具有全部指定标签的容器组。
|
||||
| Selector
|
||||
| The selector for the service's pods. The pod selector consists of one or more pod labels, and the service will route client requests to pods that have all the specified labels.
|
||||
|
||||
|DNS
|
||||
|服务在集群内部的域名，可在集群内部访问。
|
||||
| DNS
|
||||
| The internal domain of the service within the cluster, accessible within the cluster.
|
||||
|
||||
|端点
|
||||
|服务的目标容器组的虚拟 IP 地址和容器端口。
|
||||
| Endpoint
|
||||
| The virtual IP address and container port of the target pods for the service.
|
||||
|
||||
|创建时间
|
||||
|服务的创建时间。
|
||||
| Creation Time
|
||||
| The creation time of the service.
|
||||
|
||||
// |更新时间
|
||||
// |服务的最后更新时间。
|
||||
|
||||
|创建者
|
||||
|创建服务的用户。
|
||||
| Creator
|
||||
| The user who created the service.
|
||||
|===
|
||||
--
|
||||
|
||||
. 在服务详情页面右侧的**资源状态**页签查看服务的容器端口、工作负载和容器组。
|
||||
. In the **Resource Status** tab on the right side of the service details page, view the container ports, workloads, and pods for the service.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|端口
|
||||
|为使容器能够被正常访问，{ks_product-en}平台上定义了以下端口类型：
|
||||
| Ports
|
||||
| To enable containers to be accessed properly, KubeSphere Enterprise defines the following types of ports:
|
||||
|
||||
* 容器端口：容器中的应用程序监听的端口，只能在容器组内部访问。
|
||||
* Container Port: The port on which the application in the container listens, only accessible within the pod.
|
||||
|
||||
* 服务端口：服务虚拟 IP 地址的端口，只能在集群内部访问，发送到服务端口的请求将被转发给容器端口。
|
||||
* Service Port: The port for the virtual IP address of the service, only accessible within the cluster. Requests sent to the service port will be forwarded to the container port.
|
||||
|
||||
* 节点端口：节点主机上的端口，可以从集群外部访问，发送到节点端口的请求将被转发给服务端口。NodePort 或 LoadBalancer 类型的服务具有节点端口。
|
||||
* Node Port: The port on the node host, accessible from outside the cluster. Requests sent to the node port will be forwarded to the service port. Services with the NodePort or LoadBalancer type have node ports.
|
||||
|
||||
|工作负载
|
||||
|显示管理容器组的工作负载的名称、更新时间、类型、状态和当前修改记录。
|
||||
| Workloads
|
||||
| Displays the name, update time, type, status, and current revision records of the workload managing the pods.
|
||||
|
||||
|容器组
|
||||
| Pods
|
||||
|
|
||||
include::../nodes/nodes-para-podList.adoc[]
|
||||
|===
|
||||
--
|
||||
|
||||
. 在服务详情页面右侧点击**元数据**页签查看服务的标签和注解。
|
||||
. Click the **Metadata** tab on the right side of the service details page to view the labels and annotations for the service.
|
||||
|
||||
. 在服务详情页面右侧点击**事件**页签查看服务相关的事件。
|
||||
. Click the **Events** tab on the right side of the service details page to view events related to the service.
|
||||
+
|
||||
--
|
||||
include::../clusterManagement-para-eventsTab.adoc[]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: f7bc10d6a0ae4ebfb0956bf2cd8624dd
|
||||
|创建时间
|
||||
|服务的创建时间。
|
||||
| Creation Time
|
||||
| The time the service created.
|
||||
|
|
@ -1,9 +1,9 @@
|
|||
// :ks_include_id: 9ed594d85e2d49d189b604ba75506964
|
||||
|外部访问
|
||||
|服务的外部访问模式。
|
||||
| External Access
|
||||
| The external access mode for the service.
|
||||
|
||||
// tag::bullets[]
|
||||
* **NodePort**：系统将节点的端口映射到服务端口，可通过节点的 IP 地址和节点端口访问服务。
|
||||
* **NodePort**: The system maps the ports of nodes to the service ports, and the service can be accessed through the node IP address and node port.
|
||||
|
||||
* **LoadBalancer**：系统在 NodePort 服务的基础上为服务分配一个外部 IP 地址，并将外部 IP 地址与一个外部负载均衡器绑定。外部负载均衡器监听服务对应的节点端口，从而可以通过外部 IP 地址访问服务。为实现上述功能，LoadBalancer 类型的服务需要负载均衡器插件和基础设施环境提供支持，并且需要设置相关注解。有关更多信息，请联系您的基础设施环境提供商。
|
||||
// end::bullets[]
|
||||
* **LoadBalancer**: On the basis of a NodePort service, the system assigns an external IP address to the service and binds the external IP address to an external load balancer. The external load balancer listens on the node port corresponding to the service, allowing access to the service through the external IP address. To achieve this, LoadBalancer-type services need support from load balancer plugins and the infrastructure environment, and relevant annotations need to be set. For more information, please contact your infrastructure environment provider.
|
||||
// end::bullets[]
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: ae3aeeab99d2436aaf471a053199ed31
|
||||
* **ExternalName**：服务将业务流量转发给集群外部的其他服务。系统不为服务分配虚拟 IP 地址，可通过 `<service name>.<project name>.svc.cluster.local` 格式的域名从集群内部访问。
|
||||
* **ExternalName**: The service routes business traffic to other services outside the cluster. The system does not assign a virtual IP address to the service, and it can be accessed internally by using the format `<service name>.<project name>.svc.cluster.local`.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: d2f7e4ed2c324015a246ad69584a8562
|
||||
服务的内部访问模式。
|
||||
The internal access mode for the service.
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: fc0d8d22d3934c7c8a894c53da744ea6
|
||||
|名称
|
||||
|服务的名称和描述信息。
|
||||
| Name
|
||||
| The name and description of the service.
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: f7106eed4381415e895021d16070780d
|
||||
|别名
|
||||
|服务的别名。不同服务的别名可以相同。别名只能包含中文、字母、数字和连字符（-），不得以连字符（-）开头或结尾，最长 63 个字符。
|
||||
| Alias
|
||||
| The alias of the service. Aliases can be the same for different services. Aliases can only contain Chinese characters, letters, numbers, and hyphens (-), and must not start or end with a hyphen (-), with a maximum length is 63 characters.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: 84acacc3966a4dea95858ffeabf4a6b7
|
||||
|描述
|
||||
|服务的描述信息。描述可包含任意字符，最长 256 个字符。
|
||||
| Description
|
||||
| The description of the service. The description can contain any characters, with a maximum length of 256 characters.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: 89c9a4c83d7a46889b95133fc816d28d
|
||||
|名称
|
||||
|服务的名称。同一项目中的服务名称不能重复。名称只能包含小写字母、数字和连字符（-），必须以小写字母开头并以小写字母或数字结尾，最长 63 个字符。
|
||||
| Name
|
||||
| The name of the service. Service names within the same project must be unique. Names can only contain lowercase letters, numbers, and hyphens (-), and must start and end with a lowercase letter or number, with a maximum length of 253 characters.
|
||||
|
|
@ -1,34 +1,34 @@
|
|||
// :ks_include_id: 797c8dc7400f4f17940a76eb88ae5149
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|内部访问模式
|
||||
|从集群内部访问服务的方式。
|
||||
| Internal Access Mode
|
||||
| The way to access the service within the cluster.
|
||||
|
||||
* **内部域名**：系统不为服务分配虚拟 IP 地址，可通过 `<service name>.<namespace>.svc.cluster.local` 或 `<service name>.<namespace>` 格式的域名从集群内部访问。
|
||||
* **Internal Domain Name**: The system does not assign a virtual IP address to the service. It can be accessed internally by using the format `<service name>.<namespace>.svc.cluster.local` or `<service name>.<namespace>`.
|
||||
|
||||
* **虚拟 IP 地址**：系统为服务分配一个虚拟 IP 地址供集群内部访问，同时也支持通过 `<service name>.<namespace>.svc.cluster.local` 或 `<service name>.<namespace>` 格式的域名从集群内部访问。
|
||||
* **Virtual IP Address**: The system assigns a virtual IP address to the service for internal access within the cluster. It also supports access internally by using the format `<service name>.<namespace>.svc.cluster.local` or `<service name>.<namespace>`.
|
||||
|
||||
|工作负载选择器
|
||||
|指定服务将业务流量转发给具有特定标签的工作负载管理的容器组。
|
||||
| Workload Selector
|
||||
| Specify the workloads with specific labels to which the service routes business traffic.
|
||||
|
||||
* 输入标签的键和值可手动设置选择器。点击**添加**可设置多个标签。
|
||||
* Manually set selectors by entering the key and value of a label. Click **Add** to set multiple labels.
|
||||
|
||||
* 点击**指定工作负载**可手动选择工作负载。
|
||||
* Manually select workloads by clicking **Specify Workload**.
|
||||
|
||||
* 在已创建的标签右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除标签。
|
||||
* Click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right side of a created label to delete it.
|
||||
|
||||
|端口
|
||||
|服务端口及其与目标容器端口的映射关系。
|
||||
| Ports
|
||||
| Map service ports and their corresponding container ports.
|
||||
|
||||
* **协议**：目标容器中的应用程序实际监听的协议。如需使用{ks_product-en}提供的应用治理功能，请确保此处选择的协议与目标容器中的应用程序实际监听的协议保持一致。
|
||||
* **Protocol**: The protocol that the application in the target container actually listens on. To use the application governance features provided by KubeSphere Enterprise, ensure that the protocol selected here matches the one the application in the target container actually listens on.
|
||||
|
||||
* **名称**：服务端口的名称。{ks_product-en}的应用治理功能要求服务端口名称以协议名称小写为前缀。如需使用{ks_product-en}提供的应用治理功能，请使用协议名称小写作为端口名称的前缀（例如 **http-**）。
|
||||
* **Name**: The name of the service port. The application governance features of KubeSphere Enterprise require the service port name to have the protocol name in lowercase as a prefix. To use the application governance features provided by KubeSphere Enterprise, use the lowercase protocol name as the prefix for the port name (e.g., **http-**).
|
||||
|
||||
* **容器端口**：目标容器中的应用程序实际监听的端口号。
|
||||
* **Container Port**: The port number on which the application in the target container actually listens.
|
||||
|
||||
* **服务端口**：服务的端口号。
|
||||
* **Service Port**: The port number of the service.
|
||||
|
||||
点击**添加**可设置多个服务端口。在已创建的服务端口右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除服务端口。
|
||||
Click **Add** to set multiple service ports. Click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right side of a created service port to delete it.
|
||||
|===
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: 9bd9803a7946434cb487882abcb428b8
|
||||
|会话保持
|
||||
|设置系统在指定的时间内将同一个会话中来自同一个客户端的请求全部转发给同一个容器组。最长会话保持时间默认值为 10800 秒，您也可以手动设置最长会话保持时间。
|
||||
| Session Persistence
|
||||
| Configure the system to forward all requests from the same client in the same session to the same pod within a specified duration. The default maximum stickiness duration is 10800 seconds, and you can also change it.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: bed3eb4cd7fa441990451420cd9a8ed4
|
||||
* **Headless**：系统不为服务分配虚拟 IP 地址，可通过 `<service name>.<project name>.svc.cluster.local` 或 `<service name>.<project name>` 格式的域名从集群内部访问。
|
||||
* **Headless**: The system does not assign a virtual IP address to the service. It can be accessed internally by using the format `<service name>.<project name>.svc.cluster.local` or `<service name>.<project name>`.
|
||||
|
||||
* **VirtualIP**：系统为服务分配一个虚拟 IP 地址供集群内部访问，同时也支持通过 `<service name>.<project name>.svc.cluster.local` 或 `<service name>.<project name>` 格式的域名从集群内部访问。
|
||||
* **VirtualIP**: The system assigns a virtual IP address to the service for internal access within the cluster. It also supports access internally by using the format `<service name>.<project name>.svc.cluster.local` or `<service name>.<project name>`.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 4521ce6a20e1414e9ee4a6025bfae0f4
|
||||
为容器挂载卷、配置字典或保密字典。
|
||||
Mount volumes, ConfigMaps, or Secrets for the container.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 847da7da89ca4546b3e0d53d8edb7441
|
||||
设置容器的镜像、名称、类型和资源。
|
||||
Configure the container's image, name, type, and resources.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: c366a748b75848288944f6526bbf6aa7
|
||||
设置工作负载的标签和注解。
|
||||
Configure labels and annotations for the workload.
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: a03937e2a0cc45ffac2b60c8f2321638
|
||||
* 将光标悬停在已添加的卷或持久卷声明模板上，然后在右侧点击image:/images/ks-qkcp/zh/icons/pen-light.svg[pen,18,18]可编辑卷或持久卷声明模板的设置。
|
||||
* 将光标悬停在已挂载的卷或持久卷声明模板上，然后在右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除卷或持久卷声明模板。
|
||||
* Hover over the added volume or PVC template, then click image:/images/ks-qkcp/zh/icons/pen-light.svg[pen,18,18] on the right to edit its settings.
|
||||
* Hover over the mounted volume or PVC template, then click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right to delete it.
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: a03937e2a0cc45ffac2b60c8f2321638
|
||||
* 将光标悬停在已添加的卷上，然后在右侧点击image:/images/ks-qkcp/zh/icons/pen-light.svg[pen,18,18]可编辑卷的设置。
|
||||
* 将光标悬停在已挂载的卷上，然后在右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除卷。
|
||||
* Hover over the added volume, then click image:/images/ks-qkcp/zh/icons/pen-light.svg[pen,18,18] on the right to edit the volume settings.
|
||||
* Hover over the mounted volume, then click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right to delete the volume.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: 6d818141bdf246f49b4c4825976cc804
|
||||
* 点击**添加**可设置多条标签或注解。
|
||||
* Click **Add** to set multiple labels or annotations.
|
||||
|
||||
* 在已创建的标签或注解右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除标签或注解。
|
||||
* Click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right of a created label or annotation to delete it.
|
||||
|
|
@ -1,4 +1,3 @@
|
|||
// :ks_include_id: 7e4e28a3e5ce47da9d146777b262caf4
|
||||
|
||||
设置容器终止前等待的时间，超时后容器将强制终止。默认取值为 30s。
|
||||
|
||||
Set the waiting time before the pod terminates; the pod will be forcefully terminated after the specified timeout. The default value is 30 seconds.
|
||||
|
|
@ -1,6 +1,5 @@
|
|||
// :ks_include_id: 91f17518b6d34f729b683653e6fa81e3
|
||||
设置容器组的元数据。目前仅支持设置容器组的注解，不支持设置容器组的标签。
|
||||
Add metadata for the pod. Currently, you can only set annotations for the pod.
|
||||
|
||||
* 点击添加可设置多条注解。
|
||||
|
||||
* 在已创建的注解右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除注解。
|
||||
* Click **Add** to set multiple annotations.
|
||||
* To delete an annotation, Click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right of the created annotation.
|
||||
|
|
@ -1,16 +1,16 @@
|
|||
// :ks_include_id: addcd8f38f374f16a793b840c8f4524b
|
||||
设置容器的端口。点击**使用默认镜像端口**可将容器端口设置为镜像的默认端口。点击**添加端口**可为容器设置多个端口。
|
||||
Configure the ports for the container. Click **Use Default Port of Images** to set the container ports to the default ports of the image. Click **Add Port** to set multiple ports for the container.
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|协议
|
||||
|容器中的应用程序实际监听的协议。如需使用{ks_product-en}提供的应用治理功能，请确保此处选择的协议与容器中的应用程序实际监听的协议保持一致。
|
||||
| Protocol
|
||||
| The protocol that the application in the container actually listens to. To use the Application Governance features provided by KubeSphere, ensure that the selected protocol matches the protocol that the application in the container actually listens to.
|
||||
|
||||
|名称
|
||||
|端口的名称。如需使用{ks_product-en}提供的应用治理功能，请使用协议名称小写作为端口名称的前缀（例如 **http-**）。
|
||||
| Name
|
||||
| The name of the port. To use the Application Governance features provided by KubeSphere, use the lowercase protocol name as a prefix for the port name (e.g., **http-**).
|
||||
|
||||
|容器端口
|
||||
|容器中的应用程序实际监听的端口号。
|
||||
|===
|
||||
| Container Port
|
||||
| The port number that the application in the container actually listens to.
|
||||
|===
|
||||
|
|
@ -1,22 +1,22 @@
|
|||
// :ks_include_id: 90da833da58d47cbad5d77d94fe4d826
|
||||
创建容器启动后动作或终止前动作。
|
||||
Create post-start or pre-termination actions for the container.
|
||||
|
||||
* 点击**添加动作**可创建动作。
|
||||
* Click **Add Action** to create an action.
|
||||
|
||||
* 将光标悬停在已创建的动作上，然后在右侧点击image:/images/ks-qkcp/zh/icons/pen-light.svg[pen,18,18]可编辑动作的设置。
|
||||
* Hover over the created action, then click image:/images/ks-qkcp/zh/icons/pen-light.svg[pen,18,18] on the right to edit the action settings.
|
||||
|
||||
* 将光标悬停在已创建的动作上，然后在右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除动作。
|
||||
* Hover over the created action, then click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right to delete the action.
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|路径
|
||||
|HTTP 请求的协议（HTTP 或 HTTPS）、请求目标相对于容器组虚拟 IP 地址的路径以及请求的端口号。仅在动作执行方式为 **HTTP 请求**时可用。
|
||||
| Path
|
||||
| The protocol (HTTP or HTTPS), the path relative to the virtual IP address of the pod for HTTP requests, and the port number for the request. Only available when the action execution method is **HTTP Request**.
|
||||
|
||||
|命令
|
||||
|将要在容器中运行的命令。您可以使用半角逗号（,）分隔命令及其参数。仅在动作执行方式为**命令**时可用。
|
||||
| Command
|
||||
| The command to run in the container. You can use commas (,) to separate the commands and its parameters. Only available when the action execution method is **Command**.
|
||||
|
||||
|端口
|
||||
|用于 TCP 检查的容器端口号。仅在动作执行方式为 **TCP 端口**时可用。
|
||||
| Port
|
||||
| The container port number for TCP checks. Only available when the action execution method is **TCP Port**.
|
||||
|===
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
// :ks_include_id: 26629381ce2c4637b491e4fe2386923e
|
||||
创建容器组中运行的容器。您可以在容器组中创建多个容器。
|
||||
Create containers to run within the pod. You can create multiple containers within a pod.
|
||||
|
||||
* 点击**添加容器**可创建容器。
|
||||
* Click **Add Container** to create a container.
|
||||
|
||||
* 将光标悬停在已创建的容器上，然后在右侧点击image:/images/ks-qkcp/zh/icons/pen-light.svg[pen,18,18]可编辑容器的设置。
|
||||
* Hover over a created container, then click image:/images/ks-qkcp/zh/icons/pen-light.svg[pen,18,18] on the right to edit the container settings.
|
||||
|
||||
* 将光标悬停在已创建的容器上，然后在右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除容器。
|
||||
* Hover over a created container, then click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right to delete the container.
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: 87861bb084774716a738a763e7cb8d5a
|
||||
|添加持久卷声明模板
|
||||
|为有状态副本集添加持久卷声明模板。系统将为每个容器组副本单独创建持久卷声明和持久卷，并将持久卷分别挂载到每个容器组副本中的指定容器。仅对**有状态副本集**可用。
|
||||
|Add Persistent Volume Claim Template
|
||||
|Add Persistent Volume Claim templates for StatefulSets. The system will create separate Persistent Volume Claims and Persistent Volumes for each pod replica, and mount the Persistent Volumes to the specified containers in each pod replica. Only available for **StatefulSets**.
|
||||
|
|
@ -1,37 +1,37 @@
|
|||
// :ks_include_id: 55d0e202da594ec3bf0eec8a473d3557
|
||||
创建探针对容器进行存活检查、就绪检查或启动检查。
|
||||
Create probes for liveness, readiness, or startup checks on the container.
|
||||
|
||||
* 点击**添加探针**可创建探针。
|
||||
* Click **Add Probe** to create a probe.
|
||||
|
||||
* 将光标悬停在已创建的探针上，然后在右侧点击image:/images/ks-qkcp/zh/icons/pen-light.svg[pen,18,18]可编辑探针的设置。
|
||||
* Hover over the created probe, then click image:/images/ks-qkcp/zh/icons/pen-light.svg[pen,18,18] on the right to edit the probe settings.
|
||||
|
||||
* 将光标悬停在已创建的探针上，然后在右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除探针。
|
||||
* Hover over the created probe, then click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right to delete the probe.
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|路径
|
||||
|HTTP 请求的协议（HTTP 或 HTTPS）、请求目标相对于容器组虚拟 IP 地址的路径以及请求的端口号。仅在健康检查方式为 **HTTP 请求**时可用。
|
||||
| Path
|
||||
| The protocol (HTTP or HTTPS), the path relative to the virtual IP address of the pod for HTTP requests, and the port number for the request. Only available when the health check method is **HTTP Request**.
|
||||
|
||||
|命令
|
||||
|将要在容器中运行的命令。您可以使用半角逗号（,）分隔命令及其参数。仅在健康检查方式为**命令**时可用。
|
||||
| Command
|
||||
| The command to run in the container. You can use commas (,) to separate the commands and its parameters. Only available when the health check method is **Command**.
|
||||
|
||||
|端口
|
||||
|用于 TCP 检查的容器端口号。仅在健康检查方式为 **TCP 端口**时可用。
|
||||
| Port
|
||||
| The container port number for TCP checks. Only available when the health check method is **TCP Port**.
|
||||
|
||||
|初始延迟
|
||||
|容器启动后探针启动前的延迟时间，单位为秒。
|
||||
| Initial Delay
|
||||
| The delay time in seconds before the probe is initiated after container startup.
|
||||
|
||||
|超时时间
|
||||
|探针超时时间，单位为秒。探针超时后，检查将被视为失败。取值必须为整数，最小值为 **0**。
|
||||
| Timeout
|
||||
| The timeout period for the probe in seconds. After the timeout, the check will be considered a failure. The value must be an integer, with a minimum of **0**.
|
||||
|
||||
|检查间隔
|
||||
|执行检查的时间间隔，单位为秒。取值必须为整数，最小值为 **1**。
|
||||
| Check Interval
|
||||
| The time interval for performing checks in seconds. The value must be an integer, with a minimum of **1**.
|
||||
|
||||
|成功阈值
|
||||
|检查失败后再次被视为成功所需的最小连续成功次数，最小值为 **1**。对于存活探针和启动探针，此参数值必须为 **1**。
|
||||
| Success Threshold
|
||||
| The minimum consecutive successes required to consider the check successful after a failure. The minimum value is **1**. For liveness probes and startup probes, this parameter must be **1**.
|
||||
|
||||
|失败阈值
|
||||
|检查成功后再次被视为失败所需的最小连续失败次数，最小值为 **1**。
|
||||
| Failure Threshold
|
||||
| The minimum consecutive failures required to consider the check failed after a success. The minimum value is **1**.
|
||||
|===
|
||||
|
|
@ -1,25 +1,24 @@
|
|||
// :ks_include_id: aaa01b3ba5d6460b9ee0d50de5a5def9
|
||||
* 基本信息
|
||||
* Basic Information
|
||||
+
|
||||
--
|
||||
设置工作负载的基本信息。
|
||||
Configure the basic information for the workload.
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|名称
|
||||
|工作负载的名称。名称只能包含小写字母、数字和连字符（-），必须以小写字母或数字开头和结尾，最长 253 个字符。
|
||||
| Name
|
||||
| The name of the workload. The name can only contain lowercase letters, numbers, and hyphens (-). It must start and end with a lowercase letter or number, with a maximum length of 253 characters.
|
||||
|
||||
|别名
|
||||
|工作负载的别名。不同工作负载的别名可以相同。别名只能包含中文、字母、数字和连字符（-），不得以连字符（-）开头或结尾，最长 63 个字符。
|
||||
| Alias
|
||||
| The alias of the workload. Aliases can be the same for different workloads. The alias can only contain Chinese characters, letters, numbers, and hyphens (-). It must not start or end with a hyphen (-), with a maximum length of 63 characters.
|
||||
|
||||
ifndef::kubefed[]
|
||||
|项目
|
||||
|将要创建资源的项目。
|
||||
| Project
|
||||
| The project in which the resources will be created.
|
||||
endif::[]
|
||||
|
||||
|描述
|
||||
|工作负载的描述信息。描述可包含任意字符，最长 256 个字符。
|
||||
| Description
|
||||
| The description of the workload. The description can contain any characters, with a maximum length of 256 characters.
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,10 +1,10 @@
|
|||
// :ks_include_id: 0c5011c424e145ec95155aed67c9fccb
|
||||
|镜像
|
||||
| Image
|
||||
|
|
||||
创建容器所需的镜像。
|
||||
The image required to create the container.
|
||||
|
||||
* 输入镜像的名称（例如 **nginx:latest**）或路径（例如 **docker.io/nginx:latest**），然后按 **Enter** 键可搜索镜像。
|
||||
* Enter the image name (e.g., **nginx:latest**) or path (e.g., **docker.io/nginx:latest**), then press **Enter** to search for the image.
|
||||
|
||||
* 如果您只输入镜像的名称，默认情况下将从 Docker Hub 拉取镜像。如需使用私有镜像服务，您需要创建包含私有镜像服务信息的保密字典，然后在**镜像**文本框左侧选择私有镜像服务。
|
||||
* If you only enter the image name, the image will be pulled from Docker Hub by default. To use a private image registry, you need to create a Secret containing the information for the private image registry, and then select the private image registry on the left side of the **Image** text box.
|
||||
|
||||
* 点击image:/images/ks-qkcp/zh/icons/templet.svg[template,18,18]可浏览当前镜像服务中的镜像。
|
||||
* Click image:/images/ks-qkcp/zh/icons/templet.svg[template,18,18] to browse images in the current image registry.
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: 3e5d0001b8ce42a688e457086df147d3
|
||||
|容器名称
|
||||
|容器的名称。名称只能包含小写字母、数字和连字符（-），必须以小写字母或数字开头和结尾，最长 63 个字符。
|
||||
| Container Name
|
||||
| The name of the container. The name can only contain lowercase letters, numbers, and hyphens (-). It must start and end with a lowercase letter or number, with a maximum length of 63 characters.
|
||||
|
|
@ -1,27 +1,36 @@
|
|||
// :ks_include_id: 03ba4803bc5e4930b178cd6397356d2c
|
||||
设置容器进程在 Linux 系统中的权限。
|
||||
Configure the permissions of the container process in the Linux system.
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|访问控制
|
||||
| Access Control
|
||||
| Access permissions for the container process.
|
||||
|
||||
* **Privileged Mode**: Run the container process as the **root** user on the host.
|
||||
|
||||
* **Allow Privilege Escalation**: Allow the container process to gain more privileges than the parent process. This option is enabled by default when **Privileged Mode** is enabled.
|
||||
|
||||
* **Root Directory Read-Only**: Set the root directory of the container filesystem to read-only.
|
||||
|
||||
|User and User Group
|
||||
|
|
||||
容器进程的访问权限。
|
||||
The users and user groups running the entry point of container processes.
|
||||
|
||||
* **特权模式**：以主机上的 **root** 用户运行容器进程。
|
||||
* **Run as Non-root**: Checks if the container will run as the **root** user before starting. If the container is set to run as the **root** user, it won't start. When this feature is enabled, the system will ignore the **Privileged mode** setting.
|
||||
|
||||
* **允许特权提升**：允许容器进程获取比父进程更多的特权。当**特权模式**启用时，此选项默认启用。
|
||||
* **User**: The UID (User ID) executing the container process entry point. Defaults to the UID specified in the image metadata.
|
||||
|
||||
* **根目录只读**：将容器文件系统的根目录设置为只读。
|
||||
* **User Group**: The GID (Group ID) executing the container process entry point. Defaults to the default GID of the container runtime.
|
||||
|
||||
include::workloads-para-uidGidSelinux.adoc[]
|
||||
|SELinux Context
|
||||
|The SELinux labels for the container process, including **Level**, **Role**, **Type**, and **User**. For more information, refer to the link:https://www.selinuxproject.org/page/Main_Page[SELinux Documentation].
|
||||
|
||||
|权能
|
||||
|
|
||||
在 Linux 系统中对容器进程额外添加或移除的权限。请参阅 link:https://man7.org/linux/man-pages/man7/capabilities.7.html[Linux 官方文档]获取 Linux 进程的权能列表。
|
||||
| Capabilities
|
||||
| Additional capabilities added to or removed from the container process in the Linux system. Refer to the link:https://man7.org/linux/man-pages/man7/capabilities.7.html[Linux Documentation] for the list of Linux process capabilities.
|
||||
|
||||
* 为容器进程添加或移除权能时，您需要去掉权能名称中的 **CAP_** 前缀。例如，在**移除**文本框中输入 **SYS_TIME** 可移除容器进程的 **CAP_SYS_TIME** 权能。
|
||||
* When adding or removing capabilities for the container process, you need to remove the **CAP_** prefix from the capability names. For example, entering **SYS_TIME** in the **Drop** text box will remove the **CAP_SYS_TIME** capability from the container process.
|
||||
|
||||
* 点击**添加**可设置多条权能添加或移除指令。
|
||||
* Click **Add** to set multiple instructions for adding or removing capabilities.
|
||||
|===
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
// :ks_include_id: 44485d9a2c89473b896d0aa6c172b2c2
|
||||
|容器类型
|
||||
| Container Type
|
||||
|
|
||||
容器的类型。
|
||||
The type of container.
|
||||
|
||||
* **初始化容器**：为工作容器进行初始化工作的容器。工作容器只有在所有初始化容器成功完成之后才会启动。如果初始化容器运行失败，系统会把容器组的状态设置为失败。
|
||||
* **Init Container**: A container that performs initialization tasks for the working containers. The working containers will only start after all init containers have successfully completed. If an init container fails, the system sets the status of the pod to failure.
|
||||
|
||||
* **工作容器**：运行应用程序的容器。通常建议每个容器组中只运行一个工作容器。
|
||||
* **Work Container**: A container that runs the application. It is generally recommended to have only one work container running in each pod.
|
||||
|
|
@ -1,30 +1,29 @@
|
|||
// :ks_include_id: 3bea77d96c69484c89893f226380c3c4
|
||||
设置自定义的容器组调度规则。
|
||||
Configure custom rules for pod scheduling.
|
||||
|
||||
* 点击**添加**可以设置多条规则。
|
||||
|
||||
* 在已创建的规则右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除规则。
|
||||
* Click **Add** to set multiple rules.
|
||||
* To delete a rule, Click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right of the created rule.
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|类型
|
||||
|Type
|
||||
|
|
||||
规则的类型。
|
||||
The type of the rule.
|
||||
|
||||
* **与目标调度到一起**：容器组副本将与当前项目中具特定标签的容器组调度到同一个节点。
|
||||
* **Schedule with target** : Pod replicas will be scheduled to the same node as other pods with specific labels in the current project.
|
||||
|
||||
* **远离目标**：容器组副本将与当前项目中具特定标签的容器组调度到不同节点。
|
||||
* **Schedule away from target** : Pod replicas will be scheduled to different nodes than other pods with specific labels in the current project.
|
||||
|
||||
|策略
|
||||
|Policy
|
||||
|
|
||||
规则实施的策略。
|
||||
The policy by which the rule is enforced.
|
||||
|
||||
* **尽可能匹配**：尽可能满足规则要求。如果规则要求无法得到满足，容器组副本将被调度到不满足规则要求节点上。
|
||||
* **Match if possible** : Try to satisfy the rule as much as possible. If the rule cannot be satisfied, the pod replicas will be scheduled to nodes that do not meet the rule requirements.
|
||||
|
||||
* **必须匹配**：必须满足规则要求。如果规则要求无法得到满足，容器组副本将不能调度到任何节点上。
|
||||
* **Must match** : Must satisfy the rule requirements. If the rule requirements cannot be met, the pod replicas will not be scheduled to any node.
|
||||
|
||||
|目标
|
||||
|规则的目标。容器组副本将与具有 **app=**<target> 标签（<target> 为此处选择的值）的容器组调度到同一个节点或不同节点，取决于规则的类型和策略。
|
||||
|Target
|
||||
|The target of the rule. Pod replicas will be scheduled to the same or different nodes as pods with the label **app=**<target> (<target> is the selected value here), depending on the rule's type and policy.
|
||||
|===
|
||||
|
|
@ -1,25 +1,25 @@
|
|||
// :ks_include_id: 5f8f7ff05ece4c439f6806ad715b9c8c
|
||||
设置容器的环境变量。
|
||||
Configure environment variables for the container.
|
||||
|
||||
* 点击**添加环境变量**可设置多个环境变量。
|
||||
* Click **Add Environment Variable** to set multiple environment variables.
|
||||
|
||||
* 点击**批量引用**可使用配置字典或保密字典中的数据创建环境变量。配置字典或密保字典必须与容器属于同一个项目才能被容器引用。容器创建后环境变量的值不会随配置字典或保密字典设置的变更而动态变化。
|
||||
* Click **Batch Reference** to create environment variables using data from a ConfigMap or Secret. The ConfigMap or Secret to be referenced must belong to the same project as the container. The values of environment variables will not dynamically change with changes made in the ConfigMap or Secret after the container is created.
|
||||
|
||||
* 在已创建的环境变量右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除环境变量。
|
||||
* Click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right of the created environment variable to delete it.
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
| Parameter | Description
|
||||
|
||||
|键
|
||||
|环境变量的名称。
|
||||
| Key
|
||||
| The name of the environment variable.
|
||||
|
||||
|值
|
||||
|环境变量的值。
|
||||
| Value
|
||||
| The value of the environment variable.
|
||||
|
||||
|资源
|
||||
|配置字典或保密字典的名称。仅在引用配置字典或保密字典时可用。
|
||||
| Resource
|
||||
| The name of the ConfigMap or Secret. Only available when referencing a ConfigMap or Secret.
|
||||
|
||||
|资源中的键
|
||||
|配置字典或保密字典中的键。与该键对应的值将被用作环境变量的值。仅在引用配置字典或保密字典时可用。
|
||||
| Key in Resource
|
||||
| The key in the ConfigMap or Secret. The value corresponding to this key will be used as the value of the environment variable. Only available when referencing a ConfigMap or Secret.
|
||||
|===
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue