oeotvos/application-service-mesh
1
0
Fork 0
forked from docs/application-service-mesh
Code Pull Requests Activity

Changes to asm_umn from docs/doc-exports#1415 (ASM UMN update 20241203 version

Browse Source 
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com>
Co-authored-by: OpenTelekomCloud Proposal Bot <proposalbot@otc-service.com>
Co-committed-by: OpenTelekomCloud Proposal Bot <proposalbot@otc-service.com>
This commit is contained in:
OpenTelekomCloud Proposal Bot 2024-12-05 07:22:42 +00:00 committed by zuul
parent 30148efa0a
commit 4b0546ef7d
9 changed files with 79 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
umn/source/_static/images/en-us_image_0000002086005592.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 6.9 KiB

2
umn/source/change_history.rst
View File

@ -10,6 +10,8 @@ Change History
+-----------------------------------+--------------------------------------------------------------+
| Released On | Description |
+===================================+==============================================================+
| 2024-12-02 | Added clusters v1.29 and v1.30. |
+-----------------------------------+--------------------------------------------------------------+
| 2024-10-12 | - The following are modifications based on review comments: |
| | |
| | - Added the "Upgrades" chapter. |

6
umn/source/faqs/mesh_management/how_do_i_handle_a_canary_upgrade_failure.rst
View File

@ -31,11 +31,11 @@ There are many reasons for a canary upgrade failure. In case of a canary upgrade
**Solution**: Use the cluster version listed in the following table.
==================== ==========================
==================== ================================
Service Mesh Version Supported Cluster Version
1.15 1.21, 1.23, 1.25, and 1.27
1.18 1.25,1.27, and 1.28
==================== ==========================
1.18 1.25, 1.27, 1.28, 1.29, and 1.30
==================== ================================
#. Failed to check the component affinity before the upgrade.

10
umn/source/service_overview/constraints.rst
View File

@ -14,17 +14,15 @@ Before creating a service mesh, ensure that you have an available cluster. Clust
.. table:: **Table 1** Adaptation rules between ASM and cluster versions
=========== =============================
=========== ====================================
ASM Version Cluster Version
=========== =============================
=========== ====================================
1.15 v1.21, v1.23, v1.25, or v1.27
1.18 v1.25, v1.27, or v1.28
=========== =============================
1.18 v1.25, v1.27, v1.28, v1.29, or v1.30
=========== ====================================
Containers on the node running Ubuntu 22.04 in a CCE Turbo cluster cannot be added to a service mesh earlier than v1.18.
- Ubuntu 22.04
Constraints on Service Meshes
-----------------------------

6
umn/source/user_guide/creating_a_service_mesh/creating_a_service_mesh.rst
View File

@ -1,6 +1,6 @@
:original_name: asm_01_0084.html
:original_name: asm_01_0020.html
.. _asm_01_0084:
.. _asm_01_0020:
Creating a Service Mesh
=======================
@ -94,7 +94,7 @@ Procedure
Select a namespace and label it with **istio-injection=enabled**. After being restarted, all pods in the namespace will be automatically injected with an istio-proxy sidecar.
You can inject a sidecar in **Mesh Configuration** > **Sidecar Management** after the mesh is created. For details, see :ref:`Injecting a Sidecar <asm_01_0041__section65931513505>`.
If you do not configure namespace injection, you can inject a sidecar on the **Sidecar Management** tab (**Mesh Configuration** > **Sidecar Management**) after the service mesh is created. For details, see :ref:`Injecting a Sidecar <asm_01_0041__section65931513505>`.
- **Restart Existing Services**

2
umn/source/user_guide/creating_a_service_mesh/index.rst
View File

@ -5,7 +5,7 @@
Creating a Service Mesh
=======================
- :ref:`Creating a Service Mesh <asm_01_0084>`
- :ref:`Creating a Service Mesh <asm_01_0020>`
.. toctree::
:maxdepth: 1

28
umn/source/user_guide/mesh_configuration/sidecar_management.rst
View File

@ -5,26 +5,40 @@
Sidecar Management
==================
On the **Sidecar Management** page, you can view information about all workloads injected with sidecars, perform sidecar injection, and configure sidecar resource limits.
On the **Sidecar Management** tab, you can view information about all workloads injected with sidecars, inject sidecars, and configure sidecar resource limits.
.. _asm_01_0041__section65931513505:
Injecting a Sidecar
-------------------
You can view the namespace and cluster to which the injected sidecar belongs. If no sidecar has been injected or you need to inject sidecar for more namespaces, perform the following operations:
You can view the namespace and cluster that the injected sidecar belongs to. If no sidecar has been injected or you need to inject sidecars for more namespaces, perform the following operations:
#. Log in to the ASM console and click the name of the target service mesh to go to its details page.
#. In the navigation pane, choose **Mesh Configuration**. Then click the **Sidecar Management** tab.
#. Click **Sidecar Management**, select a namespace, determine whether to restart the existing services, and click **OK**.
- **Namespace**: Select one or more namespaces. The system labels the namespaces with **istio-injection=enabled**.
#. In the navigation pane, choose **Mesh Configuration**. Then, click the **Sidecar Management** tab.
#. Click **Sidecar Management**, select a namespace, determine whether enable **Restart Existing Services**, and click **OK**.
Parameter description:
- **Namespace**: Select one or more namespaces. The system adds labels for namespaces based on Istio versions.
- **istio-injection=enabled** can be used in Istio 1.13.9-r3 and earlier versions, as well as Istio 1.15.5-r2 and earlier versions.
- **istio.io/rev=<revision>** can be used in Istio later than 1.13.9-r3, Istio later than 1.15.5-r2, and all Istio 1.18 versions.
- **Restart Existing Services**
|image1|: Pods of the existing services in the namespace will be restarted, which will temporarily interrupt your services. The **istio-proxy** sidecar is automatically injected into the pods of the existing services.
|image1|: Enabling **Restart Existing Services** will restart the associated pods and temporarily interrupt your services. New pods will have istio-proxy sidecars automatically injected.
|image2|: The **istio-proxy** sidecar cannot be automatically injected into the pods of the existing services. You need to manually restart the workloads on the CCE console to inject the sidecar. Whether to restart existing services affects only existing services. If the namespaces are labeled with **istio-injection=enabled**, sidecars will be automatically injected into new pods.
- If you select a new namespace, an automatic injection label is added. After all pods running the Deployment in that namespace are restarted, the istio-proxy sidecars will be automatically injected into new pods.
- If you deselect a namespace, the automatic injection label is deleted. After all pods running the Deployment in that namespace are restarted, new pods do not have istio-proxy sidecars.
- If there are pods that are not injected with sidecars in selected namespaces, all pods running the Deployment will be restarted to inject sidecars. If all pods have sidecars injected, the pods will not be restarted.
|image2|: When you do not enable **Restart Existing Services**, the istio-proxy sidecars cannot be automatically injected into the associated pods. You need to manually restart the workload on the CCE console to inject sidecars. This parameter affects only existing services. If the namespaces are labeled with **istio-injection=enabled**, sidecars will be automatically injected into new pods.
- **Traffic Interception Settings**

4
umn/source/user_guide/mesh_configuration/upgrades/features_in_v1.18.rst
View File

@ -6,8 +6,8 @@ Features in v1.18
=================
- Istio 1.18 is supported.
- CCE Turbo clusters v1.25, v1.27, and v1.28 are supported.
- CCE clusters v1.25, v1.27, and v1.28 are supported.
- CCE Turbo clusters v1.25, v1.27, v1.28, v1.29, and v1.30 are supported.
- CCE clusters v1.25, v1.27, v1.28, v1.29, and v1.30 are supported.
- Kubernetes Gateway API is supported.
For details, visit https://istio.io/latest/news/releases/1.18.x/.

54
umn/source/user_guide/service_management/manual_fixing_items/all_pods_have_sidecars_injected.rst
View File

@ -15,27 +15,58 @@ Rectification Guide
#. Log in to the ASM console and click the name of the service mesh that the Service is added to. Choose **Mesh Configuration** in the navigation pane, click the **Sidecar Management** tab, and check whether a sidecar is injected into the namespace that the Service belongs to.
- If no, go to :ref:`2 <asm_01_0063__li1665121115612>`.
- If yes, go to :ref:`3 <asm_01_0063__li127525055610>`.
- If the sidecar is not injected into the namespace, go to :ref:`2 <asm_01_0063__li1665121115612>`.
- If the sidecar has been injected into the namespace, go to :ref:`3 <asm_01_0063__li127525055610>`.
Check method:
On the CCE console, click the cluster name to access the cluster console. In the navigation pane, choose **Namespaces**. On the displayed page, locate your namespace and click **Edit YAML** in the **Operation** column. If there is the **istio.io/rev=<revision>** or **istio-injection=enabled** label, the sidecar has been injected.
.. note::
- There must the **istio-injection=enabled** label for Istio 1.13.9-r3 and earlier versions, as well as Istio 1.15.5-r2 and earlier versions. Note that the version numbers are combined by hyphens (-).
- There must be the **istio.io/rev=<revision>** label for Istio later than 1.13.9-r3, Istio later than 1.15.5-r2, and all Istio 1.18 versions. Note that the version numbers are combined by hyphens (-).
|image1|
#. .. _asm_01_0063__li1665121115612:
Inject a sidecar.
Inject a sidecar into a workload or inject sidecars into the pods of all workloads in the namespace. For details, see :ref:`Injecting a Sidecar <asm_01_0041__section65931513505>`.
You can inject sidecars for pods of all workloads in the namespace. For details, see :ref:`Injecting a Sidecar <asm_01_0041__section65931513505>`. You can also inject sidecars for a workload as follows:
Injection methods:
a. Label the namespace where the workload is located with **istio-injection=enabled**.
- To inject sidecars into the pods of all workloads in the namespace, run the following command to add a label to the namespace (the label varies depending on the Istio version):
**kubectl label ns** <namespace> **istio-injection=enabled**
.. code-block::
b. Add the **annotations** field for the workload on the CCE console.
kubectl label ns <namespace> istio-injection=enabled
Or
.. code-block::
kubectl label ns <namespace> istio.io/rev=<revision>
.. note::
The system adds labels for namespaces based on Istio versions.
- **istio-injection=enabled** can be used in Istio 1.13.9-r3 and earlier versions, as well as Istio 1.15.5-r2 and earlier versions.
- **istio.io/rev=<revision>** can be used in Istio later than 1.13.9-r3, Istio later than 1.15.5-r2, and all Istio 1.18 versions.
- Injecting a sidecar into a workload
On the CCE console, locate the target workload, choose **More** > **Edit YAML** in the **Operation** column, and manually add the **annotations** field.
.. code-block::
annotations:
sidecar.istio.io/inject: 'true'
|image1|
|image2|
For more details about sidecar injection, see `Installing the Sidecar <https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/>`__.
@ -49,11 +80,12 @@ Rectification Guide
On the CCE console, choose **More** > **Edit YAML** in the **Operation** column of the target workload, and check whether **spec.template.spec.hostNetwork: true** is configured. If yes, check whether this field can be deleted or set to **false**. Otherwise, sidecars cannot be injected.
|image2|
|image3|
#. Check whether the number of pods exceeds the service mesh scale.
If the number exceeds , the excess pods cannot be injected with sidecars.
.. |image1| image:: /_static/images/en-us_image_0000001394586873.png
.. |image2| image:: /_static/images/en-us_image_0000001344069664.png
.. |image1| image:: /_static/images/en-us_image_0000002086005592.png
.. |image2| image:: /_static/images/en-us_image_0000001394586873.png
.. |image3| image:: /_static/images/en-us_image_0000001344069664.png