On this page

Show all

Help Center/ Application Service Mesh/ FAQs/ Mesh Management/ How Do I Enable Namespace Injection for a Cluster?

How Do I Enable Namespace Injection for a Cluster?

Updated on 2023-07-03 GMT+08:00

View PDF

When injecting a sidecar to the namespace of a cluster, if the namespace injection is not enabled in the cluster, perform the following steps:

Connect to the cluster using kubectl.
Run the kubectl get iop -nistio-system command to query iop resources.
- If the following information is displayed, the iop resource exists. Go to 3.
- If the following information is displayed, no iop resources exist. Go to 4.

Run the kubectl edit iop -nistio-system data-plane command to modify the autoInject configuration item. In the preceding command, data-plane indicates the name of the iop resource queried in the previous step. Replace it with the actual value.

    global:
      defaultPodDisruptionBudget:
        enabled: true
      hub: 100.79.1.215:20202/asm
      logging:
        level: default:info
      meshID: test-payment
      multiCluster:
        clusterName: test-yy
      network: test-yy-network
      proxy:
        autoInject: enabled
      remotePilotAddress: 10.252.2.34
      tag: 1.8.6-r1-20220512225026

Run the kubectl edit cm -nistio-system istio-sidecar-injector command to modify the istio-sidecar-injector configuration item.
```
data:
  config: |-
    policy: enabled
```

Parent topic: Mesh Management

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel