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

ASM UMN update 20241012

Browse Source 
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com>
Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
This commit is contained in:
Dong, Qiu Jian 2024-10-18 07:32:37 +00:00 committed by zuul
parent f5c28c856a
commit e743e7f7b8
47 changed files with 849 additions and 360 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

File diff suppressed because it is too large Load Diff

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

File diff suppressed because it is too large Load Diff

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_0020.html">Creating a Service Mesh</a></strong><br> <li class="ulchildlink"><strong><a href="asm_01_0084.html">Creating a Service Mesh</a></strong><br>
</li> </li>
</ul> </ul>

56
docs/asm/umn/asm_01_0020.html
View File

@ -1,56 +0,0 @@
<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 service mesh of the Basic edition, which is a standard service mesh available 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.</p>
</li><li id="asm_01_0020__en-us_topic_0000001542706401_li35901243162718"><strong id="asm_01_0020__b696006975">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__b1645938020">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__p1499153613599">Determine whether to enable IPv6. This option is supported only in Istio 1.18 or later.</p>
</li><li id="asm_01_0020__en-us_topic_0000001542706401_li4590154315271"><strong id="asm_01_0020__b1309500367">Cluster</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p4590184313278">Select the target cluster from the cluster list or enter the target cluster name in the upper right corner of the list to search for it. You can select only the clusters which versions are supported by the current mesh version.</p>
</li><li id="asm_01_0020__en-us_topic_0000001542706401_li159044311277"><strong id="asm_01_0020__b1490852056">Mesh Control Plane Node</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p125902437272">To install the control plane components for the service mesh of the Basic edition in your cluster, you need to select a node for installation. 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">The selected node is labeled with <strong id="asm_01_0020__b12113195612363">istio:master</strong>, and the components are scheduled to this 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__b274587613">Application Metrics</strong><p id="asm_01_0020__p93321821123112">If this option is enabled, you can build service access metrics, application topologies, and service health and SLO definitions in the service mesh.</p>
</li><li id="asm_01_0020__li4225182181210"><strong id="asm_01_0020__b784414181280">Access Logging</strong><p id="asm_01_0020__p172253214122">If this option is enabled, you can query inter-service access records in the service mesh to locate exceptions. After enabling this option, you need to select the Log Tank Service (LTS) log group and log stream. Access logs will be transmitted to the log stream. You can view the access logs on the <strong id="asm_01_0020__b109851931102518">Monitoring Center</strong> &gt; <strong id="asm_01_0020__b098543172514">Access Logs</strong> page.</p>
<div class="note" id="asm_01_0020__note172251629121"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="asm_01_0020__ul10225923127"><li id="asm_01_0020__li17225122121217">Only Istio 1.18 or later can work with LTS to collect and store access logs. To ensure logs are reported to LTS, install CCE Log-Agent on the <strong id="asm_01_0020__b16168103005612">Add-ons</strong> page in advance.</li></ul>
</div></div>
</li><li id="asm_01_0020__li1522512214127">Tracing<p id="asm_01_0020__p3225124129"><a name="asm_01_0020__li1522512214127"></a><a name="li1522512214127"></a>- <strong id="asm_01_0020__b1649171110292">Sampling Rate</strong>: Number of requests generated by the tracing/Total number of requests</p>
<p id="asm_01_0020__p722519210123">- <strong id="asm_01_0020__b13853258294">Version</strong>: the 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 Jaeger or Zipkin first. Alternatively, you can obtain the service address after installing Jaeger or Zipkin by referring to section "Installing Jaeger/Zipkin" in the <em id="asm_01_0020__i195711233204615">FAQs</em>.</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__b1279363897">Sidecar Configuration</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p0591154316270">Select a namespace and label it with <strong id="asm_01_0020__b1228706015">istio-injection=enabled</strong>. All pods in the namespace will be injected with an istio-proxy sidecar.</p>
<p id="asm_01_0020__en-us_topic_0000001542706401_p1459184332714">You can inject a sidecar in <strong id="asm_01_0020__b441230997">Mesh Configuration</strong> &gt; <strong id="asm_01_0020__b844338891">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_0020__en-us_topic_0000001542706401_li1059184310276"><strong id="asm_01_0020__b534709116">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__b666069868">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__b1846318299347">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 excluded from redirection to the sidecar.</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__b1838169676">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 the <strong id="asm_01_0020__b1200737994">Configuration List</strong> on the right of the page and click <strong id="asm_01_0020__b170596237">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__b1247244532">Installing</strong> to <strong id="asm_01_0020__b335797679">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>

4
docs/asm/umn/asm_01_0023.html
View File

@ -4,9 +4,9 @@
<div id="body0000001158734023"></div> <div id="body0000001158734023"></div>
<div> <div>
<ul class="ullinks"> <ul class="ullinks">
<li class="ulchildlink"><strong><a href="asm_01_0133.html">Mesh Events</a></strong><br> <li class="ulchildlink"><strong><a href="asm_01_0133.html">Service Mesh Events</a></strong><br>
</li> </li>
<li class="ulchildlink"><strong><a href="asm_01_0086.html">Uninstalling a Mesh</a></strong><br> <li class="ulchildlink"><strong><a href="asm_01_0086.html">Uninstalling a Service Mesh</a></strong><br>
</li> </li>
</ul> </ul>

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

@ -10,7 +10,7 @@
</li> </li>
<li class="ulchildlink"><strong><a href="asm_01_0091.html">Istio Resource Management</a></strong><br> <li class="ulchildlink"><strong><a href="asm_01_0091.html">Istio Resource Management</a></strong><br>
</li> </li>
<li class="ulchildlink"><strong><a href="asm_01_0123.html">Service Mesh Extension</a></strong><br> <li class="ulchildlink"><strong><a href="asm_01_0082.html">Upgrades</a></strong><br>
</li> </li>
</ul> </ul>

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

@ -4,7 +4,7 @@
<div id="body0000001130251799"><p id="asm_01_0039__p4238151805917">Mesh configuration provides cluster management, sidecar management, Istio resource management, and upgrade capabilities.</p> <div id="body0000001130251799"><p id="asm_01_0039__p4238151805917">Mesh configuration provides cluster management, sidecar management, Istio resource management, and upgrade capabilities.</p>
<p id="asm_01_0039__p163921786389">The <span class="keyword" id="asm_01_0039__keyword131251951123817">mesh control plane</span> workloads inject and manage sidecars of data plane pods, deliver policies and configurations, and collect monitoring data. Sidecars work with service containers in data plane pods, and they are in charge of routing and forwarding, traffic policy configuration, and monitoring data collection.</p> <p id="asm_01_0039__p163921786389">The <span class="keyword" id="asm_01_0039__keyword131251951123817">mesh control plane</span> workloads inject and manage sidecars of data plane pods, deliver policies and configurations, and collect monitoring data. Sidecars work with service containers in data plane pods, and they are in charge of routing and forwarding, traffic policy configuration, and monitoring data collection.</p>
<p id="asm_01_0039__p1536713311506">The functions of each tab page in <strong id="asm_01_0039__b177799347410267">Mesh Configuration</strong> are as follows:</p> <p id="asm_01_0039__p1536713311506">The functions of each tab page in <strong id="asm_01_0039__b177799347410267">Mesh Configuration</strong> are as follows:</p>
<ul id="asm_01_0039__ul9284111135016"><li id="asm_01_0039__li15284151145016"><strong id="asm_01_0039__b10692151818228">Basic Information</strong>: You can view the mesh name, ID, status, edition, version, observability, creation time, and clusters with the mesh enabled.</li><li id="asm_01_0039__li528481114502"><strong id="asm_01_0039__b19089497110267">Sidecar Management</strong>: You can view information about all workloads injected with sidecars, perform sidecar injection, and configure sidecar resource limits. For details, see <a href="asm_01_0041.html">Sidecar Management</a>.</li><li id="asm_01_0039__li1928421195014"><strong id="asm_01_0039__b31091261810267">Istio Resource Management</strong>: You can view all Istio resources (such as VirtualService and DestinationRule), create Istio resources in YAML or JSON format, and modify existing Istio resources. For details, see <a href="asm_01_0091.html">Istio Resource Management</a>.</li><li id="asm_01_0039__li5725212101718"><strong id="asm_01_0039__b1280153963219">Upgrade</strong>: You can upgrade the version of a service mesh.</li><li id="asm_01_0039__li95496517363">Mesh extension: provides the observability configuration. For details, see <a href="asm_01_0123.html">Service Mesh Extension</a>.</li></ul> <ul id="asm_01_0039__ul9284111135016"><li id="asm_01_0039__li15284151145016"><strong id="asm_01_0039__b10692151818228">Basic Information</strong>: You can view the mesh name, ID, status, edition, version, observability, creation time, and clusters with the mesh enabled.</li><li id="asm_01_0039__li528481114502"><strong id="asm_01_0039__b19089497110267">Sidecar Management</strong>: You can view information about all workloads injected with sidecars, perform sidecar injection, and configure sidecar resource limits. For details, see <a href="asm_01_0041.html">Sidecar Management</a>.</li><li id="asm_01_0039__li1928421195014"><strong id="asm_01_0039__b31091261810267">Istio Resource Management</strong>: You can view all Istio resources (such as VirtualService and DestinationRule), create Istio resources in YAML or JSON format, and modify existing Istio resources. For details, see <a href="asm_01_0091.html">Istio Resource Management</a>.</li><li id="asm_01_0039__li5725212101718"><strong id="asm_01_0039__b1280153963219">Upgrade</strong>: You can upgrade the version of a service mesh.</li><li id="asm_01_0039__li95496517363"><strong id="asm_01_0039__b26693011417">Extensions</strong>: provides the observability configuration. </li></ul>
</div> </div>
<div> <div>
<div class="familylinks"> <div class="familylinks">

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

@ -17,7 +17,7 @@
</td> </td>
<td class="cellrowborder" valign="top" width="50.44504450445044%" headers="mcps1.3.1.3.2.4.2.4.1.2 "><p id="asm_01_0050__p1794123683516">Maximum number of retries allowed for a single request. The default retry interval is 25 ms. The actual number of retries depends on the configured timeout period and retry timeout period.</p> <td class="cellrowborder" valign="top" width="50.44504450445044%" headers="mcps1.3.1.3.2.4.2.4.1.2 "><p id="asm_01_0050__p1794123683516">Maximum number of retries allowed for a single request. The default retry interval is 25 ms. The actual number of retries depends on the configured timeout period and retry timeout period.</p>
</td> </td>
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.4.2.4.1.3 "><p id="asm_01_0050__p29443612355">1-2147483647</p> <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.4.2.4.1.3 "><p id="asm_01_0050__p29443612355">1-4294967295</p>
</td> </td>
</tr> </tr>
<tr id="asm_01_0050__row394336163516"><td class="cellrowborder" valign="top" width="16.221622162216224%" headers="mcps1.3.1.3.2.4.2.4.1.1 "><p id="asm_01_0050__p159453616355">Retry Timeout (s)</p> <tr id="asm_01_0050__row394336163516"><td class="cellrowborder" valign="top" width="16.221622162216224%" headers="mcps1.3.1.3.2.4.2.4.1.1 "><p id="asm_01_0050__p159453616355">Retry Timeout (s)</p>
@ -75,14 +75,14 @@
</td> </td>
<td class="cellrowborder" valign="top" width="46.31463146314631%" headers="mcps1.3.1.3.2.12.2.4.1.2 "><p id="asm_01_0050__p259314264212">Maximum number of HTTP/TCP connections to the target service. The default value is <strong id="asm_01_0050__b19141131716237">4294967295</strong>.</p> <td class="cellrowborder" valign="top" width="46.31463146314631%" headers="mcps1.3.1.3.2.12.2.4.1.2 "><p id="asm_01_0050__p259314264212">Maximum number of HTTP/TCP connections to the target service. The default value is <strong id="asm_01_0050__b19141131716237">4294967295</strong>.</p>
</td> </td>
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.12.2.4.1.3 "><p id="asm_01_0050__p195931021426">1-2147483647</p> <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.12.2.4.1.3 "><p id="asm_01_0050__p195931021426">1-4294967295</p>
</td> </td>
</tr> </tr>
<tr id="asm_01_0050__row115931724426"><td class="cellrowborder" valign="top" width="20.352035203520348%" headers="mcps1.3.1.3.2.12.2.4.1.1 "><p id="asm_01_0050__p10593924425">Maximum Number of Non-responses</p> <tr id="asm_01_0050__row115931724426"><td class="cellrowborder" valign="top" width="20.352035203520348%" headers="mcps1.3.1.3.2.12.2.4.1.1 "><p id="asm_01_0050__p10593924425">Maximum Number of Non-responses</p>
</td> </td>
<td class="cellrowborder" valign="top" width="46.31463146314631%" headers="mcps1.3.1.3.2.12.2.4.1.2 "><p id="asm_01_0050__p5593220428">Maximum number of keepalive probes to be sent before the connection is determined to be invalid. By default, the OS-level configuration is used. (The default value is <strong id="asm_01_0050__b1550574018557">9</strong> for Linux.)</p> <td class="cellrowborder" valign="top" width="46.31463146314631%" headers="mcps1.3.1.3.2.12.2.4.1.2 "><p id="asm_01_0050__p5593220428">Maximum number of keepalive probes to be sent before the connection is determined to be invalid. By default, the OS-level configuration is used. (The default value is <strong id="asm_01_0050__b1550574018557">9</strong> for Linux.)</p>
</td> </td>
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.12.2.4.1.3 "><p id="asm_01_0050__p7593162154215">1-2147483647</p> <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.12.2.4.1.3 "><p id="asm_01_0050__p7593162154215">1-4294967295</p>
</td> </td>
</tr> </tr>
<tr id="asm_01_0050__row5593228426"><td class="cellrowborder" valign="top" width="20.352035203520348%" headers="mcps1.3.1.3.2.12.2.4.1.1 "><p id="asm_01_0050__p75931722427">Health Check Interval (s)</p> <tr id="asm_01_0050__row5593228426"><td class="cellrowborder" valign="top" width="20.352035203520348%" headers="mcps1.3.1.3.2.12.2.4.1.1 "><p id="asm_01_0050__p75931722427">Health Check Interval (s)</p>
@ -122,14 +122,14 @@
</td> </td>
<td class="cellrowborder" valign="top" width="46.31463146314631%" headers="mcps1.3.1.3.2.13.2.4.1.2 "><p id="asm_01_0050__p119841260462">Maximum number of requests that can be forwarded to a single service pod. The default value is <strong id="asm_01_0050__b7763925181711">4294967295</strong>.</p> <td class="cellrowborder" valign="top" width="46.31463146314631%" headers="mcps1.3.1.3.2.13.2.4.1.2 "><p id="asm_01_0050__p119841260462">Maximum number of requests that can be forwarded to a single service pod. The default value is <strong id="asm_01_0050__b7763925181711">4294967295</strong>.</p>
</td> </td>
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.13.2.4.1.3 "><p id="asm_01_0050__p15984116134610">1-2147483647</p> <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.13.2.4.1.3 "><p id="asm_01_0050__p15984116134610">1-4294967295</p>
</td> </td>
</tr> </tr>
<tr id="asm_01_0050__row19984365464"><td class="cellrowborder" valign="top" width="20.352035203520348%" headers="mcps1.3.1.3.2.13.2.4.1.1 "><p id="asm_01_0050__p1498412684614">Maximum Number of Pending Requests</p> <tr id="asm_01_0050__row19984365464"><td class="cellrowborder" valign="top" width="20.352035203520348%" headers="mcps1.3.1.3.2.13.2.4.1.1 "><p id="asm_01_0050__p1498412684614">Maximum Number of Pending Requests</p>
</td> </td>
<td class="cellrowborder" valign="top" width="46.31463146314631%" headers="mcps1.3.1.3.2.13.2.4.1.2 "><p id="asm_01_0050__p169845614613">Maximum number of HTTP requests that can be forwarded to the target service for processing. The default value is <strong id="asm_01_0050__b165001542141714">4294967295</strong>.</p> <td class="cellrowborder" valign="top" width="46.31463146314631%" headers="mcps1.3.1.3.2.13.2.4.1.2 "><p id="asm_01_0050__p169845614613">Maximum number of HTTP requests that can be forwarded to the target service for processing. The default value is <strong id="asm_01_0050__b165001542141714">4294967295</strong>.</p>
</td> </td>
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.13.2.4.1.3 "><p id="asm_01_0050__p19848684618">1-2147483647</p> <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.13.2.4.1.3 "><p id="asm_01_0050__p19848684618">1-4294967295</p>
</td> </td>
</tr> </tr>
<tr id="asm_01_0050__row17984176114616"><td class="cellrowborder" valign="top" width="20.352035203520348%" headers="mcps1.3.1.3.2.13.2.4.1.1 "><p id="asm_01_0050__p89841861468">Maximum Connection Idle Period (s)</p> <tr id="asm_01_0050__row17984176114616"><td class="cellrowborder" valign="top" width="20.352035203520348%" headers="mcps1.3.1.3.2.13.2.4.1.1 "><p id="asm_01_0050__p89841861468">Maximum Connection Idle Period (s)</p>
@ -143,7 +143,7 @@
</td> </td>
<td class="cellrowborder" valign="top" width="46.31463146314631%" headers="mcps1.3.1.3.2.13.2.4.1.2 "><p id="asm_01_0050__p79854615461">Maximum number of retries of all service pods within a specified period. The default value is <strong id="asm_01_0050__b47711511121815">4294967295</strong>.</p> <td class="cellrowborder" valign="top" width="46.31463146314631%" headers="mcps1.3.1.3.2.13.2.4.1.2 "><p id="asm_01_0050__p79854615461">Maximum number of retries of all service pods within a specified period. The default value is <strong id="asm_01_0050__b47711511121815">4294967295</strong>.</p>
</td> </td>
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.13.2.4.1.3 "><p id="asm_01_0050__p2985569460">1-2147483647</p> <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.13.2.4.1.3 "><p id="asm_01_0050__p2985569460">1-4294967295</p>
</td> </td>
</tr> </tr>
<tr id="asm_01_0050__row89859613462"><td class="cellrowborder" valign="top" width="20.352035203520348%" headers="mcps1.3.1.3.2.13.2.4.1.1 "><p id="asm_01_0050__p1698516634615">Maximum Number of Requests Per Connection</p> <tr id="asm_01_0050__row89859613462"><td class="cellrowborder" valign="top" width="20.352035203520348%" headers="mcps1.3.1.3.2.13.2.4.1.1 "><p id="asm_01_0050__p1698516634615">Maximum Number of Requests Per Connection</p>
@ -173,7 +173,7 @@
</td> </td>
<td class="cellrowborder" valign="top" width="46.31463146314631%" headers="mcps1.3.1.3.2.18.2.4.1.2 "><p id="asm_01_0050__p20900174285110">Number of consecutive errors in a specified time period. If the number of consecutive errors exceeds the parameter value, the pod will be ejected. The default value is <strong id="asm_01_0050__b17615054111613">5</strong>.</p> <td class="cellrowborder" valign="top" width="46.31463146314631%" headers="mcps1.3.1.3.2.18.2.4.1.2 "><p id="asm_01_0050__p20900174285110">Number of consecutive errors in a specified time period. If the number of consecutive errors exceeds the parameter value, the pod will be ejected. The default value is <strong id="asm_01_0050__b17615054111613">5</strong>.</p>
</td> </td>
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.18.2.4.1.3 "><p id="asm_01_0050__p7900124265118">1-2147483647</p> <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.2.18.2.4.1.3 "><p id="asm_01_0050__p7900124265118">1-4294967295</p>
</td> </td>
</tr> </tr>
<tr id="asm_01_0050__row090044235117"><td class="cellrowborder" valign="top" width="20.352035203520348%" headers="mcps1.3.1.3.2.18.2.4.1.1 "><p id="asm_01_0050__p13900242175114">Base Ejection Time (s)</p> <tr id="asm_01_0050__row090044235117"><td class="cellrowborder" valign="top" width="20.352035203520348%" headers="mcps1.3.1.3.2.18.2.4.1.1 "><p id="asm_01_0050__p13900242175114">Base Ejection Time (s)</p>

