vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity

ASM UMN update 20241203 version

Browse Source 
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
This commit is contained in:
Dong, Qiu Jian 2024-12-05 07:28:25 +00:00 committed by zuul
parent ca9b774f3d
commit e0c340133f
13 changed files with 136 additions and 113 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/asm/umn/ALL_META.TXT.json
View File

@ -489,8 +489,8 @@
"githuburl":"" "githuburl":""
}, },
{ {
"uri":"asm_01_0084.html", "uri":"asm_01_0020.html",
"node_id":"asm_01_0084.xml", "node_id":"asm_01_0020.xml",
"product_code":"asm", "product_code":"asm",
"code":"28", "code":"28",
"des":"ASM allows you to create a Basic service mesh for commercial use.A CCE cluster is available.ASM depends on the domain name resolution of CoreDNS. Before creating a servic", "des":"ASM allows you to create a Basic service mesh for commercial use.A CCE cluster is available.ASM depends on the domain name resolution of CoreDNS. Before creating a servic",
@ -655,7 +655,7 @@
"node_id":"asm_01_0063.xml", "node_id":"asm_01_0063.xml",
"product_code":"asm", "product_code":"asm",
"code":"37", "code":"37",
"des":"An istio-proxy container must exist in all pods of a Service. Otherwise, this item is abnormal.If no, go to 2.If yes, go to 3.You can inject sidecars for pods of all work", "des":"An istio-proxy container must exist in all pods of a Service. Otherwise, this item is abnormal.If the sidecar is not injected into the namespace, go to 2.If the sidecar h",
"doc_type":"usermanual", "doc_type":"usermanual",
"kw":"All Pods Have Sidecars Injected,Manual Fixing Items,User Guide", "kw":"All Pods Have Sidecars Injected,Manual Fixing Items,User Guide",
"search_title":"", "search_title":"",
@ -907,7 +907,7 @@
"node_id":"asm_01_0041.xml", "node_id":"asm_01_0041.xml",
"product_code":"asm", "product_code":"asm",
"code":"51", "code":"51",
"des":"On the Sidecar Management page, you can view information about all workloads injected with sidecars, perform sidecar injection, and configure sidecar resource limits.You ", "des":"On the Sidecar Management tab, you can view information about all workloads injected with sidecars, inject sidecars, and configure sidecar resource limits.You can view th",
"doc_type":"usermanual", "doc_type":"usermanual",
"kw":"Sidecar Management,Mesh Configuration,User Guide", "kw":"Sidecar Management,Mesh Configuration,User Guide",
"search_title":"", "search_title":"",
@ -997,7 +997,7 @@
"node_id":"asm_01_0124.xml", "node_id":"asm_01_0124.xml",
"product_code":"asm", "product_code":"asm",
"code":"56", "code":"56",
"des":"Istio 1.18 is supported.CCE Turbo clusters v1.25, v1.27, and v1.28 are supported.CCE clusters v1.25, v1.27, and v1.28 are supported.Kubernetes Gateway API is supported.Fo", "des":"Istio 1.18 is supported.CCE Turbo clusters v1.25, v1.27, v1.28, v1.29, and v1.30 are supported.CCE clusters v1.25, v1.27, v1.28, v1.29, and v1.30 are supported.Kubernetes",
"doc_type":"usermanual", "doc_type":"usermanual",
"kw":"Features in v1.18,Upgrades,User Guide", "kw":"Features in v1.18,Upgrades,User Guide",
"search_title":"", "search_title":"",

8
docs/asm/umn/CLASS.TXT.json
View File

@ -246,7 +246,7 @@
"desc":"ASM allows you to create a Basic service mesh for commercial use.A CCE cluster is available.ASM depends on the domain name resolution of CoreDNS. Before creating a servic", "desc":"ASM allows you to create a Basic service mesh for commercial use.A CCE cluster is available.ASM depends on the domain name resolution of CoreDNS. Before creating a servic",
"product_code":"asm", "product_code":"asm",
"title":"Creating a Service Mesh", "title":"Creating a Service Mesh",
"uri":"asm_01_0084.html", "uri":"asm_01_0020.html",
"doc_type":"usermanual", "doc_type":"usermanual",
"p_code":"27", "p_code":"27",
"code":"28" "code":"28"
@ -324,7 +324,7 @@
"code":"36" "code":"36"
}, },
{ {
"desc":"An istio-proxy container must exist in all pods of a Service. Otherwise, this item is abnormal.If no, go to 2.If yes, go to 3.You can inject sidecars for pods of all work", "desc":"An istio-proxy container must exist in all pods of a Service. Otherwise, this item is abnormal.If the sidecar is not injected into the namespace, go to 2.If the sidecar h",
"product_code":"asm", "product_code":"asm",
"title":"All Pods Have Sidecars Injected", "title":"All Pods Have Sidecars Injected",
"uri":"asm_01_0063.html", "uri":"asm_01_0063.html",
@ -450,7 +450,7 @@
"code":"50" "code":"50"
}, },
{ {
"desc":"On the Sidecar Management page, you can view information about all workloads injected with sidecars, perform sidecar injection, and configure sidecar resource limits.You ", "desc":"On the Sidecar Management tab, you can view information about all workloads injected with sidecars, inject sidecars, and configure sidecar resource limits.You can view th",
"product_code":"asm", "product_code":"asm",
"title":"Sidecar Management", "title":"Sidecar Management",
"uri":"asm_01_0041.html", "uri":"asm_01_0041.html",
@ -495,7 +495,7 @@
"code":"55" "code":"55"
}, },
{ {
"desc":"Istio 1.18 is supported.CCE Turbo clusters v1.25, v1.27, and v1.28 are supported.CCE clusters v1.25, v1.27, and v1.28 are supported.Kubernetes Gateway API is supported.Fo", "desc":"Istio 1.18 is supported.CCE Turbo clusters v1.25, v1.27, v1.28, v1.29, and v1.30 are supported.CCE clusters v1.25, v1.27, v1.28, v1.29, and v1.30 are supported.Kubernetes",
"product_code":"asm", "product_code":"asm",
"title":"Features in v1.18", "title":"Features in v1.18",
"uri":"asm_01_0124.html", "uri":"asm_01_0124.html",

2
docs/asm/umn/asm_01_0017.html
View File

@ -4,7 +4,7 @@
<div id="body0000001209619746"></div> <div id="body0000001209619746"></div>
<div> <div>
<ul class="ullinks"> <ul class="ullinks">
<li class="ulchildlink"><strong><a href="asm_01_0084.html">Creating a Service Mesh</a></strong><br> <li class="ulchildlink"><strong><a href="asm_01_0020.html">Creating a Service Mesh</a></strong><br>
</li> </li>
</ul> </ul>

84
docs/asm/umn/asm_01_0020.html Normal file
View File

@ -0,0 +1,84 @@
<a name="asm_01_0020"></a><a name="asm_01_0020"></a>
<h1 class="topictitle1">Creating a Service Mesh</h1>
<div id="body8662426"><p id="asm_01_0020__en-us_topic_0000001542706401_p7705103811473">ASM allows you to create a Basic service mesh for commercial use.</p>
<div class="section" id="asm_01_0020__en-us_topic_0000001542706401_section033812246196"><h4 class="sectiontitle">Prerequisites</h4><p id="asm_01_0020__en-us_topic_0000001542706401_p43381724171910">A CCE cluster is available.</p>
</div>
<div class="section" id="asm_01_0020__en-us_topic_0000001542706401_section1486314595204"><h4 class="sectiontitle">Constraints</h4><ul id="asm_01_0020__en-us_topic_0000001542706401_ul186475910202"><li id="asm_01_0020__en-us_topic_0000001542706401_li1786417596203">ASM depends on the domain name resolution of CoreDNS. Before creating a service mesh for a cluster, ensure that the cluster has required resources and CoreDNS is running normally.</li><li id="asm_01_0020__li133817361244">Istio components v1.13 and v1.15 cannot run on nodes running CentOS or EulerOS 2.5. When creating a service mesh, do not specify these types of nodes as master nodes.</li></ul>
</div>
<div class="section" id="asm_01_0020__en-us_topic_0000001542706401_section201371027102715"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0020__en-us_topic_0000001542706401_ol1158918434276"><li id="asm_01_0020__en-us_topic_0000001542706401_li184614499427"><span>Log in to the ASM console.</span></li><li id="asm_01_0020__en-us_topic_0000001542706401_li125894431271"><span>Click Create Mesh in the upper right corner.</span></li><li id="asm_01_0020__en-us_topic_0000001542706401_li135891543162714"><span>Configure the following parameters.</span><p><ul id="asm_01_0020__en-us_topic_0000001542706401_ul75901043202711"><li id="asm_01_0020__en-us_topic_0000001542706401_li2092711501216"><strong id="asm_01_0020__en-us_topic_0000001542706401_b1094850142211">Mesh Edition</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p4479132261213">Only service meshes of the Basic edition are supported for commercial use.</p>
</li><li id="asm_01_0020__en-us_topic_0000001542706401_li35901243162718"><strong id="asm_01_0020__b147201102">Mesh Name</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p19590743152711">Enter a service mesh name, which consists of 4 to 64 characters. It must start with a lowercase letter and cannot end with a hyphen (-). Only lowercase letters, digits, and hyphens (-) are allowed.</p>
<p id="asm_01_0020__en-us_topic_0000001542706401_p11590144316275">Service mesh names under the same account must be unique and cannot be modified after creation.</p>
</li><li id="asm_01_0020__en-us_topic_0000001542706401_li3590184362716"><strong id="asm_01_0020__b1937452824">Istio Version</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p19590144310274">Select the Istio version supported by the service mesh.</p>
</li><li id="asm_01_0020__li20991123625914"><strong id="asm_01_0020__b54661518132116">Enable IPv6</strong><p id="asm_01_0020__p04381549215">Conditions for enabling IPv4/IPv6 dual stack for a service mesh</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="asm_01_0020__table11439754142117" frame="border" border="1" rules="all"><thead align="left"><tr id="asm_01_0020__row1743955417212"><th align="left" class="cellrowborder" valign="top" width="12.379999999999999%" id="mcps1.3.4.2.3.2.1.4.3.1.6.1.1"><p id="asm_01_0020__p1643985417218">Service Mesh Edition</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="14.91%" id="mcps1.3.4.2.3.2.1.4.3.1.6.1.2"><p id="asm_01_0020__p8439135413212">Istio Version</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="15.260000000000002%" id="mcps1.3.4.2.3.2.1.4.3.1.6.1.3"><p id="asm_01_0020__p1443995417219">Cluster Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="20.4%" id="mcps1.3.4.2.3.2.1.4.3.1.6.1.4"><p id="asm_01_0020__p14394543213">Cluster Network Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="37.05%" id="mcps1.3.4.2.3.2.1.4.3.1.6.1.5"><p id="asm_01_0020__p6439195402115">Remarks</p>
</th>
</tr>
</thead>
<tbody><tr id="asm_01_0020__row184391354172116"><td class="cellrowborder" valign="top" width="12.379999999999999%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.1 "><p id="asm_01_0020__p2043975418214">Basic edition</p>
</td>
<td class="cellrowborder" valign="top" width="14.91%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.2 "><p id="asm_01_0020__p643945413219">1.18 or later</p>
</td>
<td class="cellrowborder" valign="top" width="15.260000000000002%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.3 "><p id="asm_01_0020__p94391954112116">CCE Turbo clusters</p>
</td>
<td class="cellrowborder" valign="top" width="20.4%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.4 "><p id="asm_01_0020__p843985414211">Cloud native network 2.0</p>
</td>
<td class="cellrowborder" valign="top" width="37.05%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.5 "><p id="asm_01_0020__p17439135413211">To enable IPv6.</p>
</td>
</tr>
</tbody>
</table>
</div>
<p id="asm_01_0020__p124428207334">For details, see <a href="asm_bestpractice_1009.html">How Do I Create a Service Mesh with IPv4/IPv6 Dual Stack Enabled</a></p>
<div class="note" id="asm_01_0020__note18440654152111"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="asm_01_0020__ul1744075432120"><li id="asm_01_0020__li1744055413210"><strong id="asm_01_0020__b11396256101815">Enable IPv6</strong> is only available in Basic service meshes based on Istio 1.18 or later.</li><li id="asm_01_0020__li194404548216">IPv4/IPv6 dual stack cannot be enabled for a service mesh whose Istio version is upgraded to 1.18 or later.</li></ul>
<ul id="asm_01_0020__ul144085482119"><li id="asm_01_0020__li1344010549212">IPv4/IPv6 dual stack cannot be disabled once it is enabled for a service mesh. IPv4/IPv6 dual stack cannot be enabled for an existing service mesh.</li></ul>
</div></div>
</li><li id="asm_01_0020__en-us_topic_0000001542706401_li4590154315271"><strong id="asm_01_0020__b2100410425">Cluster</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p4590184313278">Select the cluster from the cluster list or enter the cluster name in the upper right corner of the list to search for it. You can only select the clusters whose versions are supported by the current service mesh version.</p>
</li><li id="asm_01_0020__en-us_topic_0000001542706401_li159044311277"><strong id="asm_01_0020__b973752981">Mesh Control Plane Node</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p125902437272">The control plane components of the Basic service mesh are installed in the user cluster. Therefore, you need to select a node for installing the control plane. If HA is required, you can select two or more nodes from different AZs.</p>
<p id="asm_01_0020__en-us_topic_0000001542706401_p1959024392713">A selected node will be labeled with <strong id="asm_01_0020__b12113195612363">istio:master</strong>, and the components will be scheduled to that node.</p>
</li><li id="asm_01_0020__li17225629125"><strong id="asm_01_0020__b182161818152520">Observability Configuration</strong><ul id="asm_01_0020__ul162251921123"><li id="asm_01_0020__li1233211216319"><strong id="asm_01_0020__b1115002839">Application Metrics</strong><p id="asm_01_0020__p93321821123112">If this option is enabled, you can specify service access metrics, application topologies, and service health and SLO definitions in the service mesh.</p>
</li><li id="asm_01_0020__li1522512214127"><strong id="asm_01_0020__b1443315218391">Tracing</strong><p id="asm_01_0020__p3225124129">- <strong id="asm_01_0020__b1649171110292">Sampling Rate</strong>: Number of requests generated by the tracing service/Total number of requests</p>
<p id="asm_01_0020__p722519210123">- <strong id="asm_01_0020__b13853258294">Version</strong>: tracing service. If you select <strong id="asm_01_0020__b1028517591813">Third-party Jaeger/Zipkin service</strong>, you need to set <strong id="asm_01_0020__b613018597425">Service Address</strong> and <strong id="asm_01_0020__b665636154317">Service Port</strong>, which indicate the address and port number used by the third-party tracing service to receive requests.</p>
<div class="note" id="asm_01_0020__note122518211219"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="asm_01_0020__ul1522613251216"><li id="asm_01_0020__li112261223127">Only Istio 1.15 or later support the third-party tracing service.</li><li id="asm_01_0020__li142761222131512">If you want to use the third-party Jaeger or Zipkin service, install it first. Then, obtain the service address.</li><li id="asm_01_0020__li1622612111211">The default service ports of Jaeger and Zipkin are both 9411. If you customize the service port during Jaeger or Zipkin installation, replace <strong id="asm_01_0020__b3675134710313">Service Port</strong> with the actual value.</li></ul>
</div></div>
</li></ul>
</li></ul>
</p></li><li id="asm_01_0020__en-us_topic_0000001542706401_li185901043112713"><span>(Optional) Configure advanced settings.</span><p><ul id="asm_01_0020__en-us_topic_0000001542706401_ul195914431277"><li id="asm_01_0020__en-us_topic_0000001542706401_li105911243172720"><strong id="asm_01_0020__b808612298">Namespace Injection Settings</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p0591154316270">Select a namespace and label it with <strong id="asm_01_0020__b1742517548222">istio-injection=enabled</strong>. After being restarted, all pods in the namespace will be automatically injected with an istio-proxy sidecar.</p>
<p id="asm_01_0020__en-us_topic_0000001542706401_p1459184332714">If you do not configure namespace injection, you can inject a sidecar on the <strong id="asm_01_0020__b1960806132112">Sidecar Management</strong> tab (<strong id="asm_01_0020__b86087612111">Mesh Configuration</strong> &gt; <strong id="asm_01_0020__b196087611215">Sidecar Management</strong>) after the service mesh is created. For details, see <a href="asm_01_0041.html#asm_01_0041__section65931513505">Injecting a Sidecar</a>.</p>
</li><li id="asm_01_0020__en-us_topic_0000001542706401_li1059184310276"><strong id="asm_01_0020__b963350775">Restart Existing Services</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p12591144362715"><span><img id="asm_01_0020__image879324619490" src="en-us_image_0000001920032153.png"></span>: Pods of the existing services in the namespace will be restarted, which will temporarily interrupt your services. The <strong id="asm_01_0020__b658216428">istio-proxy</strong> sidecar is automatically injected into the pods of the existing services.</p>
<p id="asm_01_0020__en-us_topic_0000001542706401_p195911343162718"><span><img id="asm_01_0020__en-us_topic_0000001542706401_image1736110311031" src="en-us_image_0000001494249996.png"></span>: The <strong id="asm_01_0020__b166037221819">istio-proxy</strong> sidecar cannot be automatically injected into the pods of the existing services. You need to manually restart the workloads on the CCE console to inject the sidecar.</p>
</li><li id="asm_01_0020__li103761117176"><strong id="asm_01_0020__b161488533415">Traffic Interception Settings</strong><div class="note" id="asm_01_0020__note9376117978"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0020__p2376181712720">By default, sidecars intercept all inbound and outbound traffic of pods. You can modify the default traffic rules in <strong id="asm_01_0020__b134331479345">Traffic Interception Settings</strong>.</p>
</div></div>
<p id="asm_01_0020__p93763174718"><strong id="asm_01_0020__b9810181314341">Inbound Ports</strong>: Inbound ports separated by commas (,). You can use this field to specify the ports that will be included or excluded for inbound traffic redirection.</p>
<ul id="asm_01_0020__ul1376817679"><li id="asm_01_0020__li33768171718"><strong id="asm_01_0020__b16992015173412">Include only specified ports</strong> means that the traffic to services in a service mesh over specified ports will be redirected to the sidecar.</li></ul>
<ul id="asm_01_0020__ul73766176715"><li id="asm_01_0020__li1137612175714"><strong id="asm_01_0020__b15386151833412">Exclude only specified ports</strong> means that the traffic to services in a service mesh over the ports except the specified ports will be redirected to the sidecar.</li></ul>
<p id="asm_01_0020__p437612171973"><strong id="asm_01_0020__b155051822203412">Outbound Ports</strong>: Outbound ports separated by commas (,). You can use this field to specify the ports that will be included or excluded for outbound traffic redirection.</p>
<ul id="asm_01_0020__ul10376151714710"><li id="asm_01_0020__li16376121711719"><strong id="asm_01_0020__b10871024123417">Include only specified ports</strong> means that the traffic from services in a service mesh over specified ports will be redirected to the sidecar.</li></ul>
<ul id="asm_01_0020__ul337611714716"><li id="asm_01_0020__li1337717171578"><strong id="asm_01_0020__b67131127173417">Exclude only specified ports</strong> means that the traffic from services in a service mesh over the ports except the specified ports will be redirected to the sidecar.</li></ul>
<p id="asm_01_0020__p11377181717712"><strong id="asm_01_0020__b20653518442">Outbound IP Ranges</strong>: IP address ranges separated by commas (,) in CIDR format. You can use this field to specify the IP ranges that will be included or excluded for outbound traffic redirection.</p>
<ul id="asm_01_0020__ul1337716172078"><li id="asm_01_0020__li1377417579"><strong id="asm_01_0020__b39502030153411">Include only specified IP ranges</strong> means that the traffic from specified IP ranges will be redirected to the sidecar.</li></ul>
<ul id="asm_01_0020__ul14377181711717"><li id="asm_01_0020__li3377171710719"><strong id="asm_01_0020__b393303213347">Exclude only specified IP ranges</strong> means that the traffic from IP ranges except the specified IP ranges will be redirected to the sidecar.</li></ul>
</li><li id="asm_01_0020__li1611138125316"><strong id="asm_01_0020__b1576740032">Resource Tags</strong><p id="asm_01_0020__p1711128135317">Enter the tag key and tag value. A maximum of 20 tags can be added.</p>
</li></ul>
</p></li><li id="asm_01_0020__en-us_topic_0000001542706401_li859154318271"><span>Review the service mesh configuration in <strong id="asm_01_0020__b151099494">Configuration List</strong> on the right of the page and click <strong id="asm_01_0020__b441494675">Submit</strong>.</span><p><p id="asm_01_0020__en-us_topic_0000001542706401_p13591174382714">It takes about 1 to 3 minutes to create a service mesh. If the service mesh status changes from <strong id="asm_01_0020__b567440244">Installing</strong> to <strong id="asm_01_0020__b17683781">Running</strong>, the service mesh is successfully created.</p>
<div class="note" id="asm_01_0020__en-us_topic_0000001542706401_note14591184342712"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0020__en-us_topic_0000001542706401_p1459119432275">When the service mesh is enabled, the following operations are performed:</p>
<ul id="asm_01_0020__en-us_topic_0000001542706401_ul859134311276"><li id="asm_01_0020__en-us_topic_0000001542706401_li195911043152719">Helm orchestrates the application into a Release as the resource of the service mesh control plane.</li></ul>
</div></div>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0017.html">Creating a Service Mesh</a></div>
</div>
</div>

14
docs/asm/umn/asm_01_0041.html
View File

@ -1,10 +1,16 @@
<a name="asm_01_0041"></a><a name="asm_01_0041"></a> <a name="asm_01_0041"></a><a name="asm_01_0041"></a>
<h1 class="topictitle1">Sidecar Management</h1> <h1 class="topictitle1">Sidecar Management</h1>
<div id="body0000001083107046"><p id="asm_01_0041__p84481631152714">On the <strong id="asm_01_0041__b712243010246">Sidecar Management</strong> page, you can view information about all workloads injected with sidecars, perform sidecar injection, and configure sidecar resource limits.</p> <div id="body0000001083107046"><p id="asm_01_0041__p84481631152714">On the <strong id="asm_01_0041__b712243010246">Sidecar Management</strong> tab, you can view information about all workloads injected with sidecars, inject sidecars, and configure sidecar resource limits.</p>
<div class="section" id="asm_01_0041__section65931513505"><a name="asm_01_0041__section65931513505"></a><a name="section65931513505"></a><h4 class="sectiontitle">Injecting a Sidecar</h4><p id="asm_01_0041__p1820212632111">You can view the namespace and cluster to which the injected sidecar belongs. If no sidecar has been injected or you need to inject sidecar for more namespaces, perform the following operations:</p> <div class="section" id="asm_01_0041__section65931513505"><a name="asm_01_0041__section65931513505"></a><a name="section65931513505"></a><h4 class="sectiontitle">Injecting a Sidecar</h4><p id="asm_01_0041__p1820212632111">You can view the namespace and cluster that the injected sidecar belongs to. If no sidecar has been injected or you need to inject sidecars for more namespaces, perform the following operations:</p>
<ol id="asm_01_0041__ol13641175216560"><li id="asm_01_0041__li683575385614"><span>Log in to the ASM console and click the name of the target service mesh to go to its details page.</span></li><li id="asm_01_0041__li987742619292"><span>In the navigation pane, choose <strong id="asm_01_0041__b23024965310246">Mesh Configuration</strong>. Then click the <strong id="asm_01_0041__b79698741510246">Sidecar Management</strong> tab.</span></li><li id="asm_01_0041__li122863200343"><span>Click <strong id="asm_01_0041__b212025475310246">Sidecar Management</strong>, select a namespace, determine whether to restart the existing services, and click <strong id="asm_01_0041__b163426572510246">OK</strong>.</span><p><ul id="asm_01_0041__ul1213414267113"><li id="asm_01_0041__li151346264113"><strong id="asm_01_0041__b25961104110246">Namespace</strong>: Select one or more namespaces. The system labels the namespaces with <strong id="asm_01_0041__b86877081210246">istio-injection=enabled</strong>.</li><li id="asm_01_0041__li1283731219"><strong id="asm_01_0041__b176898850910246">Restart Existing Services</strong><p id="asm_01_0041__p16974516217"><span><img id="asm_01_0041__image1251935012150" src="en-us_image_0000001930216052.png"></span>: Pods of the existing services in the namespace will be restarted, which will temporarily interrupt your services. The <strong id="asm_01_0041__b35079130010246">istio-proxy</strong> sidecar is automatically injected into the pods of the existing services.</p> <ol id="asm_01_0041__ol13641175216560"><li id="asm_01_0041__li683575385614"><span>Log in to the ASM console and click the name of the target service mesh to go to its details page.</span></li><li id="asm_01_0041__li987742619292"><span>In the navigation pane, choose <strong id="asm_01_0041__b23024965310246">Mesh Configuration</strong>. Then, click the <strong id="asm_01_0041__b79698741510246">Sidecar Management</strong> tab.</span></li><li id="asm_01_0041__li122863200343"><span>Click <strong id="asm_01_0041__b212025475310246">Sidecar Management</strong>, select a namespace, determine whether enable <strong id="asm_01_0041__b34328513417">Restart Existing Services</strong>, and click <strong id="asm_01_0041__b163426572510246">OK</strong>.</span><p><p id="asm_01_0041__p5867153384619">Parameter description:</p>
<p id="asm_01_0041__p45731657222"><span><img id="asm_01_0041__image1736110311031" src="en-us_image_0000001256463368.png"></span>: The <strong id="asm_01_0041__b19208133718302">istio-proxy</strong> sidecar cannot be automatically injected into the pods of the existing services. You need to manually restart the workloads on the CCE console to inject the sidecar. Whether to restart existing services affects only existing services. If the namespaces are labeled with <strong id="asm_01_0041__b1545117533412">istio-injection=enabled</strong>, sidecars will be automatically injected into new pods.</p> <ul id="asm_01_0041__ul1213414267113"><li id="asm_01_0041__li151346264113"><strong id="asm_01_0041__b162639501293">Namespace</strong>: Select one or more namespaces. The system adds labels for namespaces based on Istio versions.<ul id="asm_01_0041__ul715833017173"><li id="asm_01_0041__li115810307178"><strong id="asm_01_0041__b93355351461">istio-injection=enabled</strong> can be used in Istio 1.13.9-r3 and earlier versions, as well as Istio 1.15.5-r2 and earlier versions.</li></ul>
<ul id="asm_01_0041__ul196772518187"><li id="asm_01_0041__li6677853189"><strong id="asm_01_0041__b5658241104719">istio.io/rev=&lt;revision&gt;</strong> can be used in Istio later than 1.13.9-r3, Istio later than 1.15.5-r2, and all Istio 1.18 versions.</li></ul>
</li><li id="asm_01_0041__li1283731219"><strong id="asm_01_0041__b176898850910246">Restart Existing Services</strong><p id="asm_01_0041__p16974516217"><span><img id="asm_01_0041__image1251935012150" src="en-us_image_0000001930216052.png"></span>: Enabling <strong id="asm_01_0041__b178031814163717">Restart Existing Services</strong> will restart the associated pods and temporarily interrupt your services. New pods will have istio-proxy sidecars automatically injected.</p>
<ul id="asm_01_0041__ul1893924912361"><li id="asm_01_0041__li149404492367">If you select a new namespace, an automatic injection label is added. After all pods running the Deployment in that namespace are restarted, the istio-proxy sidecars will be automatically injected into new pods.</li></ul>
<ul id="asm_01_0041__ul330205410366"><li id="asm_01_0041__li5302135413618">If you deselect a namespace, the automatic injection label is deleted. After all pods running the Deployment in that namespace are restarted, new pods do not have istio-proxy sidecars.</li></ul>
<ul id="asm_01_0041__ul157408585364"><li id="asm_01_0041__li074055833619">If there are pods that are not injected with sidecars in selected namespaces, all pods running the Deployment will be restarted to inject sidecars. If all pods have sidecars injected, the pods will not be restarted.</li></ul>
<p id="asm_01_0041__p45731657222"><span><img id="asm_01_0041__image1297291313419" src="en-us_image_0000001256463368.png"></span>: When you do not enable <strong id="asm_01_0041__b198411563510">Restart Existing Services</strong>, the istio-proxy sidecars cannot be automatically injected into the associated pods. You need to manually restart the workload on the CCE console to inject sidecars. This parameter affects only existing services. If the namespaces are labeled with <strong id="asm_01_0041__b1545117533412">istio-injection=enabled</strong>, sidecars will be automatically injected into new pods.</p>
</li><li id="asm_01_0041__li975935132613"><strong id="asm_01_0041__b4935192843517">Traffic Interception Settings</strong><div class="note" id="asm_01_0041__note130182311537"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0041__p5301112325320">By default, sidecars intercept all inbound and outbound traffic of pods. You can modify the default traffic rules in <strong id="asm_01_0041__b15949143017359">Traffic Interception Settings</strong>.</p> </li><li id="asm_01_0041__li975935132613"><strong id="asm_01_0041__b4935192843517">Traffic Interception Settings</strong><div class="note" id="asm_01_0041__note130182311537"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0041__p5301112325320">By default, sidecars intercept all inbound and outbound traffic of pods. You can modify the default traffic rules in <strong id="asm_01_0041__b15949143017359">Traffic Interception Settings</strong>.</p>
</div></div> </div></div>
<p id="asm_01_0041__p10174123175619"><strong id="asm_01_0041__b97421432123511">Inbound Ports</strong>: Inbound ports separated by commas (,). You can use this field to specify the ports that will be included or excluded for inbound traffic redirection.</p> <p id="asm_01_0041__p10174123175619"><strong id="asm_01_0041__b97421432123511">Inbound Ports</strong>: Inbound ports separated by commas (,). You can use this field to specify the ports that will be included or excluded for inbound traffic redirection.</p>

23
docs/asm/umn/asm_01_0063.html
View File

@ -3,13 +3,26 @@
<h1 class="topictitle1">All Pods Have Sidecars Injected</h1> <h1 class="topictitle1">All Pods Have Sidecars Injected</h1>
<div id="body0000001175772865"><div class="section" id="asm_01_0063__section146041745338"><h4 class="sectiontitle">Description</h4><p id="asm_01_0063__p1487717583317">An <strong id="asm_01_0063__b8850152035217">istio-proxy</strong> container must exist in all pods of a Service. Otherwise, this item is abnormal.</p> <div id="body0000001175772865"><div class="section" id="asm_01_0063__section146041745338"><h4 class="sectiontitle">Description</h4><p id="asm_01_0063__p1487717583317">An <strong id="asm_01_0063__b8850152035217">istio-proxy</strong> container must exist in all pods of a Service. Otherwise, this item is abnormal.</p>
</div> </div>
<div class="section" id="asm_01_0063__section1457519694110"><h4 class="sectiontitle">Rectification Guide</h4><ol id="asm_01_0063__ol11865432551"><li id="asm_01_0063__li12186243175513"><span>Log in to the ASM console and click the name of the service mesh that the Service is added to. Choose <strong id="asm_01_0063__b761794971520">Mesh Configuration</strong> in the navigation pane, click the <strong id="asm_01_0063__b861824921513">Sidecar Management</strong> tab, and check whether a sidecar is injected into the namespace that the Service belongs to.</span><p><ul id="asm_01_0063__ul1680513160015"><li id="asm_01_0063__li1680515161008">If no, go to <a href="#asm_01_0063__li1665121115612">2</a>.</li><li id="asm_01_0063__li198192408015">If yes, go to <a href="#asm_01_0063__li127525055610">3</a>.</li></ul> <div class="section" id="asm_01_0063__section1457519694110"><h4 class="sectiontitle">Rectification Guide</h4><ol id="asm_01_0063__ol11865432551"><li id="asm_01_0063__li12186243175513"><span>Log in to the ASM console and click the name of the service mesh that the Service is added to. Choose <strong id="asm_01_0063__b761794971520">Mesh Configuration</strong> in the navigation pane, click the <strong id="asm_01_0063__b861824921513">Sidecar Management</strong> tab, and check whether a sidecar is injected into the namespace that the Service belongs to.</span><p><ul id="asm_01_0063__ul1680513160015"><li id="asm_01_0063__li1680515161008">If the sidecar is not injected into the namespace, go to <a href="#asm_01_0063__li1665121115612">2</a>.</li><li id="asm_01_0063__li198192408015">If the sidecar has been injected into the namespace, go to <a href="#asm_01_0063__li127525055610">3</a>.<p id="asm_01_0063__p1515351917258">Check method:</p>
</p></li><li id="asm_01_0063__li1665121115612"><a name="asm_01_0063__li1665121115612"></a><a name="li1665121115612"></a><span>Inject a sidecar.</span><p><p id="asm_01_0063__p126911222119">You can inject sidecars for pods of all workloads in the namespace. For details, see <a href="asm_01_0041.html#asm_01_0041__section65931513505">Injecting a Sidecar</a>. You can also inject sidecars for a workload as follows:</p> <p id="asm_01_0063__p42381524122517">On the CCE console, click the cluster name to access the cluster console. In the navigation pane, choose <strong id="asm_01_0063__b11801397414">Namespaces</strong>. On the displayed page, locate your namespace and click <strong id="asm_01_0063__b9613112883416">Edit YAML</strong> in the <strong id="asm_01_0063__b15711152403411">Operation</strong> column. If there is the <strong id="asm_01_0063__b175091651103918">istio.io/rev=&lt;revision&gt;</strong> or <strong id="asm_01_0063__b20795258123916">istio-injection=enabled</strong> label, the sidecar has been injected.</p>
<ol type="a" id="asm_01_0063__ol12815202013285"><li id="asm_01_0063__li1581512002813">Label the namespace where the workload is located with <strong id="asm_01_0063__b1443112112588">istio-injection=enabled</strong>.<p id="asm_01_0063__p135581615312"><strong id="asm_01_0063__b1635231118566">kubectl label ns</strong> &lt;namespace&gt; <strong id="asm_01_0063__b44311413135617">istio-injection=enabled</strong></p> <div class="note" id="asm_01_0063__note87391512153111"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="asm_01_0063__ul12328442183114"><li id="asm_01_0063__li832864243112">There must the <strong id="asm_01_0063__b128477083514">istio-injection=enabled</strong> label for Istio 1.13.9-r3 and earlier versions, as well as Istio 1.15.5-r2 and earlier versions. Note that the version numbers are combined by hyphens (-).</li><li id="asm_01_0063__li89671844113111">There must be the <strong id="asm_01_0063__b198671148379">istio.io/rev=&lt;revision&gt;</strong> label for Istio later than 1.13.9-r3, Istio later than 1.15.5-r2, and all Istio 1.18 versions. Note that the version numbers are combined by hyphens (-).<p id="asm_01_0063__p1336942717254"><span><img id="asm_01_0063__image4821824135818" src="en-us_image_0000002086005592.png"></span></p>
</li><li id="asm_01_0063__li2511172882919">Add the <strong id="asm_01_0063__b169051134115811">annotations</strong> field for the workload on the CCE console.<pre class="screen" id="asm_01_0063__screen575018269110"> annotations: </li></ul>
</div></div>
</li></ul>
</p></li><li id="asm_01_0063__li1665121115612"><a name="asm_01_0063__li1665121115612"></a><a name="li1665121115612"></a><span>Inject a sidecar into a workload or inject sidecars into the pods of all workloads in the namespace. For details, see <a href="asm_01_0041.html#asm_01_0041__section65931513505">Injecting a Sidecar</a>.</span><p><p id="asm_01_0063__p126911222119">Injection methods:</p>
<ul id="asm_01_0063__ul142566176620"><li id="asm_01_0063__li1717131013105">To inject sidecars into the pods of all workloads in the namespace, run the following command to add a label to the namespace (the label varies depending on the Istio version):<pre class="screen" id="asm_01_0063__screen1281611095517"><strong id="asm_01_0063__b1181951015558">kubectl label ns</strong> &lt;namespace&gt; istio-injection=enabled</pre>
<p id="asm_01_0063__p19362226185219">Or</p>
<pre class="screen" id="asm_01_0063__screen1788741815554"><strong id="asm_01_0063__b128882181554">kubectl label ns</strong> &lt;namespace&gt; istio.io/rev=&lt;revision&gt;</pre>
<div class="note" id="asm_01_0063__note12977171985010"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><div class="p" id="asm_01_0063__p16180546195012">The system adds labels for namespaces based on Istio versions.<ul id="asm_01_0063__ul4788103410502"><li id="asm_01_0063__li2788734195016"><strong id="asm_01_0063__b1223320133017">istio-injection=enabled</strong> can be used in Istio 1.13.9-r3 and earlier versions, as well as Istio 1.15.5-r2 and earlier versions.</li></ul>
<ul id="asm_01_0063__ul3789103425019"><li id="asm_01_0063__li87899349504"><strong id="asm_01_0063__b19540824143010">istio.io/rev=&lt;revision&gt;</strong> can be used in Istio later than 1.13.9-r3, Istio later than 1.15.5-r2, and all Istio 1.18 versions.</li></ul>
</div>
</div></div>
</li></ul>
<ul id="asm_01_0063__ul77018142713"><li id="asm_01_0063__li168449341119">Injecting a sidecar into a workload<div class="p" id="asm_01_0063__p10496970111"><a name="asm_01_0063__li168449341119"></a><a name="li168449341119"></a>On the CCE console, locate the target workload, choose <strong id="asm_01_0063__b4452123114113">More</strong> &gt; <strong id="asm_01_0063__b109016381012">Edit YAML</strong> in the <strong id="asm_01_0063__b157254481818">Operation</strong> column, and manually add the <strong id="asm_01_0063__b04982581119">annotations</strong> field.<pre class="screen" id="asm_01_0063__screen575018269110"> annotations:
sidecar.istio.io/inject: 'true'</pre> sidecar.istio.io/inject: 'true'</pre>
</div>
<p id="asm_01_0063__p1794791520305"><span><img id="asm_01_0063__image115521522121112" src="en-us_image_0000001394586873.png"></span></p> <p id="asm_01_0063__p1794791520305"><span><img id="asm_01_0063__image115521522121112" src="en-us_image_0000001394586873.png"></span></p>
</li></ol> </li></ul>
<p id="asm_01_0063__p18904104210315">For more details about sidecar injection, see <a href="https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/" target="_blank" rel="noopener noreferrer">Installing the Sidecar</a>.</p> <p id="asm_01_0063__p18904104210315">For more details about sidecar injection, see <a href="https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/" target="_blank" rel="noopener noreferrer">Installing the Sidecar</a>.</p>
</p></li><li id="asm_01_0063__li127525055610"><a name="asm_01_0063__li127525055610"></a><a name="li127525055610"></a><span>If namespace injection is enabled for the cluster but no sidecar is injected into the pod, you need to manually restart the pod on the CCE console as follows:</span><p><p id="asm_01_0063__p6931112013420">On the CCE console, choose <strong id="asm_01_0063__b51514267743241">More</strong> &gt; <strong id="asm_01_0063__b185900250343241">Redeploy</strong> in the <strong id="asm_01_0063__b143167820043241">Operation</strong> column of the target workload.</p> </p></li><li id="asm_01_0063__li127525055610"><a name="asm_01_0063__li127525055610"></a><a name="li127525055610"></a><span>If namespace injection is enabled for the cluster but no sidecar is injected into the pod, you need to manually restart the pod on the CCE console as follows:</span><p><p id="asm_01_0063__p6931112013420">On the CCE console, choose <strong id="asm_01_0063__b51514267743241">More</strong> &gt; <strong id="asm_01_0063__b185900250343241">Redeploy</strong> in the <strong id="asm_01_0063__b143167820043241">Operation</strong> column of the target workload.</p>
</p></li><li id="asm_01_0063__li10713191914412"><span>Check whether the host network mode is configured for the workload as follows:</span><p><p id="asm_01_0063__p31276451075">On the CCE console, choose <strong id="asm_01_0063__b1371751914718">More</strong> &gt; <strong id="asm_01_0063__b15717191914719">Edit YAML</strong> in the <strong id="asm_01_0063__b07176192714">Operation</strong> column of the target workload, and check whether <strong id="asm_01_0063__b1178116582714">spec.template.spec.hostNetwork: true</strong> is configured. If yes, check whether this field can be deleted or set to <strong id="asm_01_0063__b1692120472143">false</strong>. Otherwise, sidecars cannot be injected.</p> </p></li><li id="asm_01_0063__li10713191914412"><span>Check whether the host network mode is configured for the workload as follows:</span><p><p id="asm_01_0063__p31276451075">On the CCE console, choose <strong id="asm_01_0063__b1371751914718">More</strong> &gt; <strong id="asm_01_0063__b15717191914719">Edit YAML</strong> in the <strong id="asm_01_0063__b07176192714">Operation</strong> column of the target workload, and check whether <strong id="asm_01_0063__b1178116582714">spec.template.spec.hostNetwork: true</strong> is configured. If yes, check whether this field can be deleted or set to <strong id="asm_01_0063__b1692120472143">false</strong>. Otherwise, sidecars cannot be injected.</p>

84
docs/asm/umn/asm_01_0084.html
View File

@ -1,84 +0,0 @@
<a name="asm_01_0084"></a><a name="asm_01_0084"></a>
<h1 class="topictitle1">Creating a Service Mesh</h1>
<div id="body8662426"><p id="asm_01_0084__en-us_topic_0000001542706401_p7705103811473">ASM allows you to create a Basic service mesh for commercial use.</p>
<div class="section" id="asm_01_0084__en-us_topic_0000001542706401_section033812246196"><h4 class="sectiontitle">Prerequisites</h4><p id="asm_01_0084__en-us_topic_0000001542706401_p43381724171910">A CCE cluster is available.</p>
</div>
<div class="section" id="asm_01_0084__en-us_topic_0000001542706401_section1486314595204"><h4 class="sectiontitle">Constraints</h4><ul id="asm_01_0084__en-us_topic_0000001542706401_ul186475910202"><li id="asm_01_0084__en-us_topic_0000001542706401_li1786417596203">ASM depends on the domain name resolution of CoreDNS. Before creating a service mesh for a cluster, ensure that the cluster has required resources and CoreDNS is running normally.</li><li id="asm_01_0084__li133817361244">Istio components v1.13 and v1.15 cannot run on nodes running CentOS or EulerOS 2.5. When creating a service mesh, do not specify these types of nodes as master nodes.</li></ul>
</div>
<div class="section" id="asm_01_0084__en-us_topic_0000001542706401_section201371027102715"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0084__en-us_topic_0000001542706401_ol1158918434276"><li id="asm_01_0084__en-us_topic_0000001542706401_li184614499427"><span>Log in to the ASM console.</span></li><li id="asm_01_0084__en-us_topic_0000001542706401_li125894431271"><span>Click Create Mesh in the upper right corner.</span></li><li id="asm_01_0084__en-us_topic_0000001542706401_li135891543162714"><span>Configure the following parameters.</span><p><ul id="asm_01_0084__en-us_topic_0000001542706401_ul75901043202711"><li id="asm_01_0084__en-us_topic_0000001542706401_li2092711501216"><strong id="asm_01_0084__en-us_topic_0000001542706401_b1094850142211">Mesh Edition</strong><p id="asm_01_0084__en-us_topic_0000001542706401_p4479132261213">Only service meshes of the Basic edition are supported for commercial use.</p>
</li><li id="asm_01_0084__en-us_topic_0000001542706401_li35901243162718"><strong id="asm_01_0084__b515610026">Mesh Name</strong><p id="asm_01_0084__en-us_topic_0000001542706401_p19590743152711">Enter a service mesh name, which consists of 4 to 64 characters. It must start with a lowercase letter and cannot end with a hyphen (-). Only lowercase letters, digits, and hyphens (-) are allowed.</p>
<p id="asm_01_0084__en-us_topic_0000001542706401_p11590144316275">Service mesh names under the same account must be unique and cannot be modified after creation.</p>
</li><li id="asm_01_0084__en-us_topic_0000001542706401_li3590184362716"><strong id="asm_01_0084__b1652258664">Istio Version</strong><p id="asm_01_0084__en-us_topic_0000001542706401_p19590144310274">Select the Istio version supported by the service mesh.</p>
</li><li id="asm_01_0084__li20991123625914"><strong id="asm_01_0084__b54661518132116">Enable IPv6</strong><p id="asm_01_0084__p04381549215">Conditions for enabling IPv4/IPv6 dual stack for a service mesh</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="asm_01_0084__table11439754142117" frame="border" border="1" rules="all"><thead align="left"><tr id="asm_01_0084__row1743955417212"><th align="left" class="cellrowborder" valign="top" width="12.379999999999999%" id="mcps1.3.4.2.3.2.1.4.3.1.6.1.1"><p id="asm_01_0084__p1643985417218">Service Mesh Edition</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="14.91%" id="mcps1.3.4.2.3.2.1.4.3.1.6.1.2"><p id="asm_01_0084__p8439135413212">Istio Version</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="15.260000000000002%" id="mcps1.3.4.2.3.2.1.4.3.1.6.1.3"><p id="asm_01_0084__p1443995417219">Cluster Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="20.4%" id="mcps1.3.4.2.3.2.1.4.3.1.6.1.4"><p id="asm_01_0084__p14394543213">Cluster Network Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="37.05%" id="mcps1.3.4.2.3.2.1.4.3.1.6.1.5"><p id="asm_01_0084__p6439195402115">Remarks</p>
</th>
</tr>
</thead>
<tbody><tr id="asm_01_0084__row184391354172116"><td class="cellrowborder" valign="top" width="12.379999999999999%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.1 "><p id="asm_01_0084__p2043975418214">Basic edition</p>
</td>
<td class="cellrowborder" valign="top" width="14.91%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.2 "><p id="asm_01_0084__p643945413219">1.18 or later</p>
</td>
<td class="cellrowborder" valign="top" width="15.260000000000002%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.3 "><p id="asm_01_0084__p94391954112116">CCE Turbo clusters</p>
</td>
<td class="cellrowborder" valign="top" width="20.4%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.4 "><p id="asm_01_0084__p843985414211">Cloud native network 2.0</p>
</td>
<td class="cellrowborder" valign="top" width="37.05%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.5 "><p id="asm_01_0084__p17439135413211">To enable IPv6.</p>
</td>
</tr>
</tbody>
</table>
</div>
<p id="asm_01_0084__p124428207334">For details, see <a href="asm_bestpractice_1009.html">How Do I Create a Service Mesh with IPv4/IPv6 Dual Stack Enabled</a></p>
<div class="note" id="asm_01_0084__note18440654152111"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="asm_01_0084__ul1744075432120"><li id="asm_01_0084__li1744055413210"><strong id="asm_01_0084__b11396256101815">Enable IPv6</strong> is only available in Basic service meshes based on Istio 1.18 or later.</li><li id="asm_01_0084__li194404548216">IPv4/IPv6 dual stack cannot be enabled for a service mesh whose Istio version is upgraded to 1.18 or later.</li></ul>
<ul id="asm_01_0084__ul144085482119"><li id="asm_01_0084__li1344010549212">IPv4/IPv6 dual stack cannot be disabled once it is enabled for a service mesh. IPv4/IPv6 dual stack cannot be enabled for an existing service mesh.</li></ul>
</div></div>
</li><li id="asm_01_0084__en-us_topic_0000001542706401_li4590154315271"><strong id="asm_01_0084__b802456746">Cluster</strong><p id="asm_01_0084__en-us_topic_0000001542706401_p4590184313278">Select the cluster from the cluster list or enter the cluster name in the upper right corner of the list to search for it. You can only select the clusters whose versions are supported by the current service mesh version.</p>
</li><li id="asm_01_0084__en-us_topic_0000001542706401_li159044311277"><strong id="asm_01_0084__b188400504">Mesh Control Plane Node</strong><p id="asm_01_0084__en-us_topic_0000001542706401_p125902437272">The control plane components of the Basic service mesh are installed in the user cluster. Therefore, you need to select a node for installing the control plane. If HA is required, you can select two or more nodes from different AZs.</p>
<p id="asm_01_0084__en-us_topic_0000001542706401_p1959024392713">A selected node will be labeled with <strong id="asm_01_0084__b12113195612363">istio:master</strong>, and the components will be scheduled to that node.</p>
</li><li id="asm_01_0084__li17225629125"><strong id="asm_01_0084__b182161818152520">Observability Configuration</strong><ul id="asm_01_0084__ul162251921123"><li id="asm_01_0084__li1233211216319"><strong id="asm_01_0084__b1539718138">Application Metrics</strong><p id="asm_01_0084__p93321821123112">If this option is enabled, you can specify service access metrics, application topologies, and service health and SLO definitions in the service mesh.</p>
</li><li id="asm_01_0084__li1522512214127"><strong id="asm_01_0084__b1443315218391">Tracing</strong><p id="asm_01_0084__p3225124129">- <strong id="asm_01_0084__b1649171110292">Sampling Rate</strong>: Number of requests generated by the tracing service/Total number of requests</p>
<p id="asm_01_0084__p722519210123">- <strong id="asm_01_0084__b13853258294">Version</strong>: tracing service. If you select <strong id="asm_01_0084__b1028517591813">Third-party Jaeger/Zipkin service</strong>, you need to set <strong id="asm_01_0084__b613018597425">Service Address</strong> and <strong id="asm_01_0084__b665636154317">Service Port</strong>, which indicate the address and port number used by the third-party tracing service to receive requests.</p>
<div class="note" id="asm_01_0084__note122518211219"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="asm_01_0084__ul1522613251216"><li id="asm_01_0084__li112261223127">Only Istio 1.15 or later support the third-party tracing service.</li><li id="asm_01_0084__li142761222131512">If you want to use the third-party Jaeger or Zipkin service, install it first. Then, obtain the service address.</li><li id="asm_01_0084__li1622612111211">The default service ports of Jaeger and Zipkin are both 9411. If you customize the service port during Jaeger or Zipkin installation, replace <strong id="asm_01_0084__b3675134710313">Service Port</strong> with the actual value.</li></ul>
</div></div>
</li></ul>
</li></ul>
</p></li><li id="asm_01_0084__en-us_topic_0000001542706401_li185901043112713"><span>(Optional) Configure advanced settings.</span><p><ul id="asm_01_0084__en-us_topic_0000001542706401_ul195914431277"><li id="asm_01_0084__en-us_topic_0000001542706401_li105911243172720"><strong id="asm_01_0084__b103531733173714">Namespace Injection Settings</strong><p id="asm_01_0084__en-us_topic_0000001542706401_p0591154316270">Select a namespace and label it with <strong id="asm_01_0084__b1742517548222">istio-injection=enabled</strong>. After being restarted, all pods in the namespace will be automatically injected with an istio-proxy sidecar.</p>
<p id="asm_01_0084__en-us_topic_0000001542706401_p1459184332714">You can inject a sidecar in <strong id="asm_01_0084__b144823761">Mesh Configuration</strong> &gt; <strong id="asm_01_0084__b396053378">Sidecar Management</strong> after the mesh is created. For details, see <a href="asm_01_0041.html#asm_01_0041__section65931513505">Injecting a Sidecar</a>.</p>
</li><li id="asm_01_0084__en-us_topic_0000001542706401_li1059184310276"><strong id="asm_01_0084__b1787690131">Restart Existing Services</strong><p id="asm_01_0084__en-us_topic_0000001542706401_p12591144362715"><span><img id="asm_01_0084__image879324619490" src="en-us_image_0000001920032153.png"></span>: Pods of the existing services in the namespace will be restarted, which will temporarily interrupt your services. The <strong id="asm_01_0084__b408378786">istio-proxy</strong> sidecar is automatically injected into the pods of the existing services.</p>
<p id="asm_01_0084__en-us_topic_0000001542706401_p195911343162718"><span><img id="asm_01_0084__en-us_topic_0000001542706401_image1736110311031" src="en-us_image_0000001494249996.png"></span>: The <strong id="asm_01_0084__b166037221819">istio-proxy</strong> sidecar cannot be automatically injected into the pods of the existing services. You need to manually restart the workloads on the CCE console to inject the sidecar.</p>
</li><li id="asm_01_0084__li103761117176"><strong id="asm_01_0084__b161488533415">Traffic Interception Settings</strong><div class="note" id="asm_01_0084__note9376117978"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0084__p2376181712720">By default, sidecars intercept all inbound and outbound traffic of pods. You can modify the default traffic rules in <strong id="asm_01_0084__b134331479345">Traffic Interception Settings</strong>.</p>
</div></div>
<p id="asm_01_0084__p93763174718"><strong id="asm_01_0084__b9810181314341">Inbound Ports</strong>: Inbound ports separated by commas (,). You can use this field to specify the ports that will be included or excluded for inbound traffic redirection.</p>
<ul id="asm_01_0084__ul1376817679"><li id="asm_01_0084__li33768171718"><strong id="asm_01_0084__b16992015173412">Include only specified ports</strong> means that the traffic to services in a service mesh over specified ports will be redirected to the sidecar.</li></ul>
<ul id="asm_01_0084__ul73766176715"><li id="asm_01_0084__li1137612175714"><strong id="asm_01_0084__b15386151833412">Exclude only specified ports</strong> means that the traffic to services in a service mesh over the ports except the specified ports will be redirected to the sidecar.</li></ul>
<p id="asm_01_0084__p437612171973"><strong id="asm_01_0084__b155051822203412">Outbound Ports</strong>: Outbound ports separated by commas (,). You can use this field to specify the ports that will be included or excluded for outbound traffic redirection.</p>
<ul id="asm_01_0084__ul10376151714710"><li id="asm_01_0084__li16376121711719"><strong id="asm_01_0084__b10871024123417">Include only specified ports</strong> means that the traffic from services in a service mesh over specified ports will be redirected to the sidecar.</li></ul>
<ul id="asm_01_0084__ul337611714716"><li id="asm_01_0084__li1337717171578"><strong id="asm_01_0084__b67131127173417">Exclude only specified ports</strong> means that the traffic from services in a service mesh over the ports except the specified ports will be redirected to the sidecar.</li></ul>
<p id="asm_01_0084__p11377181717712"><strong id="asm_01_0084__b20653518442">Outbound IP Ranges</strong>: IP address ranges separated by commas (,) in CIDR format. You can use this field to specify the IP ranges that will be included or excluded for outbound traffic redirection.</p>
<ul id="asm_01_0084__ul1337716172078"><li id="asm_01_0084__li1377417579"><strong id="asm_01_0084__b39502030153411">Include only specified IP ranges</strong> means that the traffic from specified IP ranges will be redirected to the sidecar.</li></ul>
<ul id="asm_01_0084__ul14377181711717"><li id="asm_01_0084__li3377171710719"><strong id="asm_01_0084__b393303213347">Exclude only specified IP ranges</strong> means that the traffic from IP ranges except the specified IP ranges will be redirected to the sidecar.</li></ul>
</li><li id="asm_01_0084__li1611138125316"><strong id="asm_01_0084__b45332301">Resource Tags</strong><p id="asm_01_0084__p1711128135317">Enter the tag key and tag value. A maximum of 20 tags can be added.</p>
</li></ul>
</p></li><li id="asm_01_0084__en-us_topic_0000001542706401_li859154318271"><span>Review the service mesh configuration in <strong id="asm_01_0084__b1242153466">Configuration List</strong> on the right of the page and click <strong id="asm_01_0084__b1055755240">Submit</strong>.</span><p><p id="asm_01_0084__en-us_topic_0000001542706401_p13591174382714">It takes about 1 to 3 minutes to create a service mesh. If the service mesh status changes from <strong id="asm_01_0084__b1912594259">Installing</strong> to <strong id="asm_01_0084__b68523616">Running</strong>, the service mesh is successfully created.</p>
<div class="note" id="asm_01_0084__en-us_topic_0000001542706401_note14591184342712"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0084__en-us_topic_0000001542706401_p1459119432275">When the service mesh is enabled, the following operations are performed:</p>
<ul id="asm_01_0084__en-us_topic_0000001542706401_ul859134311276"><li id="asm_01_0084__en-us_topic_0000001542706401_li195911043152719">Helm orchestrates the application into a Release as the resource of the service mesh control plane.</li></ul>
</div></div>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0017.html">Creating a Service Mesh</a></div>
</div>
</div>

2
docs/asm/umn/asm_01_0124.html
View File

@ -1,7 +1,7 @@
<a name="asm_01_0124"></a><a name="asm_01_0124"></a> <a name="asm_01_0124"></a><a name="asm_01_0124"></a>
<h1 class="topictitle1">Features in v1.18</h1> <h1 class="topictitle1">Features in v1.18</h1>
<div id="body0000001737146797"><ul id="asm_01_0124__ul1742120185319"><li id="asm_01_0124__li1842160195316">Istio 1.18 is supported.</li><li id="asm_01_0124__li1036314425311">CCE Turbo clusters v1.25, v1.27, and v1.28 are supported.</li><li id="asm_01_0124__li6393101715319">CCE clusters v1.25, v1.27, and v1.28 are supported.</li><li id="asm_01_0124__li1910522175320">Kubernetes Gateway API is supported.</li></ul> <div id="body0000001737146797"><ul id="asm_01_0124__ul1742120185319"><li id="asm_01_0124__li1842160195316">Istio 1.18 is supported.</li><li id="asm_01_0124__li1036314425311">CCE Turbo clusters v1.25, v1.27, v1.28, v1.29, and v1.30 are supported.</li><li id="asm_01_0124__li6393101715319">CCE clusters v1.25, v1.27, v1.28, v1.29, and v1.30 are supported.</li><li id="asm_01_0124__li1910522175320">Kubernetes Gateway API is supported.</li></ul>
<p id="asm_01_0124__p58433415527">For details, visit <a href="https://istio.io/latest/news/releases/1.18.x/" target="_blank" rel="noopener noreferrer">https://istio.io/latest/news/releases/1.18.x/</a>.</p> <p id="asm_01_0124__p58433415527">For details, visit <a href="https://istio.io/latest/news/releases/1.18.x/" target="_blank" rel="noopener noreferrer">https://istio.io/latest/news/releases/1.18.x/</a>.</p>
</div> </div>
<div> <div>

2
docs/asm/umn/asm_faq_0044.html
View File

@ -21,7 +21,7 @@
</tr> </tr>
<tr id="asm_faq_0044__row13514175315319"><td class="cellrowborder" valign="top" width="49.919999999999995%"><p id="asm_faq_0044__p16527951103114">1.18</p> <tr id="asm_faq_0044__row13514175315319"><td class="cellrowborder" valign="top" width="49.919999999999995%"><p id="asm_faq_0044__p16527951103114">1.18</p>
</td> </td>
<td class="cellrowborder" valign="top" width="50.080000000000005%"><p id="asm_faq_0044__p195271851173113">1.25,1.27, and 1.28</p> <td class="cellrowborder" valign="top" width="50.080000000000005%"><p id="asm_faq_0044__p195271851173113">1.25, 1.27, 1.28, 1.29, and 1.30</p>
</td> </td>
</tr> </tr>
</tbody> </tbody>

7
docs/asm/umn/asm_his_0001.html
View File

@ -8,7 +8,12 @@
</th> </th>
</tr> </tr>
</thead> </thead>
<tbody><tr id="asm_his_0001__row12332131943315"><td class="cellrowborder" valign="top" width="20.5%" headers="mcps1.3.1.2.3.1.1 "><p id="asm_his_0001__p633271918332">2024-10-12</p> <tbody><tr id="asm_his_0001__row12221715111214"><td class="cellrowborder" valign="top" width="20.5%" headers="mcps1.3.1.2.3.1.1 "><p id="asm_his_0001__p831582041212">2024-12-02</p>
</td>
<td class="cellrowborder" valign="top" width="79.5%" headers="mcps1.3.1.2.3.1.2 "><p id="asm_his_0001__p1477102715123">Added clusters v1.29 and v1.30.</p>
</td>
</tr>
<tr id="asm_his_0001__row12332131943315"><td class="cellrowborder" valign="top" width="20.5%" headers="mcps1.3.1.2.3.1.1 "><p id="asm_his_0001__p633271918332">2024-10-12</p>
</td> </td>
<td class="cellrowborder" valign="top" width="79.5%" headers="mcps1.3.1.2.3.1.2 "><ul id="asm_his_0001__ul124871631153718"><li id="asm_his_0001__li114871531183711">The following are modifications based on review comments:<p id="asm_his_0001__p16968945178"><a name="asm_his_0001__li114871531183711"></a><a name="li114871531183711"></a>- Added the "Upgrades" chapter.</p> <td class="cellrowborder" valign="top" width="79.5%" headers="mcps1.3.1.2.3.1.2 "><ul id="asm_his_0001__ul124871631153718"><li id="asm_his_0001__li114871531183711">The following are modifications based on review comments:<p id="asm_his_0001__p16968945178"><a name="asm_his_0001__li114871531183711"></a><a name="li114871531183711"></a>- Added the "Upgrades" chapter.</p>
<p id="asm_his_0001__p13718237816">- Updated the infographic of ASM.</p> <p id="asm_his_0001__p13718237816">- Updated the infographic of ASM.</p>

3
docs/asm/umn/asm_productdesc_0004.html
View File

@ -16,14 +16,13 @@
</tr> </tr>
<tr id="asm_productdesc_0004__row2060314173555"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.1.3.2.3.1.1 "><p id="asm_productdesc_0004__p760391712553">1.18</p> <tr id="asm_productdesc_0004__row2060314173555"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.1.3.2.3.1.1 "><p id="asm_productdesc_0004__p760391712553">1.18</p>
</td> </td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.1.3.2.3.1.2 "><p id="asm_productdesc_0004__p14822277556">v1.25, v1.27, or v1.28</p> <td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.1.3.2.3.1.2 "><p id="asm_productdesc_0004__p14822277556">v1.25, v1.27, v1.28, v1.29, or v1.30</p>
</td> </td>
</tr> </tr>
</tbody> </tbody>
</table> </table>
</div> </div>
<p id="asm_productdesc_0004__p697265013512">Containers on the node running Ubuntu 22.04 in a CCE Turbo cluster cannot be added to a service mesh earlier than v1.18.</p> <p id="asm_productdesc_0004__p697265013512">Containers on the node running Ubuntu 22.04 in a CCE Turbo cluster cannot be added to a service mesh earlier than v1.18.</p>
<ul id="asm_productdesc_0004__ul29692500510"><li id="asm_productdesc_0004__li99693501352">Ubuntu 22.04</li></ul>
</div> </div>
<div class="section" id="asm_productdesc_0004__section16988202112217"><h4 class="sectiontitle">Constraints on Service Meshes</h4><p id="asm_productdesc_0004__p3409102719214">When you use service meshes for service governance, a Deployment can only match with one service to avoid abnormal grayscale release, gateway access, or other functions.</p> <div class="section" id="asm_productdesc_0004__section16988202112217"><h4 class="sectiontitle">Constraints on Service Meshes</h4><p id="asm_productdesc_0004__p3409102719214">When you use service meshes for service governance, a Deployment can only match with one service to avoid abnormal grayscale release, gateway access, or other functions.</p>
</div> </div>

10
docs/asm/umn/asm_qs_0001_0.html
View File

@ -27,12 +27,12 @@
</li></ol> </li></ol>
</p></li><li id="asm_qs_0001_0__li14380534605"><span>Create a load balancer.</span><p><p id="asm_qs_0001_0__p1488616491502">A load balancer will be used as the external access entry of a service mesh, which will route the traffic to backend services.</p> </p></li><li id="asm_qs_0001_0__li14380534605"><span>Create a load balancer.</span><p><p id="asm_qs_0001_0__p1488616491502">A load balancer will be used as the external access entry of a service mesh, which will route the traffic to backend services.</p>
<ol type="a" id="asm_qs_0001_0__ol125113615456"><li id="asm_qs_0001_0__li178327432456">Log in to the Elastic Load Balance (ELB) console.</li><li id="asm_qs_0001_0__li8832174394516">Click Create Elastic Load Balancer in the upper right corner.</li><li id="asm_qs_0001_0__li14832124394516"><strong id="asm_qs_0001_0__b1142711381198">VPC</strong> and <strong id="asm_qs_0001_0__b742716381395">Subnet</strong>: Select the VPC and subnet created in <a href="#asm_qs_0001_0__li14222135210592">1</a>, configure other parameters as prompted, and click Create Now.</li></ol> <ol type="a" id="asm_qs_0001_0__ol125113615456"><li id="asm_qs_0001_0__li178327432456">Log in to the Elastic Load Balance (ELB) console.</li><li id="asm_qs_0001_0__li8832174394516">Click Create Elastic Load Balancer in the upper right corner.</li><li id="asm_qs_0001_0__li14832124394516"><strong id="asm_qs_0001_0__b1142711381198">VPC</strong> and <strong id="asm_qs_0001_0__b742716381395">Subnet</strong>: Select the VPC and subnet created in <a href="#asm_qs_0001_0__li14222135210592">1</a>, configure other parameters as prompted, and click Create Now.</li></ol>
</p></li><li id="asm_qs_0001_0__li1024821518115"><a name="asm_qs_0001_0__li1024821518115"></a><a name="li1024821518115"></a><span>Create a cluster.</span><p><ol type="a" id="asm_qs_0001_0__ol35691826558"><li id="asm_qs_0001_0__li15698235515">Log in to the Cloud Container Engine (CCE) console.</li><li id="asm_qs_0001_0__li733813348559">In the navigation pane, choose <strong id="asm_qs_0001_0__b1639017489102436">Resource Management</strong> &gt;<strong id="asm_qs_0001_0__b1029020386102436"> Clusters</strong>. Then, click <strong id="asm_qs_0001_0__b1321849663102436">Create CCE Cluster</strong> in the upper right corner.</li><li id="asm_qs_0001_0__li03456151153">On the <span class="wintitle" id="asm_qs_0001_0__wintitle757905789"><b>Configure</b></span> page, configure the following parameters and retain the default values for other parameters.<ul id="asm_qs_0001_0__ul113451715759"><li id="asm_qs_0001_0__li234517151855"><strong id="asm_qs_0001_0__b1683900853">Cluster Name</strong>: Enter a cluster name, for example, <span class="parmvalue" id="asm_qs_0001_0__parmvalue815522302"><b>cce-asm</b></span>.</li><li id="asm_qs_0001_0__li1934519158512"><strong id="asm_qs_0001_0__b2006651786">VPC</strong> and <strong id="asm_qs_0001_0__b1290597328">Subnet</strong>: Select the VPC and subnet created in <a href="#asm_qs_0001_0__li14222135210592">1</a>.</li></ul> </p></li><li id="asm_qs_0001_0__li1024821518115"><a name="asm_qs_0001_0__li1024821518115"></a><a name="li1024821518115"></a><span>Create a cluster.</span><p><ol type="a" id="asm_qs_0001_0__ol35691826558"><li id="asm_qs_0001_0__li15698235515">Log in to the Cloud Container Engine (CCE) console.</li><li id="asm_qs_0001_0__li733813348559">In the navigation pane, choose <strong id="asm_qs_0001_0__b1639017489102436">Resource Management</strong> &gt;<strong id="asm_qs_0001_0__b1029020386102436"> Clusters</strong>. Then, click <strong id="asm_qs_0001_0__b1321849663102436">Create CCE Cluster</strong> in the upper right corner.</li><li id="asm_qs_0001_0__li03456151153">On the <span class="wintitle" id="asm_qs_0001_0__wintitle270155058"><b>Configure</b></span> page, configure the following parameters and retain the default values for other parameters.<ul id="asm_qs_0001_0__ul113451715759"><li id="asm_qs_0001_0__li234517151855"><strong id="asm_qs_0001_0__b1151554755">Cluster Name</strong>: Enter a cluster name, for example, <span class="parmvalue" id="asm_qs_0001_0__parmvalue981449106"><b>cce-asm</b></span>.</li><li id="asm_qs_0001_0__li1934519158512"><strong id="asm_qs_0001_0__b806401155">VPC</strong> and <strong id="asm_qs_0001_0__b1656264825">Subnet</strong>: Select the VPC and subnet created in <a href="#asm_qs_0001_0__li14222135210592">1</a>.</li></ul>
</li><li id="asm_qs_0001_0__li12196175014712">Click <span class="uicontrol" id="asm_qs_0001_0__uicontrol78743142118"><b>Next: Create Node</b></span>, configure the following parameters, and retain the default values for other parameters.<ul id="asm_qs_0001_0__ul1319612501720"><li id="asm_qs_0001_0__li8196050373"><strong id="asm_qs_0001_0__b1498188541">Specifications</strong>: 4 vCPUs and 8 GiB of memory.<div class="note" id="asm_qs_0001_0__note1819695010719"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_qs_0001_0__p419720501712">This is the minimum specifications for deploying Bookinfo.</p> </li><li id="asm_qs_0001_0__li12196175014712">Click <span class="uicontrol" id="asm_qs_0001_0__uicontrol78743142118"><b>Next: Create Node</b></span>, configure the following parameters, and retain the default values for other parameters.<ul id="asm_qs_0001_0__ul1319612501720"><li id="asm_qs_0001_0__li8196050373"><strong id="asm_qs_0001_0__b852110204">Specifications</strong>: 4 vCPUs and 8 GiB of memory.<div class="note" id="asm_qs_0001_0__note1819695010719"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_qs_0001_0__p419720501712">This is the minimum specifications for deploying Bookinfo.</p>
</div></div> </div></div>
</li><li id="asm_qs_0001_0__li81971050376"><strong id="asm_qs_0001_0__b365642206">Login Mode</strong>: Select the key pair created in <a href="#asm_qs_0001_0__li8805135016420">2</a> for identity authentication upon remote node login.</li></ul> </li><li id="asm_qs_0001_0__li81971050376"><strong id="asm_qs_0001_0__b1639432708">Login Mode</strong>: Select the key pair created in <a href="#asm_qs_0001_0__li8805135016420">2</a> for identity authentication upon remote node login.</li></ul>
</li><li id="asm_qs_0001_0__li9856633161616">Click <span class="uicontrol" id="asm_qs_0001_0__uicontrol1977165045"><b>Next: Install Add-on</b></span> and select the add-ons to be installed in the <span class="wintitle" id="asm_qs_0001_0__wintitle449146344"><b>Install Add-on</b></span> step.<p id="asm_qs_0001_0__p208561333191617"><span class="parmvalue" id="asm_qs_0001_0__parmvalue2034074422"><b>System resource add-on</b></span> must be installed. <span class="parmvalue" id="asm_qs_0001_0__parmvalue1841074663"><b>Advanced functional add-on</b></span> is optional.</p> </li><li id="asm_qs_0001_0__li9856633161616">Click <span class="uicontrol" id="asm_qs_0001_0__uicontrol1923337554"><b>Next: Install Add-on</b></span> and select the add-ons to be installed in the <span class="wintitle" id="asm_qs_0001_0__wintitle2012913116"><b>Install Add-on</b></span> step.<p id="asm_qs_0001_0__p208561333191617"><span class="parmvalue" id="asm_qs_0001_0__parmvalue475570086"><b>System resource add-on</b></span> must be installed. <span class="parmvalue" id="asm_qs_0001_0__parmvalue1614845412"><b>Advanced functional add-on</b></span> is optional.</p>
</li><li id="asm_qs_0001_0__li3384181011225">Click <span class="uicontrol" id="asm_qs_0001_0__uicontrol1770231579"><b>Next: Confirm</b></span>. Read the product constraints and select <span class="uicontrol" id="asm_qs_0001_0__uicontrol816523487"><b>I am aware of the above limitations</b></span>. Review the configured parameters and specifications.</li><li id="asm_qs_0001_0__li28281540151617">Submit the order.<p id="asm_qs_0001_0__p109404516228"><a name="asm_qs_0001_0__li28281540151617"></a><a name="li28281540151617"></a>It takes about 6 to 10 minutes to create a cluster. You can click <span class="uicontrol" id="asm_qs_0001_0__uicontrol582517597"><b>Back to Cluster List</b></span> to perform other operations on the cluster or click <span class="uicontrol" id="asm_qs_0001_0__uicontrol1216552876"><b>Go to Cluster Events</b></span> to view the cluster details.</p> </li><li id="asm_qs_0001_0__li3384181011225">Click <span class="uicontrol" id="asm_qs_0001_0__uicontrol1034058927"><b>Next: Confirm</b></span>. Read the product constraints and select <span class="uicontrol" id="asm_qs_0001_0__uicontrol1222777874"><b>I am aware of the above limitations</b></span>. Review the configured parameters and specifications.</li><li id="asm_qs_0001_0__li28281540151617">Submit the order.<p id="asm_qs_0001_0__p109404516228"><a name="asm_qs_0001_0__li28281540151617"></a><a name="li28281540151617"></a>It takes about 6 to 10 minutes to create a cluster. You can click <span class="uicontrol" id="asm_qs_0001_0__uicontrol1928242792"><b>Back to Cluster List</b></span> to perform other operations on the cluster or click <span class="uicontrol" id="asm_qs_0001_0__uicontrol856460628"><b>Go to Cluster Events</b></span> to view the cluster details.</p>
</li></ol> </li></ol>
</p></li><li id="asm_qs_0001_0__li137762318452"><span>Prepare the images required by Bookinfo (as shown in <a href="#asm_qs_0001_0__table428162913363">Table 1</a>), push them to SWR and set their <strong id="asm_qs_0001_0__b1358383215282">Type</strong> to <strong id="asm_qs_0001_0__b14662101312284">Public</strong>.</span><p><div class="caution" id="asm_qs_0001_0__note174901846144918"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="asm_qs_0001_0__p1649064614491">The image name and tag of each service must be the same as those in <a href="#asm_qs_0001_0__table428162913363">Table 1</a>. Otherwise, the experience task may fail.</p> </p></li><li id="asm_qs_0001_0__li137762318452"><span>Prepare the images required by Bookinfo (as shown in <a href="#asm_qs_0001_0__table428162913363">Table 1</a>), push them to SWR and set their <strong id="asm_qs_0001_0__b1358383215282">Type</strong> to <strong id="asm_qs_0001_0__b14662101312284">Public</strong>.</span><p><div class="caution" id="asm_qs_0001_0__note174901846144918"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="asm_qs_0001_0__p1649064614491">The image name and tag of each service must be the same as those in <a href="#asm_qs_0001_0__table428162913363">Table 1</a>. Otherwise, the experience task may fail.</p>
</div></div> </div></div>

BIN
docs/asm/umn/en-us_image_0000002086005592.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 6.9 KiB