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
For information about how to install the ack-onepilot component in a Container Service for Kubernetes (ACK) cluster, see Automatically install an ARMS agent in ACK.
For information about how to install the ack-onepilot component in a cluster registered in ACK One, see Enable ARMS for a registered cluster.
For information about how to install the ack-onepilot component in a Kubernetes environment, see Automatically install an ARMS agent in an open source Kubernetes cluster.
If you upgrade the ack-onepilot component to 3.0.19 or later, the interception configurations of Istio Proxy are automatically modified. In this case, you do not need to perform Step 2. For information about how to upgrade the ack-onepilot component, see Manage components.
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
annotation
to the spec.template.metadata section.