15
docs/asm/umn/asm_01_0051.html
View File

@ -1,15 +0,0 @@
<a name="asm_01_0051"></a><a name="asm_01_0051"></a>
<h1 class="topictitle1">Viewing Traffic Monitoring</h1>
<div id="body0000001083395158"><div class="section" id="asm_01_0051__section8518326102519"><h4 class="sectiontitle">Scenario</h4><p id="asm_01_0051__p948651862318">In the traffic management window, you can view the traffic monitoring data of the last hour, including RPS, success rate, and request latency.</p>
</div>
<div class="section" id="asm_01_0051__section127451436172517"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0051__ol20995184283915"><li id="asm_01_0051__li18456728440"><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_0051__li2307164162712"><span>In the navigation pane, choose <strong id="asm_01_0051__b175996716557">Service Management</strong>. In the upper right corner of the list, select the namespace that your services belong to.</span></li><li id="asm_01_0051__li14961452719"><span>Locate the target service and click <strong id="asm_01_0051__b77661216173511">Manage Traffic</strong> in the <strong id="asm_01_0051__b877220163358">Operation</strong> column. In the window that slides out from the right, view the traffic monitoring data of the last hour.</span><p><div class="fignone" id="asm_01_0051__fig13667115162916"><span class="figcap"><b>Figure 1 </b>Traffic monitoring</span><br><span><img id="asm_01_0051__image86673516296" src="en-us_image_0000001280416429.png"></span></div>
</p></li><li id="asm_01_0051__li148811724162819"><span>After real-time monitoring is enabled, data is dynamically refreshed every minute.</span></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0085.html">Traffic Management</a></div>
</div>
</div>

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

@ -1,7 +1,7 @@
<a name="asm_01_0052"></a><a name="asm_01_0052"></a> <a name="asm_01_0052"></a><a name="asm_01_0052"></a>
<h1 class="topictitle1">Changing a Traffic Policy</h1> <h1 class="topictitle1">Changing a Traffic Policy</h1>
<div id="body0000001083235534"><div class="section" id="asm_01_0052__section18497174482412"><h4 class="sectiontitle">Scenario</h4><p id="asm_01_0052__p126341845122418">You can change the settings of a configured traffic policy. For example, you can change the load balancing algorithm from <span class="parmvalue" id="asm_01_0052__parmvalue227718914386"><b>Round robin</b></span> to <span class="parmvalue" id="asm_01_0052__parmvalue3283179183810"><b>Random</b></span>.</p> <div id="body0000001083235534"><div class="section" id="asm_01_0052__section18497174482412"><h4 class="sectiontitle">Scenarios</h4><p id="asm_01_0052__p126341845122418">You can change the settings of a configured traffic policy. For example, you can change the load balancing algorithm from <span class="parmvalue" id="asm_01_0052__parmvalue227718914386"><b>Round robin</b></span> to <span class="parmvalue" id="asm_01_0052__parmvalue3283179183810"><b>Random</b></span>.</p>
</div> </div>
<div class="section" id="asm_01_0052__section2340125512411"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0052__ol75076624518"><li id="asm_01_0052__li359213189212"><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_0052__li34261121123718"><span>In the navigation pane, choose <span class="uicontrol" id="asm_01_0052__uicontrol10670066152041"><b>Service Management</b></span>. Locate the service whose traffic policy needs to be modified and click <span class="uicontrol" id="asm_01_0052__uicontrol159025963452041"><b>Manage Traffic</b></span> in the <strong id="asm_01_0052__b149172189152041">Operation</strong> column. In the window that slides out from the right, modify traffic policies.</span></li></ol> <div class="section" id="asm_01_0052__section2340125512411"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0052__ol75076624518"><li id="asm_01_0052__li359213189212"><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_0052__li34261121123718"><span>In the navigation pane, choose <span class="uicontrol" id="asm_01_0052__uicontrol10670066152041"><b>Service Management</b></span>. Locate the service whose traffic policy needs to be modified and click <span class="uicontrol" id="asm_01_0052__uicontrol159025963452041"><b>Manage Traffic</b></span> in the <strong id="asm_01_0052__b149172189152041">Operation</strong> column. In the window that slides out from the right, modify traffic policies.</span></li></ol>
</div> </div>

4
docs/asm/umn/asm_01_0056.html
View File

@ -7,8 +7,8 @@
</div> </div>
<div class="section" id="asm_01_0056__section15169750114920"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0056__ol4817103154612"><li id="asm_01_0056__li1433614120526"><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_0056__li218910061117"><span>In the navigation pane on the left, choose <strong id="asm_01_0056__b766458229102515">Gateway Management</strong> and click <strong id="asm_01_0056__b966014901102515">Add Gateway</strong>.</span></li><li id="asm_01_0056__li65921447162912"><span>Configure the following parameters.</span><p><ul id="asm_01_0056__ul1359211474297"><li id="asm_01_0056__li139001750192815"><strong id="asm_01_0056__b3657180102915">Gateway Name</strong><p id="asm_01_0056__p15441558132814">Enter a gateway name. Enter 4 to 59 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.</p> <div class="section" id="asm_01_0056__section15169750114920"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0056__ol4817103154612"><li id="asm_01_0056__li1433614120526"><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_0056__li218910061117"><span>In the navigation pane on the left, choose <strong id="asm_01_0056__b766458229102515">Gateway Management</strong> and click <strong id="asm_01_0056__b966014901102515">Add Gateway</strong>.</span></li><li id="asm_01_0056__li65921447162912"><span>Configure the following parameters.</span><p><ul id="asm_01_0056__ul1359211474297"><li id="asm_01_0056__li139001750192815"><strong id="asm_01_0056__b3657180102915">Gateway Name</strong><p id="asm_01_0056__p15441558132814">Enter a gateway name. Enter 4 to 59 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.</p>
</li><li id="asm_01_0056__li205096299321"><strong id="asm_01_0056__b1576717357329">Cluster</strong><p id="asm_01_0056__p1719143716324">Select the cluster to which the gateway belongs.</p> </li><li id="asm_01_0056__li205096299321"><strong id="asm_01_0056__b1576717357329">Cluster</strong><p id="asm_01_0056__p1719143716324">Select the cluster to which the gateway belongs.</p>
</li><li id="asm_01_0056__li1627847173510"><strong id="asm_01_0056__b72023510139">Load Balancer</strong><ul id="asm_01_0056__ul198721433124110"><li id="asm_01_0056__li1373914385357">Gateways use shared load balancers of ELB for the access over both public and private IPv4 networks.</li></ul> </li><li id="asm_01_0056__li1627847173510"><strong id="asm_01_0056__b72023510139">Load Balancer</strong><ul id="asm_01_0056__ul198721433124110"><li id="asm_01_0056__li1373914385357">Gateways use shared and dedicated load balancers of ELB for the access over both public and private IPv4 networks.</li></ul>
</li><li id="asm_01_0056__li137621212344"><strong id="asm_01_0056__b82802248345">Listener</strong><p id="asm_01_0056__p103982038193113">Gateways configure a listener for the load balancer, which listens to requests from the load balancer and distributes traffic.</p> </li><li id="asm_01_0056__li137621212344"><strong id="asm_01_0056__b196012994813">Access Entry</strong><p id="asm_01_0056__p103982038193113">Gateways configure a listener for the load balancer, which listens to requests from the load balancer and distributes traffic.</p>
<ul id="asm_01_0056__ul1776173623113"><li id="asm_01_0056__li196722183918"><strong id="asm_01_0056__b1876120366312">External Protocol</strong><p id="asm_01_0056__p12761163618313">Select one to match the protocol type of your service. <strong id="asm_01_0056__b1196471084102515">HTTP</strong>, <strong id="asm_01_0056__b727748035102515">gRPC</strong>, <strong id="asm_01_0056__b2109712016102515">TCP</strong>, <strong id="asm_01_0056__b807938525102515">TLS</strong>, and <strong id="asm_01_0056__b1914909991102515">HTTPS</strong> are supported.</p> <ul id="asm_01_0056__ul1776173623113"><li id="asm_01_0056__li196722183918"><strong id="asm_01_0056__b1876120366312">External Protocol</strong><p id="asm_01_0056__p12761163618313">Select one to match the protocol type of your service. <strong id="asm_01_0056__b1196471084102515">HTTP</strong>, <strong id="asm_01_0056__b727748035102515">gRPC</strong>, <strong id="asm_01_0056__b2109712016102515">TCP</strong>, <strong id="asm_01_0056__b807938525102515">TLS</strong>, and <strong id="asm_01_0056__b1914909991102515">HTTPS</strong> are supported.</p>
</li><li id="asm_01_0056__li776153618311"><strong id="asm_01_0056__b15761136173112">External Port</strong><p id="asm_01_0056__p17761036193110">Enter the port number exposed in the Load Balancer Service address. The port number can be specified randomly.</p> </li><li id="asm_01_0056__li776153618311"><strong id="asm_01_0056__b15761136173112">External Port</strong><p id="asm_01_0056__p17761036193110">Enter the port number exposed in the Load Balancer Service address. The port number can be specified randomly.</p>
</li><li id="asm_01_0056__li10761203617318"><strong id="asm_01_0056__b2076153618317">TLS Termination</strong><p id="asm_01_0056__p894180479">If <strong id="asm_01_0056__b1792295615209">External Protocol</strong> is <strong id="asm_01_0056__b1068528152117">HTTPS</strong>, <strong id="asm_01_0056__b1655716263218">TLS Termination</strong> is enabled and cannot be disabled.</p> </li><li id="asm_01_0056__li10761203617318"><strong id="asm_01_0056__b2076153618317">TLS Termination</strong><p id="asm_01_0056__p894180479">If <strong id="asm_01_0056__b1792295615209">External Protocol</strong> is <strong id="asm_01_0056__b1068528152117">HTTPS</strong>, <strong id="asm_01_0056__b1655716263218">TLS Termination</strong> is enabled and cannot be disabled.</p>

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

