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:
- Connect to the cluster using kubectl.
- Run the kubectl get iop -nistio-system command to query iop resources.
- 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
Mesh Management FAQs
- Why Cannot I Create a Mesh for My Cluster?
- Why Are Exclusive Nodes Still Exist After Istio Is Uninstalled?
- How Do I Upgrade ICAgent?
- How Do I Enable Namespace Injection for a Cluster?
- How Do I Disable Sidecar Injection for Workloads?
- What Can I Do If A Pod Cannot Be Started Due to Unready Sidecar
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
more