forked from docs/doc-exports
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com> Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com> Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
18 lines
2.8 KiB
HTML
18 lines
2.8 KiB
HTML
<a name="ucs_01_0099"></a><a name="ucs_01_0099"></a>
|
|
|
|
<h1 class="topictitle1">Overview</h1>
|
|
<div id="body0000001269224174"><p id="ucs_01_0099__p8060118">The UCS console allows you to manage each cluster on each cluster console.</p>
|
|
<ul id="ucs_01_0099__ul025542818445"><li id="ucs_01_0099__li12551928204410">For OTC clusters (CCE standard and Turbo clusters), the operations on the cluster console of UCS are the same as those on the cluster console of CCE. For details about CCE cluster management, see <span id="ucs_01_0099__ph89219317319"><a href="https://docs.otc.t-systems.com/cloud-container-engine/umn/clusters/cluster_overview.html#" target="_blank" rel="noopener noreferrer">CCE User Guide</a>.</span></li><li id="ucs_01_0099__li1425616288442">For attached clusters, the cluster console allows you to manage basic Kubernetes resources, such as nodes, workloads, Services and ingresses, container storage, ConfigMaps and secrets, and namespaces.<div class="notice" id="ucs_01_0099__note111561442193219"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="ucs_01_0099__en-us_topic_0000001237059247_p15991916183218">For attached clusters, you need to log in to the UCS console with a <strong id="ucs_01_0099__b1713751172211"></strong><strong id="ucs_01_0099__b115198579259">OTC account</strong> or as a user who has the <strong id="ucs_01_0099__b14719152634515">UCS FullAccess</strong> permissions to add permissions on the <strong id="ucs_01_0099__b19878155565614">Permissions</strong> page.</p>
|
|
</div></div>
|
|
</li></ul>
|
|
<div class="section" id="ucs_01_0099__section6571155915362"><h4 class="sectiontitle">Accessing the Cluster Console</h4><p id="ucs_01_0099__p78871872379">The method for accessing the cluster console varies according to whether a cluster has been added to a fleet. The details are as follows:</p>
|
|
<ul id="ucs_01_0099__ul7462117133817"><li id="ucs_01_0099__li4462157163814">Cluster in fleet: On the <span class="uicontrol" id="ucs_01_0099__en-us_topic_0157280894_uicontrol79506398445"><b>Fleets</b></span> page, click the <strong id="ucs_01_0099__b934905032411">Fleets</strong> tab and click the name of the target fleet. In the navigation pane, choose <span class="uicontrol" id="ucs_01_0099__uicontrol182671407405"><b>Container Clusters</b></span>. Then, click the cluster name to access the cluster console.</li><li id="ucs_01_0099__li17243191218383">Clusters not in fleet: Switch to the <strong id="ucs_01_0099__b196620282261">Clusters Not in Fleet</strong> tab, locate the cluster that is not added to the fleet, and click the cluster name to access the cluster console.</li></ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="ucs_01_0007.html">Single-Cluster Management</a></div>
|
|
</div>
|
|
</div>
|
|
|