Before a Java application is started, the ack-onepilot component uses init containers to prepare an ARMS agent for Java. If both ack-onepilot and Istio are used, you need to upgrade ack-onepilot to a later version or configure ack-onepilot of the earlier version, considering the different network settings in Istio and other clusters.
Step 1: Install the ack-onepilot component
You can install ack-onepilot in one of the following clusters:
Upgrading ack-onepilot to V3.0.19 or later automatically modifies the interception configurations of Istio Proxy. In this case, skip Step 2.
To disable automatic modification, upgrade ack-onepilot to V4.1.2 or later and set the environment variable
ARMS_ISTIO_AUTO_INJECT_ENABLEof ack-onepilot-ack-onepilot tofalse:Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, find the cluster you want to manage and click its name. In the left-side pane, choose .
On the Deployments page, click the ack-onepilot component. Generally, it is named ack-onepilot-ack-onepilot in the ack-onepilot namespace.
In the upper-right corner of the page that appears, click Edit.
Scroll down until you see the Environments section. Click Add, add the environment variable ARMS_ISTIO_AUTO_INJECT_ENABLE, and set the value to false.
Step 2: Modify the interception configurations of Istio Proxy
Add the following VIP ranges to the annotation of the pod. Separate the CIDR blocks with commas (,).
Take the China (Hangzhou) region as an example:
traffic.sidecar.istio.io/excludeOutboundIPRanges: "100.118.28.0/24,100.114.102.0/24,100.98.170.0/24,100.118.31.0/24"Modify the YAML file of the application and add the following
annotationto the spec.template.metadata section.