lboka/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/asm/umn/asm_faq_0036.html
Dong, Qiu Jian ec0b45029f ASM UMN initial version -20240425 
Reviewed-by: Kovács, Zoltán <zkovacs@t-systems.com>
Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
2024-09-18 09:02:28 +00:00

3.0 KiB
Raw Permalink Blame History

How Do I Enable Namespace Injection for a Cluster?

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

  1. Connect to the cluster using kubectl.
  2. 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.

  3. 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: *.*.*.*:20202/asm
      logging:
        level: default:info
      meshID: test-payment
      multiCluster:
        clusterName: test-yy
      network: test-yy-network
      proxy:
        autoInject: enabled
      remotePilotAddress: *.*.*.*
      tag: 1.8.6-r1-20220512225026

  4. 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