Updating the Namespace Injection Configuration of a Mesh
Function
This API is used to update the namespace injection configuration of a mesh.
Calling Method
For details, see Calling APIs.
Authorization Information
Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.
- If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
- If you are using identity policy-based authorization, the following identity policy-based permissions are required.
URI
PUT /v2/meshes/{mesh_id}/injection
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| mesh_id | Yes | String | Mesh ID |
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| X-Auth-Token | Yes | String | API calling can be authenticated using a token or AK/SK. If you use a token, this parameter is mandatory and must be set to the token. |
| Content-Type | Yes | String | Message body type (format) Range: |
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| clusterId | No | String | Cluster ID |
| restartNamespacePod | Yes | Boolean | Whether to restart the workload in the namespace |
| InjectNamespaces | Yes | Array of strings | Namespaces where sidecars will be injected |
| allowNsInject | No | Boolean | Whether the namespace injection is allowed in the mesh configuration |
| namespaces | No | Map<String,Injection> | Namespace injection configuration details |
| errMsg | No | String | Error message |
Response Parameters
Status code: 200
The namespace injection configuration of the mesh is updated.
Status code: 500
| Parameter | Type | Description |
|---|---|---|
| errorCode | String | Error code |
Example Requests
None
Example Responses
None
Status Codes
| Status Code | Description |
|---|---|
| 200 | The namespace injection configuration of the mesh is updated. |
| 500 | Internal error. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot