Deployed da72e30 with MkDocs version: 1.6.0

admin/ghippo/best-practice/authz-plan.html

@@ -521,14 +521,6 @@ <h1 id="_1">普通用户授权规划<a class="headerlink" href="#_1" title="Perm
  classDef cluster fill:#fff,stroke:#bbb,stroke-width:1px,color:#326ce5;
  class user,ns,ws,ws-to-ns,authu cluster;
  class start,complete plain;</code></pre>
-<p>授权后普通用户在各模块的权限为：</p>
-<ul>
-<li><a href="../permissions/amamba.md">应用工作台</a></li>
-<li><a href="../permissions/skoala.md">微服务引擎</a></li>
-<li><a href="../permissions/mspider.md">服务网格</a>（需要重复 2 - 4 准备网格/网格命名空间并绑定到工作空间）</li>
-<li><a href="../../insight/intro/permission.md">可观测性</a></li>
-<li><a href="../permissions/mcamel.md">数据服务</a></li>
-</ul>
 </article>
 </div>
 <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script>

admin/ghippo/best-practice/ws-best-practice.html

@@ -641,25 +641,11 @@ <h2 id="_2">工作空间的功能<a class="headerlink" href="#_2" title="Permane
 </li>
 </ol>
 <h2 id="ai">工作空间对 AI 算力中心各模块的作用<a class="headerlink" href="#ai" title="Permanent link">¶</a></h2>
-<ol>
-<li>
-<p>模块名称：<a href="../../amamba/intro/index.md">应用工作台</a>、<a href="../../skoala/intro/index.md">微服务引擎</a>、<a href="../../middleware/index.md">中间件</a>、<a href="../../kangaroo/intro/index.md">镜像仓库</a>、<a href="../../kant/intro/index.md">云边协同</a></p>
-<p>进入上述几个模块的前提是拥有某个工作空间的权限，因此在使用模块功能前必须具有 Admin 角色或者拥有某个工作空间的一定角色权限。</p>
-<ul>
-<li>工作空间的角色会自动应用到工作空间包含的资源上。比如当您拥有工作空间 A 的 Workspace Admin 角色，那么对于该工作空间中的所有资源您都是 Admin 角色；</li>
-<li>如果您是 Workspace Edit，那么对于工作空间中的所有资源您都是 Edit 角色；</li>
-<li>如果您是 Workspace View，那么对于工作空间中的所有资源您都是 View 角色。</li>
-</ul>
-<p>另外，您在这些模块创建的资源也将自动被绑定到对应的工作空间中，而不需要其他额外的操作。</p>
-</li>
-<li>
-<p>模块名称：<a href="../../kpanda/intro/index.md">容器管理</a>、<a href="../../mspider/intro/index.md">服务网格</a>、<a href="../../kairship/intro/index.md">多云编排</a></p>
+<p>模块名称：容器管理</p>
 <p>由于功能模块的特殊性，在容器管理模块创建的资源不会自动被绑定到某个工作空间。</p>
 <p>如果您需要通过工作空间对人和资源进行统一授权管理，可以手动将需要的资源绑定到某个工作空间中，从而将用户在该工作空间的角色应用到资源上（这里的资源是可以跨集群的）。</p>
 <p>另外，在资源的绑定入口上容器管理与服务网格稍有差异，工作空间提供了容器管理中的 Cluster 、 Cluster-Namesapce 和服务网格中的 Mesh、Mesh-Namespace 资源的绑定入口，但尚未开放对服务网格的 kairship 和 Kairship-Namespace 资源的绑定。</p>
 <p>对于 kairship 和 Kairship-Namespace 资源，可以在服务网格的资源列表进行手动绑定。</p>
-</li>
-</ol>
 <h2 id="_3">工作空间的使用场景<a class="headerlink" href="#_3" title="Permanent link">¶</a></h2>
 <ul>
 <li>映射为不同的部门、项目、组织等概念，同时可以将工作空间中 Workspace Admin、Workspace Edit 和 Workspace View 角色对应到部门、项目、组织中的不同角色</li>

admin/insight/best-practice/debug-log.html

@@ -657,16 +657,12 @@ <h2 id="_2">插件说明<a class="headerlink" href="#_2" title="Permanent link">
 <tbody>
 <tr>
 <td>es.kube.kubeevent.syslog</td>
-<td>把 Kubernetes 审计日志、事件日志，syslog 日志写入 <a href="../../middleware/elasticsearch/intro/index.md">ElasticSearch 集群</a></td>
+<td>把 Kubernetes 审计日志、事件日志，syslog 日志写入 ElasticSearch 集群</td>
 </tr>
 <tr>
 <td>forward.audit_log</td>
 <td>把 Kubernetes 审计日志和<a href="../../ghippo/audit/audit-log.html">全局管理的审计日志</a>发送到 <strong>全局管理</strong></td>
 </tr>
-<tr>
-<td>es.skoala</td>
-<td>把微服务网关的<a href="../../skoala/gateway/logs/reqlog.md">请求日志</a>和<a href="../../skoala/gateway/logs/inslog.md">实例日志</a>写入到 ElasticSearch 集群</td>
-</tr>
 </tbody>
 </table>
 </article>

admin/insight/best-practice/debug-trace.html

@@ -600,12 +600,12 @@ <h2 id="_2">区块介绍<a class="headerlink" href="#_2" title="Permanent link">
 <p><img alt="tracing debug" src="https://docs.daocloud.io/daocloud-docs-images/docs/insight/images/insighttrace04.png"/></p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p><strong>全局服务集群</strong> 的 <strong>opentelemetry collector</strong> 还负责发送所有工作集群的<a href="../../ghippo/intro/index.md">全局管理模块</a>的<a href="../../ghippo/audit/audit-log.html">审计日志</a>以及 Kubernetes 审计日志（默认不采集）到全局管理模块的 <strong>audit server</strong> 组件。</p>
+<p><strong>全局服务集群</strong> 的 <strong>opentelemetry collector</strong> 还负责发送所有工作集群的全局管理模块的<a href="../../ghippo/audit/audit-log.html">审计日志</a>以及 Kubernetes 审计日志（默认不采集）到全局管理模块的 <strong>audit server</strong> 组件。</p>
 </div>
 </li>
 <li>
 <p><strong>global jaeger collector</strong></p>
-<p>展示 <strong>全局服务集群</strong> 的 <strong>jaeger collector</strong> 在接收 <strong>全局服务集群</strong> 中 <strong>otel collector</strong> 的数据，并发送链路数据到 <a href="../../middleware/elasticsearch/intro/index.md">ElasticSearch 集群</a>的情况。</p>
+<p>展示 <strong>全局服务集群</strong> 的 <strong>jaeger collector</strong> 在接收 <strong>全局服务集群</strong> 中 <strong>otel collector</strong> 的数据，并发送链路数据到 ElasticSearch 集群的情况。</p>
 <p><img alt="tracing debug" src="https://docs.daocloud.io/daocloud-docs-images/docs/insight/images/insighttrace05.png"/></p>
 </li>
 </ol>

admin/kpanda/clusters/cluster-role.html

@@ -699,10 +699,6 @@ <h2 id="_2">全局服务集群<a class="headerlink" href="#_2" title="Permanent
 </table>
 <h2 id="_3">管理集群<a class="headerlink" href="#_3" title="Permanent link">¶</a></h2>
 <p>此集群用于管理工作集群，一般不承载业务负载。</p>
-<ul>
-<li>经典模式将全局服务集群和管理集群部署在不同的集群，适用于企业多数据中心、多架构的场景。</li>
-<li>简约模式将管理集群和全局服务集群部署在同一个集群内。</li>
-</ul>
 <table>
 <thead>
 <tr>

admin/kpanda/workloads/pod-config/workload-status.html

@@ -403,7 +403,7 @@ <h3 id="_5">定时任务状态<a class="headerlink" href="#_5" title="Permanent
 </tr>
 </tbody>
 </table>
-<p>当工作负载处于异常或未就绪状态时，您可以通过将鼠标移动到负载的状态值上，系统将通过提示框展示更加详细的错误信息。您也可以通过查看<a href="../../../../insight/data-query/log.mdlog.md">日志</a>或事件来获取工作负载的相关运行信息。</p>
+<p>当工作负载处于异常或未就绪状态时，您可以通过将鼠标移动到负载的状态值上，系统将通过提示框展示更加详细的错误信息。您也可以通过查看<a href="../../../insight/data-query/log.html">日志</a>或事件来获取工作负载的相关运行信息。</p>
 </article>
 </div>
 <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script>

en/admin/baize/best-practice/finetunel-llm.html

@@ -766,7 +766,7 @@ <h2 id="environment-requirements">Environment Requirements<a class="headerlink"
 </ul>
 <div class="admonition info">
 <p class="admonition-title">Info</p>
-<p>Before starting, ensure AI platform and <a href="../intro/install.md">AI Lab</a> are correctly installed,
+<p>Before starting, ensure AI platform and AI Lab are correctly installed,
 GPU queue resources are successfully initialized, and computing resources are sufficient.</p>
 </div>
 <h2 id="prepare-data">Prepare Data<a class="headerlink" href="#prepare-data" title="Permanent link">¶</a></h2>

en/admin/baize/developer/inference/models.html

@@ -295,8 +295,7 @@ <h1 id="model-support">Model Support<a class="headerlink" href="#model-support"
 </ul>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>The support for inference capabilities is related to the version of AI Lab.
-Refer to the <a href="../../intro/release-notes.md">Release Notes</a> to understand the latest version and update timely.</p>
+<p>The support for inference capabilities is related to the version of AI Lab.</p>
 </div>
 <p>You can use GPU types that have been verified by AI platform in AI Lab.
 For more details, refer to the <a href="../../../kpanda/gpu/gpu_matrix.html">GPU Support Matrix</a>.</p>

en/admin/ghippo/best-practice/authz-plan.html

@@ -521,10 +521,6 @@ <h1 id="ordinary-user-authorization-plan">Ordinary user authorization plan<a cla
  classDef cluster fill:#fff,stroke:#bbb,stroke-width:1px,color:#326ce5;
  class user,ns,ws,ws-to-ns,authu cluster;
  class start,complete plain;</code></pre>
-<p>After authorization, the permissions of ordinary users in each module are:</p>
-<ul>
-<li><a href="../../insight/intro/permission.md">Observability</a></li>
-</ul>
 </article>
 </div>
 <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script>

en/admin/ghippo/best-practice/cluster-for-multiws.html

@@ -610,9 +610,7 @@ <h1 id="assign-a-cluster-to-multiple-workspaces-tenants">Assign a Cluster to Mul
 
 click preparews "https://docs.daocloud.io/en/ghippo/workspace/cluster-for-multiws/#prepare-a-workspace"
 click preparecs "https://docs.daocloud.io/en/ghippo/workspace/cluster-for-multiws/#prepare-a-cluster"
-click share "https://docs.daocloud.io/en/ghippo/workspace/cluster-for-multiws/#add-a-cluster-to-the-workspace"
-click createns "https://docs.daocloud.io/en/amamba/user-guide/namespace/namespace/#create-a-namespace"
-click modifyns "https://docs.daocloud.io/en/amamba/user-guide/namespace/namespace/#namespace-quotas"</code></pre>
+click share "https://docs.daocloud.io/en/ghippo/workspace/cluster-for-multiws/#add-a-cluster-to-the-workspace"</code></pre>
 <h2 id="prepare-a-workspace">Prepare a Workspace<a class="headerlink" href="#prepare-a-workspace" title="Permanent link">¶</a></h2>
 <p>Workspaces are designed to meet multi-tenant usage scenarios, forming isolated resource environments based on clusters,
 cluster namespaces, meshes, mesh namespaces, multicloud, multicloud namespaces, and other resources. Workspaces
@@ -655,8 +653,6 @@ <h2 id="add-cluster-to-workspace">Add Cluster to Workspace<a class="headerlink"
 <p><img alt="Add Resource" src="../images/addcluster02.png"/></p>
 </li>
 </ol>
-<p>Next Step: After allocating cluster resources to multiple workspaces, users can go to <strong>Workbench</strong> to
-<a href="../../amamba/user-guide/namespace/namespace.md">create namespaces and deploy applications</a> in these workspaces.</p>
 </article>
 </div>
 <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script>

en/admin/ghippo/best-practice/ws-best-practice.html

@@ -659,7 +659,7 @@ <h2 id="workspace-features">Workspace features<a class="headerlink" href="#works
 </li>
 </ol>
 <h2 id="the-effect-of-the-workspace-on-the-ai-platfrom">The effect of the workspace on the AI platfrom<a class="headerlink" href="#the-effect-of-the-workspace-on-the-ai-platfrom" title="Permanent link">¶</a></h2>