@ -1,7 +1,7 @@
<a name="asm_01_0057"></a><a name="asm_01_0057"></a> <a name="asm_01_0057"></a><a name="asm_01_0057"></a>
<h1 class="topictitle1">Adding a Route</h1> <h1 class="topictitle1">Adding a Route</h1>
<div id="body0000001121400726"><div class="section" id="asm_01_0057__section195155335313"><h4 class="sectiontitle">Scenario</h4><p id="asm_01_0057__p931218541531">You can add multiple routes and configure multiple forwarding policies for a created gateway.</p> <div id="body0000001121400726"><div class="section" id="asm_01_0057__section195155335313"><h4 class="sectiontitle">Scenarios</h4><p id="asm_01_0057__p931218541531">You can add multiple routes and configure multiple forwarding policies for a created gateway.</p>
</div> </div>
<div class="section" id="asm_01_0057__section8243022955"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0057__ol4817103154612"><li id="asm_01_0057__li218910061117"><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_0057__li4563349450"><span>In the navigation pane on the left, choose <strong id="asm_01_0057__b1723779989102359">Gateway Management</strong>, select the target gateway, click <span class="uicontrol" id="asm_01_0057__uicontrol1443280921102359"><b>Add Route</b></span> in the <strong id="asm_01_0057__b1193311901102359">Operation</strong> column, and configure the following parameters:</span><p><ul id="asm_01_0057__ul43052021171916"><li id="asm_01_0057__li103041421111912"><strong id="asm_01_0057__b20304152120193">Domain Name</strong><p id="asm_01_0057__p1330482114196">Enter the external domain name of the service. If this parameter is left blank, the IP address of the load balancer is used by default. If you enable TLS termination, enter a domain name configured in the certificate for SNI domain name verification.</p> <div class="section" id="asm_01_0057__section8243022955"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0057__ol4817103154612"><li id="asm_01_0057__li218910061117"><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_0057__li4563349450"><span>In the navigation pane on the left, choose <strong id="asm_01_0057__b1723779989102359">Gateway Management</strong>, select the target gateway, click <span class="uicontrol" id="asm_01_0057__uicontrol1443280921102359"><b>Add Route</b></span> in the <strong id="asm_01_0057__b1193311901102359">Operation</strong> column, and configure the following parameters:</span><p><ul id="asm_01_0057__ul43052021171916"><li id="asm_01_0057__li103041421111912"><strong id="asm_01_0057__b20304152120193">Domain Name</strong><p id="asm_01_0057__p1330482114196">Enter the external domain name of the service. If this parameter is left blank, the IP address of the load balancer is used by default. If you enable TLS termination, enter a domain name configured in the certificate for SNI domain name verification.</p>
</li><li id="asm_01_0057__li1230512118195"><strong id="asm_01_0057__b3304192131916">URL Matching Rule</strong><ul id="asm_01_0057__ul43041021141915"><li id="asm_01_0057__li193041021111910"><strong id="asm_01_0057__b962008790102359">Prefix</strong>: A URL can be accessed if its prefix is the same as that you configure. For example, <strong id="asm_01_0057__b518106701102359">/healthz/v1</strong> and <strong id="asm_01_0057__b1301388330102359">/healthz/v2</strong>.</li><li id="asm_01_0057__li2304821181912"><strong id="asm_01_0057__b1070295332113">Exact</strong>: Only the URL that fully matches the values you set can be accessed. For example, if the URL is set to <strong id="asm_01_0057__b1560656592102359">/healthz</strong>, only <strong id="asm_01_0057__b592325887102359">/healthz</strong> can be accessed.</li></ul> </li><li id="asm_01_0057__li1230512118195"><strong id="asm_01_0057__b3304192131916">URL Matching Rule</strong><ul id="asm_01_0057__ul43041021141915"><li id="asm_01_0057__li193041021111910"><strong id="asm_01_0057__b962008790102359">Prefix</strong>: A URL can be accessed if its prefix is the same as that you configure. For example, <strong id="asm_01_0057__b518106701102359">/healthz/v1</strong> and <strong id="asm_01_0057__b1301388330102359">/healthz/v2</strong>.</li><li id="asm_01_0057__li2304821181912"><strong id="asm_01_0057__b1070295332113">Exact</strong>: Only the URL that fully matches the values you set can be accessed. For example, if the URL is set to <strong id="asm_01_0057__b1560656592102359">/healthz</strong>, only <strong id="asm_01_0057__b592325887102359">/healthz</strong> can be accessed.</li></ul>

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

@ -6,7 +6,7 @@
<p id="asm_01_0066__p0468101021218"><strong id="asm_01_0066__b1009304413102627">&lt;protocol&gt;</strong> can be <strong id="asm_01_0066__b2134182545102627">http</strong>, <strong id="asm_01_0066__b426502840102627">tcp</strong>, or <strong id="asm_01_0066__b1310352250102627">grpc</strong>. Istio provides routing capabilities based on protocols defined on ports. For example, <strong id="asm_01_0066__b413874376102627">name: http-service0</strong> and <strong id="asm_01_0066__b1009174383102627">name: tcp</strong> are valid port names, while <strong id="asm_01_0066__b1702190975102627">name: httpforecast</strong> is not.</p> <p id="asm_01_0066__p0468101021218"><strong id="asm_01_0066__b1009304413102627">&lt;protocol&gt;</strong> can be <strong id="asm_01_0066__b2134182545102627">http</strong>, <strong id="asm_01_0066__b426502840102627">tcp</strong>, or <strong id="asm_01_0066__b1310352250102627">grpc</strong>. Istio provides routing capabilities based on protocols defined on ports. For example, <strong id="asm_01_0066__b413874376102627">name: http-service0</strong> and <strong id="asm_01_0066__b1009174383102627">name: tcp</strong> are valid port names, while <strong id="asm_01_0066__b1702190975102627">name: httpforecast</strong> is not.</p>
<p id="asm_01_0066__p122601816122117">If the Service port name is invalid, this item is abnormal.</p> <p id="asm_01_0066__p122601816122117">If the Service port name is invalid, this item is abnormal.</p>
</div> </div>
<div class="section" id="asm_01_0066__section727870104217"><h4 class="sectiontitle">Rectification Guide</h4><ol id="asm_01_0066__ol1727810104213"><li id="asm_01_0066__li102781407429"><span>Log in to the CCE console.</span></li><li id="asm_01_0066__li52781302422"><span>Click the cluster name to go to the cluster console. In the navigation pane on the left, choose <strong id="asm_01_0066__b1122812414343">Services &amp; Ingresses</strong>. On the <strong id="asm_01_0066__b8234191818357">Services</strong> tab, search for the Service by cluster name and namespace and click <strong id="asm_01_0066__b993119232010">Edit YAML</strong>. Then, view the Service protocol and add a protocol type before the service name.</span><p><p id="asm_01_0066__p142784012424"><span><img id="asm_01_0066__image112786012424" src="en-us_image_0000001254992703.png"></span></p> <div class="section" id="asm_01_0066__section727870104217"><h4 class="sectiontitle">Rectification Guide</h4><ol id="asm_01_0066__ol1727810104213"><li id="asm_01_0066__li102781407429"><span>Log in to the CCE console and click the cluster name to go to the cluster console.</span></li><li id="asm_01_0066__li52781302422"><span>In the navigation pane, choose <strong id="asm_01_0066__b236423932019">Services &amp; Ingresses</strong>. Click the <strong id="asm_01_0066__b474713414458">Service</strong> tab, search for the Service by cluster name and namespace, and click <strong id="asm_01_0066__b862745419249">Edit YAML</strong>. Then, view the Service protocol and add a protocol type before the Service name.</span><p><p id="asm_01_0066__p142784012424"><span><img id="asm_01_0066__image112786012424" src="en-us_image_0000001254992703.png"></span></p>
</p></li><li id="asm_01_0066__li9278600425"><span>Click <strong id="asm_01_0066__b1508075284102627">OK</strong>.</span></li></ol> </p></li><li id="asm_01_0066__li9278600425"><span>Click <strong id="asm_01_0066__b1508075284102627">OK</strong>.</span></li></ol>
</div> </div>
</div> </div>

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

@ -3,7 +3,7 @@
<h1 class="topictitle1">The Service Selector Cannot Contain version Labels</h1> <h1 class="topictitle1">The Service Selector Cannot Contain version Labels</h1>
<div id="body0000001175892785"><div class="section" id="asm_01_0067__section53791230142415"><h4 class="sectiontitle">Description</h4><p id="asm_01_0067__p18675632152410">The <strong id="asm_01_0067__b9712182727">spec.selector</strong> of a Service cannot be labeled with <strong id="asm_01_0067__b127131229217">version</strong>. Otherwise, this item is abnormal.</p> <div id="body0000001175892785"><div class="section" id="asm_01_0067__section53791230142415"><h4 class="sectiontitle">Description</h4><p id="asm_01_0067__p18675632152410">The <strong id="asm_01_0067__b9712182727">spec.selector</strong> of a Service cannot be labeled with <strong id="asm_01_0067__b127131229217">version</strong>. Otherwise, this item is abnormal.</p>
</div> </div>
<div class="section" id="asm_01_0067__section1746811221448"><h4 class="sectiontitle">Rectification Guide</h4><ol id="asm_01_0067__ol2046892274413"><li id="asm_01_0067__li194682224444"><span>Log in to the CCE console.</span></li><li id="asm_01_0067__li134681722134416"><span>Click the cluster name to go to the cluster console. In the navigation pane on the left, choose <strong id="asm_01_0067__b8572121620382">Services &amp; Ingresses</strong>. On the <strong id="asm_01_0067__b1457214161384">Services</strong> tab, search for the Service by cluster name and namespace and click <strong id="asm_01_0067__b05722016133815">Edit YAML</strong>. Then, view the selector (specified by <strong id="asm_01_0067__b7653142303911">spec.selector</strong>) of the Service and delete the <strong id="asm_01_0067__b4417142944010">version</strong> label.</span><p><p id="asm_01_0067__p74682223442"><span><img id="asm_01_0067__image11468192210442" src="en-us_image_0000001254992865.png"></span></p> <div class="section" id="asm_01_0067__section1746811221448"><h4 class="sectiontitle">Rectification Guide</h4><ol id="asm_01_0067__ol2046892274413"><li id="asm_01_0067__li194682224444"><span>Log in to the CCE console and click the cluster name to go to the cluster console.</span></li><li id="asm_01_0067__li134681722134416"><span>In the navigation pane, choose <strong id="asm_01_0067__b1982141613293">Services &amp; Ingresses</strong>. Click the <strong id="asm_01_0067__b13800823104714">Service</strong> tab, search for the Service by cluster name and namespace, click <strong id="asm_01_0067__b1641517485317">Edit YAML</strong>. Then, view <strong id="asm_01_0067__b12282102411321">spec.selector</strong> and delete the <strong id="asm_01_0067__b27141245113215">version</strong> label.</span><p><p id="asm_01_0067__p74682223442"><span><img id="asm_01_0067__image11468192210442" src="en-us_image_0000001254992865.png"></span></p>
</p></li></ol> </p></li></ol>
</div> </div>
</div> </div>

17
docs/asm/umn/asm_01_0082.html Normal file
View File

@ -0,0 +1,17 @@
<a name="asm_01_0082"></a><a name="asm_01_0082"></a>
<h1 class="topictitle1">Upgrades</h1>
<div id="body0000001204311324"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="asm_01_0095.html">Features in v1.15</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="asm_01_0124.html">Features in v1.18</a></strong><br>
</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0038.html">Mesh Configuration</a></div>
</div>
</div>

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

@ -0,0 +1,84 @@
<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_0085.html
View File

@ -8,8 +8,6 @@
</li> </li>
<li class="ulchildlink"><strong><a href="asm_01_0050.html">Configuring a Traffic Policy</a></strong><br> <li class="ulchildlink"><strong><a href="asm_01_0050.html">Configuring a Traffic Policy</a></strong><br>
</li> </li>
<li class="ulchildlink"><strong><a href="asm_01_0051.html">Viewing Traffic Monitoring</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="asm_01_0052.html">Changing a Traffic Policy</a></strong><br> <li class="ulchildlink"><strong><a href="asm_01_0052.html">Changing a Traffic Policy</a></strong><br>
</li> </li>
</ul> </ul>

12
docs/asm/umn/asm_01_0086.html
View File

@ -1,15 +1,15 @@
<a name="asm_01_0086"></a><a name="asm_01_0086"></a> <a name="asm_01_0086"></a><a name="asm_01_0086"></a>
<h1 class="topictitle1">Uninstalling a Mesh</h1> <h1 class="topictitle1">Uninstalling a Service Mesh</h1>
<div id="body0000001210431052"><div class="section" id="asm_01_0086__en-us_topic_0000001233246629_section7549333407"><h4 class="sectiontitle">Scenario</h4><p id="asm_01_0086__en-us_topic_0000001233246629_p13506115164417">When a mesh is no longer needed, you can uninstall it.</p> <div id="body0000001210431052"><div class="section" id="asm_01_0086__en-us_topic_0000001233246629_section7549333407"><h4 class="sectiontitle">Scenarios</h4><p id="asm_01_0086__en-us_topic_0000001233246629_p13506115164417">If you no longer need a service mesh, you can uninstall it.</p>
</div> </div>
<div class="section" id="asm_01_0086__en-us_topic_0000001233246629_section1099812136478"><h4 class="sectiontitle">Constraints</h4><ul id="asm_01_0086__en-us_topic_0000001233246629_ul9996319104819"><li id="asm_01_0086__en-us_topic_0000001233246629_li56665210482">To uninstall a mesh in which a grayscale release task is running, you need to complete the grayscale release first.</li><li id="asm_01_0086__en-us_topic_0000001233246629_li7988148121612">You need to ensure available nodes exist in the clusters for running the cleanup task to avoid uninstallation failure.</li></ul> <div class="section" id="asm_01_0086__en-us_topic_0000001233246629_section1099812136478"><h4 class="sectiontitle">Constraints</h4><ul id="asm_01_0086__en-us_topic_0000001233246629_ul9996319104819"><li id="asm_01_0086__en-us_topic_0000001233246629_li56665210482">To uninstall a service mesh in which a grayscale release task is running, you need to complete the grayscale release first.</li><li id="asm_01_0086__en-us_topic_0000001233246629_li7988148121612">You need to ensure available nodes exist in the clusters for running the cleanup task to avoid uninstallation failure.</li></ul>
</div> </div>
<div class="section" id="asm_01_0086__section66831866261"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0086__en-us_topic_0000001233246629_ol13341319164012"><li id="asm_01_0086__li2790345102618"><span>Log in to the ASM console.</span></li><li id="asm_01_0086__en-us_topic_0000001233246629_li434101915404"><span>Click <span><img id="asm_01_0086__image19970230134618" src="en-us_image_0000001255111219.png"></span> in the target mesh.</span></li><li id="asm_01_0086__en-us_topic_0000001233246629_li1424023724312"><span>On the dialogue box displayed, select whether to restart existing services and read the precautions.</span><p><p id="asm_01_0086__en-us_topic_0000001233246629_p7846131215117">By default, existing services are not restarted during the uninstallation. The injected istio-poxy sidecar is removed only after the existing services are restarted. If you want to restart the services, select <strong id="asm_01_0086__b19442022154616">Yes</strong>. Restarting the services will interrupt your services temporarily.</p> <div class="section" id="asm_01_0086__section66831866261"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0086__en-us_topic_0000001233246629_ol13341319164012"><li id="asm_01_0086__li2790345102618"><span>Log in to the ASM console.</span></li><li id="asm_01_0086__en-us_topic_0000001233246629_li434101915404"><span>Click <span><img id="asm_01_0086__image19970230134618" src="en-us_image_0000001255111219.png"></span> in the service mesh.</span></li><li id="asm_01_0086__en-us_topic_0000001233246629_li1424023724312"><span>On the dialogue box displayed, select whether to restart existing services and read the precautions.</span><p><p id="asm_01_0086__en-us_topic_0000001233246629_p7846131215117">By default, existing services are not restarted during the uninstallation. The injected istio-poxy sidecar is removed only after the existing services are restarted. If you want to restart the services, select <strong id="asm_01_0086__b19442022154616">Yes</strong>. Restarting the services will interrupt your services temporarily.</p>
<div class="note" id="asm_01_0086__note1480104418566"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0086__p8801164415563">You are advised to restart existing services to avoid the following exceptions: If the cluster enables the current mesh again after it is uninstalled, gateway access failed.</p> <div class="note" id="asm_01_0086__note1480104418566"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0086__p8801164415563">You are advised to restart existing services to avoid the following exceptions: If the cluster enables the current mesh again after it is uninstalled, gateway access failed.</p>
</div></div> </div></div>
<ul id="asm_01_0086__en-us_topic_0000001233246629_ul208862207544"><li id="asm_01_0086__en-us_topic_0000001233246629_li38863209544">Uninstalling a mesh will uninstall its control plane components and data plane sidecars.</li><li id="asm_01_0086__en-us_topic_0000001233246629_li198861320195413">After the uninstallation, service gateways of applications cannot be used. Configure Services for external access to applications.<p id="asm_01_0086__en-us_topic_0000001233246629_p2075734025514"><a name="asm_01_0086__en-us_topic_0000001233246629_li198861320195413"></a><a name="en-us_topic_0000001233246629_li198861320195413"></a>To update the external access mode, log in to the CCE console and click the cluster name to go to the cluster console. Then, choose <strong id="asm_01_0086__b6890105019318">Services &amp; Ingresses</strong> &gt; <strong id="asm_01_0086__b7901253183119">Services</strong>.</p> <ul id="asm_01_0086__en-us_topic_0000001233246629_ul208862207544"><li id="asm_01_0086__en-us_topic_0000001233246629_li38863209544">Uninstalling a service mesh will uninstall its control plane components and data plane sidecars.</li><li id="asm_01_0086__en-us_topic_0000001233246629_li198861320195413">After the uninstallation, service gateways of applications cannot be used. Configure Services for external access to applications.<p id="asm_01_0086__en-us_topic_0000001233246629_p2075734025514"><a name="asm_01_0086__en-us_topic_0000001233246629_li198861320195413"></a><a name="en-us_topic_0000001233246629_li198861320195413"></a>To update the external access mode, log in to the CCE console and click the cluster name to go to the cluster console. Then, choose <strong id="asm_01_0086__b6890105019318">Services &amp; Ingresses</strong> &gt; <strong id="asm_01_0086__b7901253183119">Services</strong>.</p>
</li><li id="asm_01_0086__en-us_topic_0000001233246629_li338853717588">Uninstalling a mesh will delete the labels of the mesh exclusive nodes, but the Istio-master node will not be automatically deleted. You can delete it on the CCE console.<p id="asm_01_0086__en-us_topic_0000001233246629_p0805412135912"><a name="asm_01_0086__en-us_topic_0000001233246629_li338853717588"></a><a name="en-us_topic_0000001233246629_li338853717588"></a>To view node information, log in to the CCE console and click the cluster name to go to the cluster console. In the navigation pane on the left, choose <strong id="asm_01_0086__b10143645153018">Nodes</strong> &gt; <strong id="asm_01_0086__b1894316482307">Nodes</strong>.</p> </li><li id="asm_01_0086__en-us_topic_0000001233246629_li338853717588">Uninstalling a service mesh will delete the labels of the Istio exclusive nodes, but the Istio-master node will not be automatically deleted. You can delete it on the CCE console.<p id="asm_01_0086__en-us_topic_0000001233246629_p0805412135912"><a name="asm_01_0086__en-us_topic_0000001233246629_li338853717588"></a><a name="en-us_topic_0000001233246629_li338853717588"></a>To view node information, log in to the CCE console and click the cluster name to go to the cluster console. In the navigation pane on the left, choose <strong id="asm_01_0086__b10143645153018">Nodes</strong> &gt; <strong id="asm_01_0086__b1894316482307">Nodes</strong>.</p>
</li></ul> </li></ul>
</p></li></ol> </p></li></ol>
</div> </div>

12
docs/asm/umn/asm_01_0095.html Normal file
View File

@ -0,0 +1,12 @@
<a name="asm_01_0095"></a><a name="asm_01_0095"></a>
<h1 class="topictitle1">Features in v1.15</h1>
<div id="body0000001509781437"><ul id="asm_01_0095__ul9461425169"><li id="asm_01_0095__li114615221619">Istio 1.15.7 is supported.</li><li id="asm_01_0095__li572016471613">CCE Turbo clusters v1.21, v1.23, v1.25, and v1.27 are supported.</li><li id="asm_01_0095__li24721410161617">CCE clusters v1.21, v1.23, v1.25, and v1.27 are supported.</li><li id="asm_01_0095__li9405152166">Security vulnerabilities such as CVE-2023-44487, CVE-2023-39325 and CVE-2023-27487 are fixed.</li></ul>
<p id="asm_01_0095__p124581357171516">For details, visit <a href="https://istio.io/latest/news/releases/1.15.x/announcing-1.15.7/" target="_blank" rel="noopener noreferrer">https://istio.io/latest/news/releases/1.15.x/announcing-1.15.7/</a>.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0082.html">Upgrades</a></div>
</div>
</div>

4
docs/asm/umn/asm_01_0097.html
View File

@ -2,7 +2,7 @@
<h1 class="topictitle1">Authenticating JWT Requests on the Ingress Gateway Using ASM</h1> <h1 class="topictitle1">Authenticating JWT Requests on the Ingress Gateway Using ASM</h1>
<div id="body0000001476967356"><p id="asm_01_0097__p93564210389">This section describes how to authenticate JWT requests on the ingress gateway using ASM to ensure that users access services through the ingress gateway with a reliable access token.</p> <div id="body0000001476967356"><p id="asm_01_0097__p93564210389">This section describes how to authenticate JWT requests on the ingress gateway using ASM to ensure that users access services through the ingress gateway with a reliable access token.</p>
<div class="section" id="asm_01_0097__section3564173202917"><h4 class="sectiontitle">Preparations</h4><ol id="asm_01_0097__ol15987183732917"><li id="asm_01_0097__li5987183718296">A mesh of version 1.15 or 1.18 has been created.</li><li id="asm_01_0097__li1943518417306">The <strong id="asm_01_0097__b98651043464">httpbin</strong> service that passes the diagnosis exists in the mesh. The image is <strong id="asm_01_0097__b17441838124617">httpbin</strong>, the port protocol is <strong id="asm_01_0097__b3571124314612">HTTP</strong>, and the port number is <strong id="asm_01_0097__b171204715463">80</strong>.</li><li id="asm_01_0097__li14330133703019">An accessible gateway has been created for the <strong id="asm_01_0097__b1454812177479">httpbin</strong> service in the mesh.</li></ol> <div class="section" id="asm_01_0097__section3564173202917"><h4 class="sectiontitle">Preparations</h4><ol id="asm_01_0097__ol15987183732917"><li id="asm_01_0097__li5987183718296">A service mesh of version 1.15 or 1.18 has been created.</li><li id="asm_01_0097__li1943518417306">The <strong id="asm_01_0097__b98651043464">httpbin</strong> service that passes the diagnosis exists in the mesh. The image is <strong id="asm_01_0097__b17441838124617">httpbin</strong>, the port protocol is <strong id="asm_01_0097__b3571124314612">HTTP</strong>, and the port number is <strong id="asm_01_0097__b171204715463">80</strong>.</li><li id="asm_01_0097__li14330133703019">An accessible gateway has been created for the <strong id="asm_01_0097__b1454812177479">httpbin</strong> service in the mesh.</li></ol>
</div> </div>
<div class="section" id="asm_01_0097__section112090163819"><h4 class="sectiontitle">Creating JWT Authentication</h4><ol id="asm_01_0097__ol1660199171718"><li id="asm_01_0097__li116016915174"><a name="asm_01_0097__li116016915174"></a><a name="li116016915174"></a><span>Create a JWK.</span><p><ol type="a" id="asm_01_0097__ol5148943182011"><li id="asm_01_0097__li10148154317206"><a name="asm_01_0097__li10148154317206"></a><a name="li10148154317206"></a>Visit <a href="https://jwt.io/" target="_blank" rel="noopener noreferrer">JWT tool website</a>, set <strong id="asm_01_0097__b18235153518488">Algorithm</strong> to <strong id="asm_01_0097__b2950153715489">RS512</strong>, and obtain the public key (PUBLIC KEY).<div class="fignone" id="asm_01_0097__fig9556762255"><span class="figcap"><b>Figure 1 </b>Generating a public key</span><br><span><img id="asm_01_0097__image755613642519" src="en-us_image_0000001476967692.png"></span></div> <div class="section" id="asm_01_0097__section112090163819"><h4 class="sectiontitle">Creating JWT Authentication</h4><ol id="asm_01_0097__ol1660199171718"><li id="asm_01_0097__li116016915174"><a name="asm_01_0097__li116016915174"></a><a name="li116016915174"></a><span>Create a JWK.</span><p><ol type="a" id="asm_01_0097__ol5148943182011"><li id="asm_01_0097__li10148154317206"><a name="asm_01_0097__li10148154317206"></a><a name="li10148154317206"></a>Visit <a href="https://jwt.io/" target="_blank" rel="noopener noreferrer">JWT tool website</a>, set <strong id="asm_01_0097__b18235153518488">Algorithm</strong> to <strong id="asm_01_0097__b2950153715489">RS512</strong>, and obtain the public key (PUBLIC KEY).<div class="fignone" id="asm_01_0097__fig9556762255"><span class="figcap"><b>Figure 1 </b>Generating a public key</span><br><span><img id="asm_01_0097__image755613642519" src="en-us_image_0000001476967692.png"></span></div>
</li><li id="asm_01_0097__li157481253202315">Select <strong id="asm_01_0097__b94991017154919">PEM-to-JWK (RSA Only)</strong> in the <a href="https://8gwifi.org/jwkconvertfunctions.jsp?spm=a2c4g.11186623.0.0.79074d9bGGmlXG&amp;file=jwkconvertfunctions.jsp" target="_blank" rel="noopener noreferrer">JWK to PEM Convertor online</a> tool, enter the public key obtained in the previous step, and click <strong id="asm_01_0097__b1367965506">submit</strong> to convert the public key into a JWK.<div class="fignone" id="asm_01_0097__fig9353553117"><span class="figcap"><b>Figure 2 </b>Converting the public key to a JWK</span><br><span><img id="asm_01_0097__image441354311" src="en-us_image_0000001477287480.png"></span></div> </li><li id="asm_01_0097__li157481253202315">Select <strong id="asm_01_0097__b94991017154919">PEM-to-JWK (RSA Only)</strong> in the <a href="https://8gwifi.org/jwkconvertfunctions.jsp?spm=a2c4g.11186623.0.0.79074d9bGGmlXG&amp;file=jwkconvertfunctions.jsp" target="_blank" rel="noopener noreferrer">JWK to PEM Convertor online</a> tool, enter the public key obtained in the previous step, and click <strong id="asm_01_0097__b1367965506">submit</strong> to convert the public key into a JWK.<div class="fignone" id="asm_01_0097__fig9353553117"><span class="figcap"><b>Figure 2 </b>Converting the public key to a JWK</span><br><span><img id="asm_01_0097__image441354311" src="en-us_image_0000001477287480.png"></span></div>
@ -45,7 +45,7 @@ date: Wed, 21 Sep 2022 03:29:31 GMT
server: istio-envoy server: istio-envoy
x-envoy-upstream-service-time: 6</pre> x-envoy-upstream-service-time: 6</pre>
</li></ol> </li></ol>
<p id="asm_01_0097__p163452113323">According to the preceding outputs, the request with the correct JWT token can access the service, and the request with an incorrect JWT token or without a JWT token cannot access the service, which indicate that the request identity authentication takes effect.</p> <p id="asm_01_0097__p163452113323">According to the preceding outputs, the request with the correct JWT token can access the service, and the request with an incorrect JWT token or without a JWT token cannot access the service. This means the request identity authentication takes effect.</p>
</p></li></ol> </p></li></ol>
</div> </div>
</div> </div>

20
docs/asm/umn/asm_01_0123.html
View File

@ -1,20 +0,0 @@
<a name="asm_01_0123"></a><a name="asm_01_0123"></a>
<h1 class="topictitle1">Service Mesh Extension</h1>
<div id="body0000001735894325"><p id="asm_01_0123__p165881813132813">Observability configuration includes access logs, application metrics, and traces of the current service mesh. You can enable application metric collection and access logging.</p>
<div class="note" id="asm_01_0123__note550441752819"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0123__p1850591782810">Tracing can be enabled only when a service mesh is created.</p>
</div></div>
<div class="section" id="asm_01_0123__section25119231362"><h4 class="sectiontitle">Constraints</h4><p id="asm_01_0123__p14955835664">Only Istio 1.18 or later can work with LTS to collect and store access logs. To enable access logging, install CCE Log-Agent on the <strong id="asm_01_0123__b180611013502">Add-ons</strong> page in advance.</p>
</div>
<div class="section" id="asm_01_0123__section33990233516"><h4 class="sectiontitle">Enabling Application Metrics</h4><ol id="asm_01_0123__ol1593715983510"><li id="asm_01_0123__li139376973512"><span>Log in to the ASM console.</span></li><li id="asm_01_0123__li5937796354"><span>Click the name of the service mesh to go to its details page.</span></li><li id="asm_01_0123__li79374912354"><span>In the navigation pane, choose <strong id="asm_01_0123__b1839933112714">Mesh Configuration</strong>. Then click the tab for displaying service mesh extension.</span></li><li id="asm_01_0123__li179377911352"><span>Enable application metrics, select an AOM instance, and click <strong id="asm_01_0123__b14965154084214">OK</strong>.</span></li></ol>
</div>
<div class="section" id="asm_01_0123__section163119494613"><h4 class="sectiontitle">Enabling Access Logging</h4><ol id="asm_01_0123__ol1131119492069"><li id="asm_01_0123__li1631013491365"><span>Log in to the ASM console.</span></li><li id="asm_01_0123__li1531010494612"><span>Click the name of the service mesh to go to its details page.</span></li><li id="asm_01_0123__li1531074916617"><span>In the navigation pane, choose <strong id="asm_01_0123__b394565251019">Mesh Configuration</strong>. Then click the tab for displaying service mesh extension.</span></li><li id="asm_01_0123__li183117498610"><span>Enable access logging, select the log group and log stream, and click <strong id="asm_01_0123__b1744441015274">OK</strong>.</span></li></ol>
</div>
<p id="asm_01_0123__p8060118"></p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0038.html">Mesh Configuration</a></div>
</div>
</div>

12
docs/asm/umn/asm_01_0124.html Normal file
View File

@ -0,0 +1,12 @@
<a name="asm_01_0124"></a><a name="asm_01_0124"></a>
<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>
<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 class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0082.html">Upgrades</a></div>
</div>
</div>

8
docs/asm/umn/asm_01_0133.html
View File

@ -1,11 +1,11 @@
<a name="asm_01_0133"></a><a name="asm_01_0133"></a> <a name="asm_01_0133"></a><a name="asm_01_0133"></a>
<h1 class="topictitle1">Mesh Events</h1> <h1 class="topictitle1">Service Mesh Events</h1>
<div id="body0000001698194042"><div class="section" id="asm_01_0133__en-us_topic_0000001245220449_section4882153517306"><h4 class="sectiontitle">Scenario</h4><p id="asm_01_0133__en-us_topic_0000001245220449_p6387194691713">ASM supports the event center, which allows you to query details about important operations such as mesh creation and deletion and gateway creation and deletion.</p> <div id="body0000001698194042"><div class="section" id="asm_01_0133__en-us_topic_0000001245220449_section4882153517306"><h4 class="sectiontitle">Scenarios</h4><p id="asm_01_0133__en-us_topic_0000001245220449_p6387194691713">ASM supports the event center, which allows you to query details about important operations such as service mesh creation and deletion and gateway creation and deletion.</p>
<div class="note" id="asm_01_0133__note198721932184717"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0133__p10331731132415">You can view events in a mesh of the Basic edition (1.15 or later).</p> <div class="note" id="asm_01_0133__note198721932184717"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0133__p10331731132415">You can view events in a Basic service mesh (based on Istio 1.15 or later).</p>
</div></div> </div></div>
</div> </div>
<div class="section" id="asm_01_0133__section655465134710"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0133__en-us_topic_0000001245220449_ol3932132211530"><li id="asm_01_0133__en-us_topic_0000001245220449_li3932122212534"><span>Log in to the ASM console and search for the mesh of the Basic edition by edition.</span></li><li id="asm_01_0133__en-us_topic_0000001245220449_li10538191319558"><span>Click <span><img id="asm_01_0133__image689423910493" src="en-us_image_0000001698197390.png"></span> in the upper right corner. In the window that slides out from the right, view mesh events.</span><p><p id="asm_01_0133__p1728984312421"></p> <div class="section" id="asm_01_0133__section655465134710"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0133__en-us_topic_0000001245220449_ol3932132211530"><li id="asm_01_0133__en-us_topic_0000001245220449_li3932122212534"><span>Log in to the ASM console and search for the Basic service mesh by edition.</span></li><li id="asm_01_0133__en-us_topic_0000001245220449_li10538191319558"><span>Click <span><img id="asm_01_0133__image689423910493" src="en-us_image_0000001698197390.png"></span> in the upper right corner. In the window that slides out from the right, view service mesh events.</span><p><p id="asm_01_0133__p1728984312421"></p>
</p></li></ol> </p></li></ol>
<p id="asm_01_0133__p539616711425"></p> <p id="asm_01_0133__p539616711425"></p>
</div> </div>

9
docs/asm/umn/asm_bestpractice_1009.html
View File

@ -1,10 +1,10 @@
<a name="asm_bestpractice_1009"></a><a name="asm_bestpractice_1009"></a> <a name="asm_bestpractice_1009"></a><a name="asm_bestpractice_1009"></a>
<h1 class="topictitle1">Creating a Service Mesh with IPv4/IPv6 Dual Stack Enabled</h1> <h1 class="topictitle1">How Do I Create a Service Mesh with IPv4/IPv6 Dual Stack Enabled</h1>
<div id="body0000001735119876"><p id="asm_bestpractice_1009__p1629514211458">You can create a CCE cluster with IPv4/IPv6 dual stack enabled and enable IPv4/IPv6 dual stack for the service mesh that the cluster is added to. IPv4/IPv6 dual stack allows services in the service mesh to use both IPv4 and IPv6 addresses for service-to-service interactions. After an IPv4/IPv6 dual-stack gateway is added for the service mesh, you can provide services for users using an IPv6 client. This section describes how you can create a service mesh with IPv4/IPv6 dual stack, so that services in the service mesh can communicate with each other using IPv6 addresses.</p> <div id="body0000001735119876"><p id="asm_bestpractice_1009__p1629514211458">You can create a CCE cluster with IPv4/IPv6 dual stack enabled and enable IPv4/IPv6 dual stack for the service mesh that the cluster is added to. IPv4/IPv6 dual stack allows services in the service mesh to use both IPv4 and IPv6 addresses for service-to-service interactions. After an IPv4/IPv6 dual-stack gateway is added for the service mesh, you can provide services for users using an IPv6 client. This section describes how you can create a service mesh with IPv4/IPv6 dual stack, so that services in the service mesh can communicate with each other using IPv6 addresses.</p>
<div class="section" id="asm_bestpractice_1009__section241033319520"><h4 class="sectiontitle">Application Scenarios</h4><ul id="asm_bestpractice_1009__ul1891110468467"><li id="asm_bestpractice_1009__li1191184617465">If an IPv6 address is required for service access and traffic management, you can enable IPv4/IPv6 dual stack.</li><li id="asm_bestpractice_1009__li162511452164617">If you provide services for users who use IPv6 clients, you can create a gateway for a service mesh with IPv4/IPv6 dual stack enabled.</li></ul> <div class="section" id="asm_bestpractice_1009__section241033319520"><h4 class="sectiontitle">Application Scenarios</h4><ul id="asm_bestpractice_1009__ul1891110468467"><li id="asm_bestpractice_1009__li1191184617465">If an IPv6 address is required for service access and traffic management, you can enable IPv4/IPv6 dual stack.</li><li id="asm_bestpractice_1009__li162511452164617">If you provide services for users who use IPv6 clients, you can create a gateway for a service mesh with IPv4/IPv6 dual stack enabled.</li></ul>
</div> </div>
<div class="section" id="asm_bestpractice_1009__section10909135625310"><h4 class="sectiontitle">Constraints</h4><ul id="asm_bestpractice_1009__ul89074563534"><li id="asm_bestpractice_1009__li490735665310">Constraints on enabling IPv4/IPv6 dual stack for a service mesh</li></ul> <div class="section" id="asm_bestpractice_1009__section10909135625310"><h4 class="sectiontitle">Constraints</h4><ul id="asm_bestpractice_1009__ul89074563534"><li id="asm_bestpractice_1009__li490735665310">Conditions for enabling IPv4/IPv6 dual stack for a service mesh</li></ul>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="asm_bestpractice_1009__table990895610539" frame="border" border="1" rules="all"><thead align="left"><tr id="asm_bestpractice_1009__row179081156175318"><th align="left" class="cellrowborder" valign="top" width="12.379999999999999%" id="mcps1.3.3.3.1.6.1.1"><p id="asm_bestpractice_1009__p89071156165312">Service Mesh Edition</p> <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="asm_bestpractice_1009__table990895610539" frame="border" border="1" rules="all"><thead align="left"><tr id="asm_bestpractice_1009__row179081156175318"><th align="left" class="cellrowborder" valign="top" width="12.379999999999999%" id="mcps1.3.3.3.1.6.1.1"><p id="asm_bestpractice_1009__p89071156165312">Service Mesh Edition</p>
</th> </th>
@ -32,7 +32,7 @@
</tbody> </tbody>
</table> </table>
</div> </div>
<ul id="asm_bestpractice_1009__ul17908756195318"><li id="asm_bestpractice_1009__li49081056125319">Constraints on creating an IPv4/IPv6 dual-stack gateway</li></ul> <ul id="asm_bestpractice_1009__ul17908756195318"><li id="asm_bestpractice_1009__li49081056125319">Conditions for creating an IPv4/IPv6 dual-stack gateway</li></ul>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="asm_bestpractice_1009__table69092056105316" frame="border" border="1" rules="all"><thead align="left"><tr id="asm_bestpractice_1009__row109093569534"><th align="left" class="cellrowborder" valign="top" width="12.379999999999999%" id="mcps1.3.3.5.1.6.1.1"><p id="asm_bestpractice_1009__p290975645312">Service Mesh Edition</p> <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="asm_bestpractice_1009__table69092056105316" frame="border" border="1" rules="all"><thead align="left"><tr id="asm_bestpractice_1009__row109093569534"><th align="left" class="cellrowborder" valign="top" width="12.379999999999999%" id="mcps1.3.3.5.1.6.1.1"><p id="asm_bestpractice_1009__p290975645312">Service Mesh Edition</p>
</th> </th>
@ -60,7 +60,8 @@
</tbody> </tbody>
</table> </table>
</div> </div>
<ul id="asm_bestpractice_1009__ul14909156105316"><li id="asm_bestpractice_1009__li5909356155310">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><li id="asm_bestpractice_1009__li149091556195310">IPv4/IPv6 dual stack is only available for service meshes of v1.18 or later, but it cannot be enabled for a service mesh that is upgraded to v1.18 or later.</li></ul> <ul id="asm_bestpractice_1009__ul55640515486"><li id="asm_bestpractice_1009__li1744055413210"><strong id="asm_bestpractice_1009__b191812273172">Enable IPv6</strong> is only available in Basic service meshes based on Istio 1.18 or later.</li></ul>
<ul id="asm_bestpractice_1009__ul14909156105316"><li id="asm_bestpractice_1009__li5909356155310">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><li id="asm_bestpractice_1009__li149091556195310">IPv4/IPv6 dual stack cannot be enabled for a service mesh whose Istio version is upgraded to 1.18 or later.</li></ul>
</div> </div>
<div class="section" id="asm_bestpractice_1009__section22981733145214"><h4 class="sectiontitle">Creating a Service Mesh with IPv6 Addresses</h4><ol id="asm_bestpractice_1009__ol19298733165212"><li id="asm_bestpractice_1009__li162971334529"><span>Log in to the ASM console, a service mesh, and configure the parameters as follows:</span><p><ul id="asm_bestpractice_1009__ul102971334524"><li id="asm_bestpractice_1009__li122971133185210"><strong id="asm_bestpractice_1009__b1875558867">Mesh Edition</strong>: Select <strong id="asm_bestpractice_1009__b1587615581168">Basic edition</strong>.</li><li id="asm_bestpractice_1009__li152975338522"><strong id="asm_bestpractice_1009__b14671113820712">Mesh Name</strong>: Enter a service mesh name.</li><li id="asm_bestpractice_1009__li18297113395211"><strong id="asm_bestpractice_1009__b117461951185">Istio Version</strong>: Select 1.18 or later.</li><li id="asm_bestpractice_1009__li102972033125213"><strong id="asm_bestpractice_1009__b51711227082">Enable IPv6</strong>: If this option is enabled, CCE clusters that meet the conditions will be displayed.</li></ul> <div class="section" id="asm_bestpractice_1009__section22981733145214"><h4 class="sectiontitle">Creating a Service Mesh with IPv6 Addresses</h4><ol id="asm_bestpractice_1009__ol19298733165212"><li id="asm_bestpractice_1009__li162971334529"><span>Log in to the ASM console, a service mesh, and configure the parameters as follows:</span><p><ul id="asm_bestpractice_1009__ul102971334524"><li id="asm_bestpractice_1009__li122971133185210"><strong id="asm_bestpractice_1009__b1875558867">Mesh Edition</strong>: Select <strong id="asm_bestpractice_1009__b1587615581168">Basic edition</strong>.</li><li id="asm_bestpractice_1009__li152975338522"><strong id="asm_bestpractice_1009__b14671113820712">Mesh Name</strong>: Enter a service mesh name.</li><li id="asm_bestpractice_1009__li18297113395211"><strong id="asm_bestpractice_1009__b117461951185">Istio Version</strong>: Select 1.18 or later.</li><li id="asm_bestpractice_1009__li102972033125213"><strong id="asm_bestpractice_1009__b51711227082">Enable IPv6</strong>: If this option is enabled, CCE clusters that meet the conditions will be displayed.</li></ul>
<p id="asm_bestpractice_1009__p6297533195217"></p> <p id="asm_bestpractice_1009__p6297533195217"></p>

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

@ -8,7 +8,7 @@
</li> </li>
<li class="ulchildlink"><strong><a href="asm_bestpractice_3001.html">Service Governance for Dubbo-based Applications</a></strong><br> <li class="ulchildlink"><strong><a href="asm_bestpractice_3001.html">Service Governance for Dubbo-based Applications</a></strong><br>
</li> </li>
<li class="ulchildlink"><strong><a href="asm_bestpractice_1009.html">Creating a Service Mesh with IPv4/IPv6 Dual Stack Enabled</a></strong><br> <li class="ulchildlink"><strong><a href="asm_bestpractice_1009.html">How Do I Create a Service Mesh with IPv4/IPv6 Dual Stack Enabled</a></strong><br>
</li> </li>
</ul> </ul>
</div> </div>

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

@ -12,6 +12,8 @@
</li> </li>
<li class="ulchildlink"><strong><a href="asm_faq_0006.html">Performing Grayscale Release</a></strong><br> <li class="ulchildlink"><strong><a href="asm_faq_0006.html">Performing Grayscale Release</a></strong><br>
</li> </li>
<li class="ulchildlink"><strong><a href="asm_faq_0014.html">Monitoring Traffic</a></strong><br>
</li>
</ul> </ul>
</div> </div>

25
docs/asm/umn/asm_faq_0014.html Normal file
View File

@ -0,0 +1,25 @@
<a name="asm_faq_0014"></a><a name="asm_faq_0014"></a>
<h1 class="topictitle1">Monitoring Traffic</h1>
<div id="body1554353306515"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="asm_faq_0015.html">Why Cannot I View Traffic Monitoring Data Immediately After a Pod Is Started?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="asm_faq_0016.html">Why Are the Latency Statistics on the Dashboard Page Inaccurate?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="asm_faq_0017.html">Why Is the Traffic Ratio Inconsistent with That in the Traffic Monitoring Chart?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="asm_faq_0018.html">Why Can't I Find Certain Error Requests in Tracing?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="asm_faq_0023.html">Why Cannot I Find My Service in the Traffic Monitoring Topology?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="asm_faq_0049.html">How Do I Connect a Service Mesh to Jaeger or Zipkin for Viewing Traces?</a></strong><br>
</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_faq_0001_0.html">FAQs</a></div>
</div>
</div>

11
docs/asm/umn/asm_faq_0015.html Normal file
View File

@ -0,0 +1,11 @@
<a name="asm_faq_0015"></a><a name="asm_faq_0015"></a>
<h1 class="topictitle1">Why Cannot I View Traffic Monitoring Data Immediately After a Pod Is Started?</h1>
<div id="body1546055873319"><ol id="asm_faq_0015__ol13362106125720"><li id="asm_faq_0015__li1836219675710">Check whether APM has been enabled for the cluster.</li><li id="asm_faq_0015__li1346154185910">Traffic monitoring aggregates the collected data. Please wait for a minute for the data to be displayed on the <strong id="asm_faq_0015__b7388125231413">Traffic Monitoring</strong> page.</li></ol>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_faq_0014.html">Monitoring Traffic</a></div>
</div>
</div>

11
docs/asm/umn/asm_faq_0016.html Normal file
View File

@ -0,0 +1,11 @@
<a name="asm_faq_0016"></a><a name="asm_faq_0016"></a>
<h1 class="topictitle1">Why Are the Latency Statistics on the Dashboard Page Inaccurate?</h1>
<div id="body1546055873319"><p id="asm_faq_0016__p8060118">The latency statistics displayed on the <strong id="asm_faq_0016__b113175520353">Dashboard</strong> page are data of the services that have the highest latency among all the services in all the clusters of your account within the last one minute. Therefore, ensure that the service has been accessed within the last one minute.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_faq_0014.html">Monitoring Traffic</a></div>
</div>
</div>

11
docs/asm/umn/asm_faq_0017.html Normal file
View File

@ -0,0 +1,11 @@
<a name="asm_faq_0017"></a><a name="asm_faq_0017"></a>
<h1 class="topictitle1">Why Is the Traffic Ratio Inconsistent with That in the Traffic Monitoring Chart?</h1>
<div id="body1546055873319"><p id="asm_faq_0017__p8060118">The traffic ratio data is polled every 10 seconds, while the traffic monitoring data shows the traffic situation of the last 10 seconds.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_faq_0014.html">Monitoring Traffic</a></div>
</div>
</div>

11
docs/asm/umn/asm_faq_0018.html Normal file
View File

@ -0,0 +1,11 @@
<a name="asm_faq_0018"></a><a name="asm_faq_0018"></a>
<h1 class="topictitle1">Why Can't I Find Certain Error Requests in Tracing?</h1>
<div id="body1558593347201"><p id="asm_faq_0018__p113231023193718">For performance purposes, the sampling rate of tracing is 10%. That is, 10 of your 100 requests are recorded and displayed on the page.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_faq_0014.html">Monitoring Traffic</a></div>
</div>
</div>

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

@ -4,7 +4,7 @@
<div id="body1558420212482"></div> <div id="body1558420212482"></div>
<div> <div>
<ul class="ullinks"> <ul class="ullinks">
<li class="ulchildlink"><strong><a href="asm_faq_0020.html">Why Cannot I Create a Mesh for My Cluster?</a></strong><br> <li class="ulchildlink"><strong><a href="asm_faq_0020.html">Why Cannot I Create a Service Mesh for My Cluster?</a></strong><br>
</li> </li>
<li class="ulchildlink"><strong><a href="asm_faq_0022.html">Why Are Exclusive Nodes Still Exist After Istio Is Uninstalled?</a></strong><br> <li class="ulchildlink"><strong><a href="asm_faq_0022.html">Why Are Exclusive Nodes Still Exist After Istio Is Uninstalled?</a></strong><br>
</li> </li>

8
docs/asm/umn/asm_faq_0020.html
View File

@ -1,11 +1,11 @@
<a name="asm_faq_0020"></a><a name="asm_faq_0020"></a> <a name="asm_faq_0020"></a><a name="asm_faq_0020"></a>
<h1 class="topictitle1">Why Cannot I Create a Mesh for My Cluster?</h1> <h1 class="topictitle1">Why Cannot I Create a Service Mesh for My Cluster?</h1>
<div id="body1558420289267"><div class="section" id="asm_faq_0020__section9241144112532"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0020__p48901242185311">I cannot create a mesh for my cluster.</p> <div id="body1558420289267"><div class="section" id="asm_faq_0020__section9241144112532"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0020__p48901242185311">I cannot create a service mesh for my cluster.</p>
</div> </div>
<div class="section" id="asm_faq_0020__section12260657105316"><h4 class="sectiontitle">Analysis</h4><p id="asm_faq_0020__p1871911115414">Currently, clusters of versions earlier than 1.15 cannot be managed by meshes.</p> <div class="section" id="asm_faq_0020__section12260657105316"><h4 class="sectiontitle">Analysis</h4><p id="asm_faq_0020__p1871911115414">Currently, clusters earlier than v1.21 cannot be managed by service meshes.</p>
</div> </div>
<div class="section" id="asm_faq_0020__section957501035819"><h4 class="sectiontitle">Solution</h4><ol id="asm_faq_0020__ol1182114345818"><li id="asm_faq_0020__li148224317588"><span>Check the cluster version. Currently, only clusters of v1.15, v1.17, or v1.19 can be managed by meshes.</span></li><li id="asm_faq_0020__li478819209591"><span>Check your browser. Chrome is recommended. The button for mesh creation may be unavailable when you are using other browsers, such as Firefox, due to adaptation problems.</span></li></ol> <div class="section" id="asm_faq_0020__section957501035819"><h4 class="sectiontitle">Solution</h4><ol id="asm_faq_0020__ol1182114345818"><li id="asm_faq_0020__li131781824319"><span>Check the cluster version. Currently, only clusters v1.21 or later can be managed by service meshes.</span></li><li id="asm_faq_0020__li478819209591"><span>Check your browser. Chrome is recommended. The button for service mesh creation may be unavailable when you are using other browsers, such as Firefox, due to adaptation problems.</span></li></ol>
</div> </div>
</div> </div>
<div> <div>

11
docs/asm/umn/asm_faq_0023.html Normal file
View File

@ -0,0 +1,11 @@
<a name="asm_faq_0023"></a><a name="asm_faq_0023"></a>
<h1 class="topictitle1">Why Cannot I Find My Service in the Traffic Monitoring Topology?</h1>
<div id="body1561012208188"><ol id="asm_faq_0023__ol123210391503"><li id="asm_faq_0023__li6321139105017">Select a mesh, cluster, and namespace to monitor service traffic.</li><li id="asm_faq_0023__li732739145014">Check whether the ICAgent collector is correctly installed in the cluster.</li><li id="asm_faq_0023__li13273916505">Check whether the service has been added to the service mesh.</li></ol>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_faq_0014.html">Monitoring Traffic</a></div>
</div>
</div>

4
docs/asm/umn/asm_faq_0029.html
View File

@ -4,9 +4,9 @@
<div id="body1600074666720"></div> <div id="body1600074666720"></div>
<div> <div>
<ul class="ullinks"> <ul class="ullinks">
<li class="ulchildlink"><strong><a href="asm_faq_0030.html">Why Does a Service Mesh Remain in the Installing Status for a Long Time After I Enable It for a Cluster?</a></strong><br> <li class="ulchildlink"><strong><a href="asm_faq_0030.html">Why Does a Service Mesh Remain in the Installing State for a Long Time After I Enable It for a Cluster?</a></strong><br>
</li> </li>
<li class="ulchildlink"><strong><a href="asm_faq_0031.html">Why Does a Service Mesh Remain in the Unready Status for a Long Time After I Uninstall It?</a></strong><br> <li class="ulchildlink"><strong><a href="asm_faq_0031.html">Why Does a Service Mesh Remain in the Unready State for a Long Time After I Uninstall It?</a></strong><br>
</li> </li>
</ul> </ul>

6
docs/asm/umn/asm_faq_0030.html
View File

@ -1,13 +1,13 @@
<a name="asm_faq_0030"></a><a name="asm_faq_0030"></a> <a name="asm_faq_0030"></a><a name="asm_faq_0030"></a>
<h1 class="topictitle1">Why Does a Service Mesh Remain in the Installing Status for a Long Time After I Enable It for a Cluster?</h1> <h1 class="topictitle1">Why Does a Service Mesh Remain in the Installing State for a Long Time After I Enable It for a Cluster?</h1>
<div id="body1600074666721"><div class="section" id="asm_faq_0030__section1494171613215"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0030__p8837417429">After I create a service mesh (that is, create a Dedicated mesh) for a CCE cluster, the mesh remains in the installing status for a long time and a message is displayed, indicating that the user security group rules are successfully enabled.</p> <div id="body1600074666721"><div class="section" id="asm_faq_0030__section1494171613215"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0030__p8837417429">After I create a service mesh (that is, create a Dedicated service mesh) for a CCE cluster, it remains in the installing state for a long time and a message is displayed indicating that the user security group rules are successfully enabled.</p>
</div> </div>
<div class="section" id="asm_faq_0030__section19812813158"><h4 class="sectiontitle">Fault Diagnosis</h4><p id="asm_faq_0030__p29431791152">Log in to the CCE console and click the cluster name to go to the cluster console. In the navigation pane, choose <strong id="asm_faq_0030__b847051616431">Namespaces</strong>. Then, check whether the <strong id="asm_faq_0030__b718482082520">istio-system</strong> namespace exists.</p> <div class="section" id="asm_faq_0030__section19812813158"><h4 class="sectiontitle">Fault Diagnosis</h4><p id="asm_faq_0030__p29431791152">Log in to the CCE console and click the cluster name to go to the cluster console. In the navigation pane, choose <strong id="asm_faq_0030__b847051616431">Namespaces</strong>. Then, check whether the <strong id="asm_faq_0030__b718482082520">istio-system</strong> namespace exists.</p>
</div> </div>
<div class="section" id="asm_faq_0030__section16131017111611"><h4 class="sectiontitle">Analysis</h4><p id="asm_faq_0030__p4316152115164">Residual <strong id="asm_faq_0030__b1362012919168">istio-system</strong> namespaces exist.</p> <div class="section" id="asm_faq_0030__section16131017111611"><h4 class="sectiontitle">Analysis</h4><p id="asm_faq_0030__p4316152115164">Residual <strong id="asm_faq_0030__b1362012919168">istio-system</strong> namespaces exist.</p>
</div> </div>
<div class="section" id="asm_faq_0030__section540647131910"><h4 class="sectiontitle">Solution</h4><p id="asm_faq_0030__p49631218196">Delete the residual <strong id="asm_faq_0030__b2669123713166">istio-system</strong> namespaces and install the mesh again.</p> <div class="section" id="asm_faq_0030__section540647131910"><h4 class="sectiontitle">Solution</h4><p id="asm_faq_0030__p49631218196">Delete the residual <strong id="asm_faq_0030__b2669123713166">istio-system</strong> namespaces and install the service mesh again.</p>
</div> </div>
</div> </div>
<div> <div>

8
docs/asm/umn/asm_faq_0031.html
View File

@ -1,9 +1,9 @@
<a name="asm_faq_0031"></a><a name="asm_faq_0031"></a> <a name="asm_faq_0031"></a><a name="asm_faq_0031"></a>
<h1 class="topictitle1">Why Does a Service Mesh Remain in the Unready Status for a Long Time After I Uninstall It?</h1> <h1 class="topictitle1">Why Does a Service Mesh Remain in the Unready State for a Long Time After I Uninstall It?</h1>
<div id="body1600074666721"><div class="section" id="asm_faq_0031__section2060853210484"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0031__p797293315489">On the ASM console, after I uninstall a service mesh, the mesh remains in the unready status for a long time.</p> <div id="body1600074666721"><div class="section" id="asm_faq_0031__section2060853210484"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0031__p797293315489">On the ASM console, after I uninstall a service mesh, it remains in the unready state for a long time.</p>
</div> </div>
<div class="section" id="asm_faq_0031__section62421653135217"><h4 class="sectiontitle">Fault Diagnosis</h4><ol id="asm_faq_0031__ol114041584333"><li id="asm_faq_0031__li15404165815336"><span>Log in to the CCE console. Click the cluster name to go to the cluster console. In the navigation pane on the left, choose <strong id="asm_faq_0031__b1819515325711">App Templates</strong>.</span></li><li id="asm_faq_0031__li16806182703412"><span>Click <strong id="asm_faq_0031__b591845810489">Releases</strong> and select the target cluster from the drop-down list. Check the releases and the latest events about uninstallation failure.</span><p><p id="asm_faq_0031__p12911043121320">The <strong id="asm_faq_0031__b1343111283520">Status</strong> of <strong id="asm_faq_0031__b9432182819526">istio-master</strong> is <strong id="asm_faq_0031__b114331328145216">Uninstallation Failed</strong>, and the following message is displayed.</p> <div class="section" id="asm_faq_0031__section62421653135217"><h4 class="sectiontitle">Fault Diagnosis</h4><ol id="asm_faq_0031__ol114041584333"><li id="asm_faq_0031__li15404165815336"><span>Log in to the CCE console. Click the cluster name to go to the cluster console. In the navigation pane, choose <strong id="asm_faq_0031__b1819515325711">App Templates</strong>.</span></li><li id="asm_faq_0031__li16806182703412"><span>Click <strong id="asm_faq_0031__b591845810489">Releases</strong> and select the target cluster from the drop-down list. Check the releases and the latest events about uninstallation failure.</span><p><p id="asm_faq_0031__p12911043121320">The <strong id="asm_faq_0031__b1343111283520">Status</strong> of <strong id="asm_faq_0031__b9432182819526">istio-master</strong> is <strong id="asm_faq_0031__b114331328145216">Uninstallation Failed</strong>, and the following message is displayed.</p>
<pre class="screen" id="asm_faq_0031__screen252345201312">deletion failed with 1 error(s): clusterroles:rbac.authorization.k8s.io "istio-cleanup-secrets-istio-system" already exists</pre> <pre class="screen" id="asm_faq_0031__screen252345201312">deletion failed with 1 error(s): clusterroles:rbac.authorization.k8s.io "istio-cleanup-secrets-istio-system" already exists</pre>
</p></li></ol> </p></li></ol>
</div> </div>
@ -15,7 +15,7 @@ kubectl delete ClusterRoleBinding -n istio-system `kubectl get ClusterRoleBindin
kubectl delete job -n istio-system `kubectl get job -n istio-system | grep istio | awk '{print $1}'` kubectl delete job -n istio-system `kubectl get job -n istio-system | grep istio | awk '{print $1}'`
kubectl delete crd -n istio-system `kubectl get crd -n istio-system | grep istio | awk '{print $1}'` kubectl delete crd -n istio-system `kubectl get crd -n istio-system | grep istio | awk '{print $1}'`
kubectl delete mutatingwebhookconfigurations -n istio-system `kubectl get mutatingwebhookconfigurations -n istio-system | grep istio | awk '{print $1}'`</pre> kubectl delete mutatingwebhookconfigurations -n istio-system `kubectl get mutatingwebhookconfigurations -n istio-system | grep istio | awk '{print $1}'`</pre>
</p></li><li id="asm_faq_0031__li102148053612"><span>Log in to the ASM console and uninstall the mesh again.</span></li></ol> </p></li><li id="asm_faq_0031__li102148053612"><span>Log in to the ASM console and uninstall the service mesh again.</span></li></ol>
</div> </div>
</div> </div>
<div> <div>

13
docs/asm/umn/asm_faq_0037.html
View File

@ -1,11 +1,18 @@
<a name="asm_faq_0037"></a><a name="asm_faq_0037"></a> <a name="asm_faq_0037"></a><a name="asm_faq_0037"></a>
<h1 class="topictitle1">How Do I Disable Sidecar Injection for Workloads?</h1> <h1 class="topictitle1">How Do I Disable Sidecar Injection for Workloads?</h1>
<div id="body0000001268293001"><p id="asm_faq_0037__p8060118">After sidecar injection is enabled for a namespace of a cluster, sidecars are automatically injected for pods of all workloads in the namespace. You can configure sidecars not to be injected into some workloads:</p> <div id="body0000001268293001"><p id="asm_faq_0037__p8060118">If sidecar injection is enabled for a namespace of a cluster, sidecars are automatically injected for the pods of all workloads in the namespace. To prevent sidecars from being injected for some workloads, perform the following operations:</p>
<ol id="asm_faq_0037__ol425845114363"><li id="asm_faq_0037__li946861618501"><span>Log in to the CCE console and click the cluster name to go to the cluster console. Then, choose <strong id="asm_faq_0037__b1997919161">Workloads</strong> &gt; <strong id="asm_faq_0037__b5910915165">Deployments</strong>.</span></li><li id="asm_faq_0037__li411192010539"><span>Locate the workload and click <strong id="asm_faq_0037__b16189122217175">Edit YAML</strong> in the <strong id="asm_faq_0037__b1262015291810">Operation</strong> column.</span></li><li id="asm_faq_0037__li653954054313"><span>Find the <strong id="asm_faq_0037__b8861120161116">spec.template.metadata.annotations</strong> field and add <strong id="asm_faq_0037__b19358193316117">sidecar.istio.io/inject: 'false'</strong>.</span><p><pre class="screen" id="asm_faq_0037__screen575018269110"> annotations: <ol id="asm_faq_0037__ol425845114363"><li id="asm_faq_0037__li946861618501"><span>Log in to the CCE console and click the cluster name to go to the cluster console. In the navigation pane, choose <strong id="asm_faq_0037__b1997919161">Workloads</strong>. Then, click the <strong id="asm_faq_0037__b5910915165">Deployments</strong> tab.</span></li><li id="asm_faq_0037__li411192010539"><span>Locate the workload and click <strong id="asm_faq_0037__b16189122217175">Edit YAML</strong> in the <strong id="asm_faq_0037__b1262015291810">Operation</strong> column.</span></li><li id="asm_faq_0037__li15358210441"><span>Locate the target field based on the service mesh version and add <strong id="asm_faq_0037__b11704672243">sidecar.istio.io/inject: 'false'</strong>.</span><p><ul id="asm_faq_0037__ul18942053104418"><li id="asm_faq_0037__li22712717457">For service meshes earlier than 1.13<div class="p" id="asm_faq_0037__p748709104516"><a name="asm_faq_0037__li22712717457"></a><a name="li22712717457"></a>Locate the <strong id="asm_faq_0037__b485819326134">spec.template.metadata.annotations</strong> field and add <strong id="asm_faq_0037__b8858183217139">sidecar.istio.io/inject: 'false'</strong>.<pre class="screen" id="asm_faq_0037__screen575018269110"> annotations:
sidecar.istio.io/inject: 'false'</pre> sidecar.istio.io/inject: 'false'</pre>
</div>
<p id="asm_faq_0037__p17606194116195"><span><img id="asm_faq_0037__image166053415196" src="en-us_image_0000001223579300.png"></span></p> <p id="asm_faq_0037__p17606194116195"><span><img id="asm_faq_0037__image166053415196" src="en-us_image_0000001223579300.png"></span></p>
<p id="asm_faq_0037__p182961254182110">For more details about sidecar injection, see <a href="https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/#controlling-the-injection-policy" target="_blank" rel="noopener noreferrer">Automatic Sidecar Injection</a>.</p> </li></ul>
<ul id="asm_faq_0037__ul131144284459"><li id="asm_faq_0037__li161141928154518">For service meshes 1.13 or later:<p id="asm_faq_0037__p165276064812"><a name="asm_faq_0037__li161141928154518"></a><a name="li161141928154518"></a>Locate the <strong id="asm_faq_0037__b542419398134">spec.template.metadata.label</strong> field and add <strong id="asm_faq_0037__b942443915138">sidecar.istio.io/inject: 'false'</strong>.</p>
<pre class="screen" id="asm_faq_0037__screen1852740154813"> label:
sidecar.istio.io/inject: 'false'</pre>
<p id="asm_faq_0037__p194274115277"><span><img id="asm_faq_0037__image13417142112712" src="en-us_image_0000001997321585.png"></span></p>
</li></ul>
<p id="asm_faq_0037__p1535858144817">For more details about sidecar injection, see <a href="https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/#controlling-the-injection-policy" target="_blank" rel="noopener noreferrer">Automatic Sidecar Injection</a>.</p>
</p></li></ol> </p></li></ol>
</div> </div>
<div> <div>

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

@ -2,32 +2,32 @@
<h1 class="topictitle1">How Do I Handle a Canary Upgrade Failure?</h1> <h1 class="topictitle1">How Do I Handle a Canary Upgrade Failure?</h1>
<div id="body0000001566345722"><p id="asm_faq_0044__p15844739104812">There are many reasons for a canary upgrade failure. In case of a canary upgrade failure, you can use the following solutions to handle it.</p> <div id="body0000001566345722"><p id="asm_faq_0044__p15844739104812">There are many reasons for a canary upgrade failure. In case of a canary upgrade failure, you can use the following solutions to handle it.</p>
<ol id="asm_faq_0044__ol7822958185419"><li id="asm_faq_0044__li188346725614">Failed to check custom resource definitions (CRDs) before the upgrade.<p id="asm_faq_0044__p116531953105718"><a name="asm_faq_0044__li188346725614"></a><a name="li188346725614"></a><strong id="asm_faq_0044__b257713234302">Solution</strong>: New Istio version does not support some CRDs, including clusterrbacconfigs, serviceroles, servicerolebindings, and policies. If there are resources to be discarded in the current version, delete them before the upgrade.</p> <ol id="asm_faq_0044__ol7822958185419"><li id="asm_faq_0044__li188346725614">Failed to check custom resource definitions (CRDs) before the upgrade.<p id="asm_faq_0044__p116531953105718"><a name="asm_faq_0044__li188346725614"></a><a name="li188346725614"></a><strong id="asm_faq_0044__b257713234302">Solution</strong>: New Istio version does not support some CRDs, including ClusterRbacConfigs, ServiceRoles, ServiceRoleBindings, and Policies. If there are resources to be discarded in the current version, delete them before the upgrade.</p>
</li><li id="asm_faq_0044__li1350163725711">Failed to check Istio gateway labels before the upgrade.<p id="asm_faq_0044__p899201514013"><a name="asm_faq_0044__li1350163725711"></a><a name="li1350163725711"></a><strong id="asm_faq_0044__b1778184795016">Solution:</strong> Configure Istio gateway labels (specified by <strong id="asm_faq_0044__b177789476508">matchLabels</strong>) in <em id="asm_faq_0044__i477824755012">{app: istio-ingressgateway, istio: ingressgateway}</em> format.</p> </li><li id="asm_faq_0044__li1350163725711">Failed to check Istio gateway labels before the upgrade.<p id="asm_faq_0044__p899201514013"><a name="asm_faq_0044__li1350163725711"></a><a name="li1350163725711"></a><strong id="asm_faq_0044__b1778184795016">Solution:</strong> Configure Istio gateway labels (specified by <strong id="asm_faq_0044__b177789476508">matchLabels</strong>) in <em id="asm_faq_0044__i477824755012">{app: istio-ingressgateway, istio: ingressgateway}</em> format.</p>
</li><li id="asm_faq_0044__li6914111195817">Failed to check add-ons before the upgrade.<p id="asm_faq_0044__p108601011633"><a name="asm_faq_0044__li6914111195817"></a><a name="li6914111195817"></a><strong id="asm_faq_0044__b1824118892916">Solution:</strong> ASM 1.8 and later versions do not support the tracing, kiali, grafana, and prometheus add-ons. Uninstall the add-ons before the upgrade. You can install open-source add-ons or use APM.</p> </li><li id="asm_faq_0044__li6914111195817">Failed to check add-ons before the upgrade.<p id="asm_faq_0044__p108601011633"><a name="asm_faq_0044__li6914111195817"></a><a name="li6914111195817"></a><strong id="asm_faq_0044__b1824118892916">Solution:</strong> ASM 1.8 and later versions do not support the tracing, kiali, grafana, and prometheus add-ons. Uninstall the add-ons before the upgrade. You can install open-source add-ons or use APM.</p>
</li><li id="asm_faq_0044__li148631614165815">Failed to check the cluster status before the upgrade.<p id="asm_faq_0044__p137912141946"><a name="asm_faq_0044__li148631614165815"></a><a name="li148631614165815"></a><strong id="asm_faq_0044__b438672510125">Solution:</strong> If the cluster is unavailable before the upgrade, do not perform the upgrade.</p> </li><li id="asm_faq_0044__li148631614165815">Failed to check the cluster status before the upgrade.<p id="asm_faq_0044__p137912141946"><a name="asm_faq_0044__li148631614165815"></a><a name="li148631614165815"></a><strong id="asm_faq_0044__b438672510125">Solution:</strong> If the cluster is unavailable before the upgrade, do not perform the upgrade.</p>
</li><li id="asm_faq_0044__li12441191612583">Failed to query resources before the upgrade.<p id="asm_faq_0044__p7802191656"><a name="asm_faq_0044__li12441191612583"></a><a name="li12441191612583"></a><strong id="asm_faq_0044__b128111365512">Solution:</strong> Prepare the required resources for the canary upgrade.</p> </li><li id="asm_faq_0044__li12441191612583">Failed to query resources before the upgrade.<p id="asm_faq_0044__p7802191656"><a name="asm_faq_0044__li12441191612583"></a><a name="li12441191612583"></a><strong id="asm_faq_0044__b128111365512">Solution:</strong> Prepare the required resources for the canary upgrade.</p>
</li><li id="asm_faq_0044__li1581414179585">Failed to check the cluster version before the upgrade.<p id="asm_faq_0044__p89909508511"><a name="asm_faq_0044__li1581414179585"></a><a name="li1581414179585"></a><strong id="asm_faq_0044__b298104685118">Solution</strong>: Use the cluster version listed in the following table.</p> </li><li id="asm_faq_0044__li1581414179585">Failed to check the cluster version before the upgrade.<p id="asm_faq_0044__p89909508511"><a name="asm_faq_0044__li1581414179585"></a><a name="li1581414179585"></a><strong id="asm_faq_0044__b298104685118">Solution</strong>: Use the cluster version listed in the following table.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="asm_faq_0044__table1655872545813" frame="border" border="1" rules="all"><tbody><tr id="asm_faq_0044__row186381025105817"><td class="cellrowborder" valign="top" width="49.919999999999995%"><p id="asm_faq_0044__p263812555815">Mesh Version</p> <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="asm_faq_0044__table1655872545813" frame="border" border="1" rules="all"><tbody><tr id="asm_faq_0044__row186381025105817"><td class="cellrowborder" valign="top" width="49.919999999999995%"><p id="asm_faq_0044__p263812555815">Service Mesh Version</p>
</td> </td>
<td class="cellrowborder" valign="top" width="50.080000000000005%"><p id="asm_faq_0044__p863842516587">Supported Cluster Version</p> <td class="cellrowborder" valign="top" width="50.080000000000005%"><p id="asm_faq_0044__p863842516587">Supported Cluster Version</p>
</td> </td>
</tr> </tr>
<tr id="asm_faq_0044__row136381425135812"><td class="cellrowborder" valign="top" width="49.919999999999995%"><p id="asm_faq_0044__p1963882595815">1.15</p> <tr id="asm_faq_0044__row136381425135812"><td class="cellrowborder" valign="top" width="49.919999999999995%"><p id="asm_faq_0044__p1963882595815">1.15</p>
</td> </td>
<td class="cellrowborder" valign="top" width="50.080000000000005%"><p id="asm_faq_0044__p11638192517583">1.21,1.23,1.25,1.27</p> <td class="cellrowborder" valign="top" width="50.080000000000005%"><p id="asm_faq_0044__p11638192517583">1.21, 1.23, 1.25, and 1.27</p>
</td> </td>
</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,1.28,1.29</p> <td class="cellrowborder" valign="top" width="50.080000000000005%"><p id="asm_faq_0044__p195271851173113">1.25,1.27, and 1.28</p>
</td> </td>
</tr> </tr>
</tbody> </tbody>
</table> </table>
</div> </div>
</li><li id="asm_faq_0044__li17960131875820">Failed to check the component affinity before the upgrade.<p id="asm_faq_0044__p669312468613"><a name="asm_faq_0044__li17960131875820"></a><a name="li17960131875820"></a><strong id="asm_faq_0044__b46254195210">Solutions</strong>: If you upgrade Istio from a non-canary version to a canary version, ensure that there are at least twice as many nodes labeled with <strong id="asm_faq_0044__b166264135217">istio:master</strong> as there are istiod instances, and at least twice as many schedulable nodes as there are istio-ingressgateway or istio-egressgateway instances (depending on which one is larger). If such conditions are not met, add nodes to meet the scheduling requirements or set the anti-affinity of istiod, istio-ingressgateway, and istio-egressgateway to <strong id="asm_faq_0044__b162184114522">Preferred</strong>.</p> </li><li id="asm_faq_0044__li17960131875820">Failed to check the component affinity before the upgrade.<p id="asm_faq_0044__p669312468613"><a name="asm_faq_0044__li17960131875820"></a><a name="li17960131875820"></a><strong id="asm_faq_0044__b1568325792715">Solutions</strong>: If you upgrade Istio from a non-canary version to a canary version, ensure that there are at least twice as many nodes labeled with <strong id="asm_faq_0044__b7683957102712">istio:master</strong> as there are istiod instances, and at least twice as many schedulable nodes as there are istio-ingressgateway or istio-egressgateway instances (depending on which one is larger). If such conditions are not met, add nodes to meet the scheduling requirements or set the anti-affinity of istiod, istio-ingressgateway, and istio-egressgateway to <strong id="asm_faq_0044__b15683165711272">Preferred</strong>.</p>
<ul id="asm_faq_0044__ul20572165411417"><li id="asm_faq_0044__li6572155414140">Method 1: Add nodes labeled with <strong id="asm_faq_0044__b12596411145311">istio:master</strong> on the CCE console.</li></ul> <ul id="asm_faq_0044__ul20572165411417"><li id="asm_faq_0044__li6572155414140">Method 1: Add nodes labeled with <strong id="asm_faq_0044__b12596411145311">istio:master</strong> on the CCE console.</li></ul>
<p id="asm_faq_0044__p8632111679"></p> <p id="asm_faq_0044__p8632111679"></p>
<ul id="asm_faq_0044__ul0794122213159"><li id="asm_faq_0044__li979416226154"><strong id="asm_faq_0044__b11987104419536">Solution 2</strong>: Edit the YAML file to modify the anti-affinity policy on the CCE console.</li></ul> <ul id="asm_faq_0044__ul0794122213159"><li id="asm_faq_0044__li979416226154"><strong id="asm_faq_0044__b11987104419536">Solution 2</strong>: Edit the YAML file to modify the anti-affinity policy on the CCE console.</li></ul>
@ -46,7 +46,7 @@
topologyKey: kubernetes.io/hostname</pre> topologyKey: kubernetes.io/hostname</pre>
<p id="asm_faq_0044__p11633141777">Alternatively, change the anti-affinity from <strong id="asm_faq_0044__b1742791355512">Required</strong> to <strong id="asm_faq_0044__b94271813195510">Preferred</strong> on the CCE console.</p> <p id="asm_faq_0044__p11633141777">Alternatively, change the anti-affinity from <strong id="asm_faq_0044__b1742791355512">Required</strong> to <strong id="asm_faq_0044__b94271813195510">Preferred</strong> on the CCE console.</p>
<p id="asm_faq_0044__p2633011178"></p> <p id="asm_faq_0044__p2633011178"></p>
</li><li id="asm_faq_0044__li485331955816">Failed to check the automatic namespace injection before the upgrade.<p id="asm_faq_0044__p49178221785"><a name="asm_faq_0044__li485331955816"></a><a name="li485331955816"></a><strong id="asm_faq_0044__b4661328105520">Solution:</strong> If there are pods in the namespace when you migrate mesh data from the Dedicated edition to the Basic edition, enable automatic injection for the namespace.</p> </li><li id="asm_faq_0044__li485331955816">Failed to check the automatic namespace injection before the upgrade.<p id="asm_faq_0044__p49178221785"><a name="asm_faq_0044__li485331955816"></a><a name="li485331955816"></a><strong id="asm_faq_0044__b4661328105520">Solution:</strong> If there are pods in the namespace when you migrate service mesh data from the Dedicated edition to the Basic edition, enable automatic injection for the namespace.</p>
</li></ol> </li></ol>
</div> </div>
<div> <div>

95
docs/asm/umn/asm_faq_0049.html Normal file
View File

@ -0,0 +1,95 @@
<a name="asm_faq_0049"></a><a name="asm_faq_0049"></a>
<h1 class="topictitle1">How Do I Connect a Service Mesh to Jaeger or Zipkin for Viewing Traces?</h1>
<div id="body0000001953665368"><p id="asm_faq_0049__p1255084518506">ASM can export traces to Jaeger or Zipkin. You can view them on the Jaeger or Zipkin UI. The following uses Zipkin as an example.</p>
<div class="section" id="asm_faq_0049__section36511139314"><h4 class="sectiontitle">Prerequisites</h4><p id="asm_faq_0049__p4558172118611">The cluster and namespace where Zipkin is to be installed have been specified.</p>
</div>
<div class="section" id="asm_faq_0049__section5871427115120"><h4 class="sectiontitle">Procedure</h4><ol id="asm_faq_0049__ol19812285213"><li id="asm_faq_0049__li098232175213"><a name="asm_faq_0049__li098232175213"></a><a name="li098232175213"></a><span>Create a Deployment named <strong id="asm_faq_0049__b1720043173914">zipkin</strong>.</span><p><p id="asm_faq_0049__p24511053145119">Log in to the CCE console and click the cluster name to go to the cluster console. In the navigation pane, choose <strong id="asm_faq_0049__b299024534215">Workloads</strong>. On the <strong id="asm_faq_0049__b20551165010425">Deployments</strong> tab, click <strong id="asm_faq_0049__b84442405423">Create from YAML</strong>, and copy the following content to the YAML file:</p>
<pre class="screen" id="asm_faq_0049__screen876244915616">apiVersion: apps/v1
kind: Deployment
metadata:
name: zipkin
namespace: monitoring
spec:
progressDeadlineSeconds: 600
replicas: 1
revisionHistoryLimit: 10
selector:
matchLabels:
app.kubernetes.io/instance: zipkin
app.kubernetes.io/name: zipkin
strategy:
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
type: RollingUpdate
template:
metadata:
labels:
app.kubernetes.io/instance: zipkin
app.kubernetes.io/name: zipkin
spec:
automountServiceAccountToken: false
containers:
- env:
- name: STORAGE_TYPE
value: mem
image: openzipkin/zipkin-slim:latest # Community Zipkin image path. Ensure that you can access this path.
imagePullPolicy: IfNotPresent
name: zipkin
readinessProbe:
failureThreshold: 3
httpGet:
path: /health
port: 9411
scheme: HTTP
initialDelaySeconds: 5
periodSeconds: 5
successThreshold: 1
timeoutSeconds: 1
resources:
limits:
cpu: 500m
memory: 4Gi
requests:
cpu: 100m
memory: 128Mi
securityContext:
readOnlyRootFilesystem: true
runAsNonRoot: true
runAsUser: 1000
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
terminationGracePeriodSeconds: 30</pre>
<p id="asm_faq_0049__p64533535513">The Deployment named <strong id="asm_faq_0049__b1542917044816">zipkin</strong> is displayed on the <strong id="asm_faq_0049__b122941179482">Deployments</strong> tab. If the status of <strong id="asm_faq_0049__b1792103255418">zipkin</strong> changes to <strong id="asm_faq_0049__b2142194785419">Running</strong>, Zipkin has been installed in the <strong id="asm_faq_0049__b149877125519">monitoring</strong> namespace of the target cluster.</p>
<p id="asm_faq_0049__p12915155520167"></p>
<div class="note" id="asm_faq_0049__note1614844414238"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_faq_0049__p91481244152319">You can also refer to <a href="https://zipkin.io/pages/quickstart.html" target="_blank" rel="noopener noreferrer">Zipkin official website documentation</a> to complete the installation.</p>
</div></div>
</p></li><li id="asm_faq_0049__li139077291524"><a name="asm_faq_0049__li139077291524"></a><a name="li139077291524"></a><span>Create a Service of the LoadBalancer type.</span><p><p id="asm_faq_0049__p82931961535">On the cluster console, choose <strong id="asm_faq_0049__b181255321717">Services &amp; Ingresses</strong> in the navigation pane. On the <strong id="asm_faq_0049__b165383711120">Services</strong> tab, click <strong id="asm_faq_0049__b2096712551818">Create Service</strong>. Then, configure the parameters as follows:</p>
<ul id="asm_faq_0049__ul457511661315"><li id="asm_faq_0049__li1957511651311"><strong id="asm_faq_0049__b183851619826">Service Name</strong>: Enter a name. <strong id="asm_faq_0049__b724132610215">zipkin</strong> is used as an example here.</li><li id="asm_faq_0049__li168222810133"><strong id="asm_faq_0049__b45682105314">Service Type</strong>: Select <strong id="asm_faq_0049__b8568151016317">LoadBalancer</strong>.</li><li id="asm_faq_0049__li2225151117137"><strong id="asm_faq_0049__b116548271312">Selector</strong>: Click <strong id="asm_faq_0049__b477114461447">Reference Workload Label</strong>. The label is automatically added.</li><li id="asm_faq_0049__li1249291391315"><strong id="asm_faq_0049__b1143412131882">Ports</strong>: Configure the container port and Service port. <strong id="asm_faq_0049__b1145913281881">9411</strong> is used as an example here.</li></ul>
<p id="asm_faq_0049__p1054024811212">Retain the default values for other parameters.</p>
<p id="asm_faq_0049__p1813462713182"></p>
<p id="asm_faq_0049__p1228116117231">The Service named <strong id="asm_faq_0049__b01191472313">zipkin</strong> is displayed on the <strong id="asm_faq_0049__b71191676312">Services</strong> tab.</p>
<p id="asm_faq_0049__p1829426115320"></p>
<div class="caution" id="asm_faq_0049__note531232182212"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="asm_faq_0049__p13363282212">If you do not need to access the Zipkin UI, set <strong id="asm_faq_0049__b169334233214">Access Type</strong> to <strong id="asm_faq_0049__b4971887338">ClusterIP</strong>.</p>
</div></div>
</p></li><li id="asm_faq_0049__li13729338114412"><span>Buy a service mesh and interconnect it with Zipkin.</span><p><p id="asm_faq_0049__p178544214419">Log in to the ASM console and click . In <strong id="asm_faq_0049__b25262914373">Cluster Configuration</strong>, select the cluster in <a href="#asm_faq_0049__li098232175213">1</a>. In <strong id="asm_faq_0049__b119744819378">Observability Configuration</strong>, enable tracing. Then, select <strong id="asm_faq_0049__b3741155114113">Third-party Jaeger/Zipkin service</strong> for <strong id="asm_faq_0049__b129028384435">Version</strong>, set <strong id="asm_faq_0049__b6563615174517">Service Address</strong> and <strong id="asm_faq_0049__b15594118184511">Access Port</strong>, and configure other parameters as required.</p>
<p id="asm_faq_0049__p138755284596"></p>
<div class="caution" id="asm_faq_0049__note1954184272911"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="asm_faq_0049__p5541194213296">The value of <strong id="asm_faq_0049__b328316538457">Service Address</strong> is <em id="asm_faq_0049__i145201645134915">{Service name}</em><strong id="asm_faq_0049__b14606164913498">.</strong><em id="asm_faq_0049__i18501105534915">{Namespace}</em><strong id="asm_faq_0049__b1735704504">.svc.cluster.local</strong>. Replace <em id="asm_faq_0049__i1140244855114">{Service name}</em> and <em id="asm_faq_0049__i566095955112">{Namespace}</em> with those specified in <a href="#asm_faq_0049__li139077291524">2</a>.</p>
<p id="asm_faq_0049__p9502451103216">The value of <strong id="asm_faq_0049__b866100145419">Access Port</strong> is that specified in <a href="#asm_faq_0049__li139077291524">2</a>.</p>
</div></div>
</p></li><li id="asm_faq_0049__li359554412532"><span>. After the deployment is complete, the services shown in the following figure are displayed on the <strong id="asm_faq_0049__b12741242574">Service Management</strong> page.</span><p><p id="asm_faq_0049__p1912126104113"></p>
</p></li><li id="asm_faq_0049__li11168185540"><span>Access the productpage details page to trigger tracing.</span><p><p id="asm_faq_0049__p994155384316">Go to the service mesh details page. In the navigation pane, choose <strong id="asm_faq_0049__b1794819291214">Service Management</strong>. On the displayed page, click the external address <strong id="asm_faq_0049__b8391193317134">http://</strong><em id="asm_faq_0049__i19361530171312">{IP address}</em><strong id="asm_faq_0049__b3838132317585">:</strong><em id="asm_faq_0049__i1939011246589">{Port number}</em><strong id="asm_faq_0049__b1083813236584">/productpage</strong> of the <strong id="asm_faq_0049__b7804940162011">productpage</strong> service.</p>
</p></li><li id="asm_faq_0049__li97966665113"><span>View the traces on the Zipkin UI at <strong id="asm_faq_0049__b1818212220317">http://</strong><em id="asm_faq_0049__i744022917316">{Public IP address of the load balancer configured for <strong id="asm_faq_0049__b5406145520">zipkin</strong>}</em><strong id="asm_faq_0049__b123921011345">:</strong><em id="asm_faq_0049__i36251828659">{Access port of <strong id="asm_faq_0049__b178134321512">zipkin</strong>}</em><strong id="asm_faq_0049__b156189392519">/zipkin/</strong>.</span><p><p id="asm_faq_0049__p17254111175110"></p>
<div class="note" id="asm_faq_0049__note18532611511"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_faq_0049__p1637017116550">You can obtain the IP address and port for logging in to the Zipkin client as follows:</p>
<ul id="asm_faq_0049__ul186718332111"><li id="asm_faq_0049__li6671193318118">IP address: Go to the console of the cluster where Zipkin is installed. In the navigation pane, choose <strong id="asm_faq_0049__b57154251975">Services &amp; Ingresses</strong>. On the <strong id="asm_faq_0049__b37151251570">Services</strong> tab, view the public IP address of the load balancer configured for <strong id="asm_faq_0049__b1120711352073">zipkin</strong>.</li><li id="asm_faq_0049__li185710361012">Port: On the <strong id="asm_faq_0049__b1941114328325">Services</strong> tab, view the access port of <strong id="asm_faq_0049__b6548111412612">zipkin</strong>.</li></ul>
</div></div>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_faq_0014.html">Monitoring Traffic</a></div>
</div>
</div>

29
docs/asm/umn/asm_his_0001.html Normal file
View File

@ -0,0 +1,29 @@
<a name="asm_his_0001"></a><a name="asm_his_0001"></a>
<h1 class="topictitle1">Change History</h1>
<div id="body0000001944672370">
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="asm_his_0001__table15181158326" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Change history</caption><thead align="left"><tr id="asm_his_0001__row1918181514323"><th align="left" class="cellrowborder" valign="top" width="20.5%" id="mcps1.3.1.2.3.1.1"><p id="asm_his_0001__p1018181513321">Released On</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="79.5%" id="mcps1.3.1.2.3.1.2"><p id="asm_his_0001__p5181215183219">Description</p>
</th>
</tr>
</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>
</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>
<p id="asm_his_0001__p13718237816">- Updated the infographic of ASM.</p>
<p id="asm_his_0001__p1411131911920">- Optimized other problems.</p>
<p id="asm_his_0001__p153701734080">- Added the change history.</p>
</li></ul>
</td>
</tr>
<tr id="asm_his_0001__row5576183415170"><td class="cellrowborder" valign="top" width="20.5%" headers="mcps1.3.1.2.3.1.1 "><p id="asm_his_0001__p9572134181710">2024-04-25</p>
</td>
<td class="cellrowborder" valign="top" width="79.5%" headers="mcps1.3.1.2.3.1.2 "><ul id="asm_his_0001__ul75721434141716"><li id="asm_his_0001__li8572123411716">First release.</li></ul>
</td>
</tr>
</tbody>
</table>
</div>
</div>

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

@ -2,7 +2,7 @@
<h1 class="topictitle1">Infographic for ASM</h1> <h1 class="topictitle1">Infographic for ASM</h1>
<div id="body0000001209484931"><p id="asm_productdesc_0017__p1289416386116"></p> <div id="body0000001209484931"><p id="asm_productdesc_0017__p1289416386116"></p>
<p id="asm_productdesc_0017__p55821111274"><span><img id="asm_productdesc_0017__image73201388158" src="en-us_image_0000001918938240.png"></span></p> <p id="asm_productdesc_0017__p837613199456"><span><img id="asm_productdesc_0017__image73201388158" src="en-us_image_0000002043652974.png"></span></p>
</div> </div>
<div> <div>
<div class="familylinks"> <div class="familylinks">

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

File diff suppressed because it is too large Load Diff

BIN
docs/asm/umn/en-us_image_0000001280416429.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 10 KiB

BIN
docs/asm/umn/en-us_image_0000001918938240.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 2.3 MiB

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

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 14 KiB

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

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 618 KiB