-<p>Module name: <a href="../../kpanda/intro/index.md">Container Management</a></p>
+<p>Module name: Container Management</p>
 <p>Due to the particularity of functional modules, resources created in the container management module will not be automatically bound to a certain workspace.</p>
 <p>If you need to perform unified authorization management on people and resources through workspaces, you can manually bind the required resources to a certain workspace, to apply the roles of users in this workspace to resources (resources here can be cross- clustered).</p>
 <p>In addition, there is a slight difference between container management and service mesh in terms of resource binding entry. The workspace provides the binding entry of Cluster and Cluster-Namespace resources in container management, but has not opened the Mesh and Mesh-Namespace for service mesh. Bindings for Namespace resources.</p>

en/admin/ghippo/permissions/kpanda.html

@@ -288,8 +288,8 @@ <h1 id="container-management-permissions">Container Management Permissions<a cla
 <tbody>
 <tr>
 <td>Cluster</td>
-<td>Cluster List</td>
-<td>View Cluster List</td>
+<td>Clusters</td>
+<td>View Clusters</td>
 <td>✔</td>
 <td>✔</td>
 <td>✔</td>

en/admin/ghippo/workspace/quota.html

@@ -595,7 +595,7 @@ <h1 id="resource-quota">Resource Quota<a class="headerlink" href="#resource-quot
 <p>A resource (cluster) can be shared among multiple workspaces, and a workspace can use resources from
 multiple shared clusters simultaneously.</p>
 <h2 id="resource-groups-and-shared-resources">Resource Groups and Shared Resources<a class="headerlink" href="#resource-groups-and-shared-resources" title="Permanent link">¶</a></h2>
-<p>Cluster resources in both shared resources and resource groups are derived from <a href="../../../kpanda/intro/index.md">Container Management</a>. However, different effects will occur when binding a cluster to a workspace or sharing it with a workspace.</p>
+<p>Cluster resources in both shared resources and resource groups are derived from Container Management. However, different effects will occur when binding a cluster to a workspace or sharing it with a workspace.</p>
 <ol>
 <li>
 <p>Binding Resources</p>

en/admin/ghippo/workspace/ws-permission.html

@@ -708,10 +708,6 @@ <h2 id="permission-description">Permission description<a class="headerlink" href
 <p>Authorized users can go to modules such as workbench, microservice engine, middleware, multicloud orchestration, and service mesh to use resources in the workspace.
  For the operation scope of the roles of Workspace Admin, Workspace Editor, and Workspace Viewer in each module, please refer to the permission description:</p>
 <ul>
-<li><a href="../../permissions/amamba.md">Workbench Permissions</a></li>
-<li><a href="../../permissions/mspider.md">Service Mesh Permissions</a></li>
-<li><a href="../../permissions/mcamel.md">Middleware permissions</a></li>
-<li><a href="../../permissions/skoala.md">Microservice Engine Permissions</a></li>
 <li><a href="../../../kpanda/permissions/permission-brief.md">Container Management Permissions</a></li>
 </ul>
 <p><a class="footnote-backref" href="#fnref:1" title="Jump back to footnote 1 in the text">↩</a></p>

en/admin/ghippo/workspace/wsbind-permission.html

@@ -574,7 +574,7 @@ <h2 id="binding-to-workspace">Binding to Workspace<a class="headerlink" href="#b
  John can bind the specified cluster to his own workspace by using the <strong>Bind Workspace</strong> button.</p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>John can only bind clusters or namespaces to a specific workspace in the <a href="../../../kpanda/intro/index.md">Container Management module</a>, and cannot perform this operation in the Global Management module.</p>
+<p>John can only bind clusters or namespaces to a specific workspace in the Container Management module, and cannot perform this operation in the Global Management module.</p>
 </div>
 <p><img alt="cluster banding" src="../images/wsbind4.png"/></p>
 <p>To bind a namespace to a workspace, you must have at least Workspace Admin and Cluster Admin permissions.</p>

en/admin/host/usehost.html

@@ -283,7 +283,7 @@ <h2 id="steps-to-follow">Steps to Follow<a class="headerlink" href="#steps-to-fo
 <ol>
 <li>Log in to the AI platform as an administrator.</li>
 <li>
-<p>Navigate to <strong>Container Management</strong> -&gt; <strong>Container Network</strong> -&gt; <strong>Services</strong>, click on the service name to enter the service details page, and click <strong>Update</strong> at the top right corner.</p>
+<p>Navigate to <strong>Container Management</strong> -&gt; <strong>Container Network</strong> -&gt; <strong>Services</strong>, click the service name to enter the service details page, and click <strong>Update</strong> at the top right corner.</p>
 <p><img alt="service" src="../images/usehost01.png"/></p>
 </li>
 <li>

en/admin/insight/best-practice/debug-log.html

@@ -654,15 +654,15 @@ <h2 id="plugin-description">Plugin Description<a class="headerlink" href="#plugi
 <tbody>
 <tr>
 <td>es.kube.kubeevent.syslog</td>
-<td>Write Kubernetes audit logs, event logs, and syslog logs to <a href="../../middleware/elasticsearch/intro/index.md">ElasticSearch cluster</a></td>
+<td>Write Kubernetes audit logs, event logs, and syslog logs to ElasticSearch cluster</td>
 </tr>
 <tr>
 <td>forward.audit_log</td>
 <td>Send Kubernetes audit logs and <a href="../../ghippo/audit/audit-log.html">global management audit logs</a> to <strong>Global Management</strong></td>
 </tr>
 <tr>
 <td>es.skoala</td>
-<td>Write <a href="../../skoala/gateway/logs/reqlog.md">request logs</a> and <a href="../../skoala/gateway/logs/inslog.md">instance logs</a> of microservice gateway to ElasticSearch cluster</td>
+<td>Write request logs and instance logs of microservice gateway to ElasticSearch cluster</td>
 </tr>
 </tbody>
 </table>

en/admin/insight/best-practice/debug-trace.html

@@ -606,12 +606,12 @@ <h2 id="block-introduction">Block Introduction<a class="headerlink" href="#block
 <p><img alt="trace" src="https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/insight/images/insighttrace04.png"/></p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
-<p>The <strong>opentelemetry collector</strong> in the <strong>Global Management Cluster</strong> is also responsible for sending audit logs of all worker clusters' <a href="../../ghippo/intro/index.md">global management module</a> and Kubernetes audit logs (not collected by default) to the <strong>audit server</strong> component of the global management module.</p>
+<p>The <strong>opentelemetry collector</strong> in the <strong>Global Management Cluster</strong> is also responsible for sending audit logs of all worker clusters' global management module and Kubernetes audit logs (not collected by default) to the <strong>audit server</strong> component of the global management module.</p>
 </div>
 </li>
 <li>
 <p><strong>global jaeger collector</strong></p>
-<p>Display the <strong>jaeger collector</strong> in the <strong>Global Management Cluster</strong> receiving data from the <strong>otel collector</strong> in the <strong>Global Management Cluster</strong> and sending trace data to the <a href="../../middleware/elasticsearch/intro/index.md">ElasticSearch cluster</a>.</p>
+<p>Display the <strong>jaeger collector</strong> in the <strong>Global Management Cluster</strong> receiving data from the <strong>otel collector</strong> in the <strong>Global Management Cluster</strong> and sending trace data to the ElasticSearch cluster.</p>
 </li>
 </ol>
 </article>

en/admin/k8s/add-node.html

@@ -625,7 +625,7 @@ <h2 id="steps-to-add-nodes">Steps to Add Nodes<a class="headerlink" href="#steps
 <ol>
 <li>Log in to the AI platform as an <strong>administrator</strong>.</li>
 <li>
-<p>Navigate to <strong>Container Management</strong> -&gt; <strong>Clusters</strong>, and click on the name of the target cluster.</p>
+<p>Navigate to <strong>Container Management</strong> -&gt; <strong>Clusters</strong>, and click the name of the target cluster.</p>
 <p><img alt="clusters" src="../images/remove01.png"/></p>
 </li>
 <li>

en/admin/k8s/create-k8s.html

@@ -326,7 +326,7 @@ <h2 id="steps-to-create-the-cluster">Steps to Create the Cluster<a class="header
 <p><img alt="done" src="../images/k8s08.png"/></p>
 </li>
 <li>
-<p>In the cluster list, find the newly created cluster, click on the cluster name, navigate to <strong>Helm Apps</strong> -&gt; <strong>Helm Charts</strong>, and search for <code>metax-gpu-extensions</code> in the search box, then click the card.</p>
+<p>In the cluster list, find the newly created cluster, click the cluster name, navigate to <strong>Helm Apps</strong> -&gt; <strong>Helm Charts</strong>, and search for <code>metax-gpu-extensions</code> in the search box, then click the card.</p>
 <p><img alt="cluster" src="../images/k8s09.png"/></p>
 <p><img alt="helm" src="../images/k8s10.png"/></p>
 </li>