Configuring Istio HA by using replica count
Enable High Availability (HA) for the Istio control plane by pinning a static replica count, which keeps the mesh available and provides a fixed level of redundancy across the istiod pods.
A static replica count fixes the size of the Istio control plane. This approach is appropriate when control plane load is steady or predictable, or when you would rather scale istiod manually instead of relying on autoscaling.
Prerequisites
- You are logged in to the Alauda Container Platform web console as a user with the
cluster-adminrole, or you have an active ACP CLI (kubectl) session as a cluster administrator. - The Alauda Service Mesh v2 Operator is installed.
- The
Istioresource has been deployed.
Configuring via the web console
Procedure
-
In the Alauda Container Platform web console, navigate to Administrator.
-
Select Marketplace > OperatorHub.
-
Search for the
Alauda Service Mesh v2. -
Locate the
Alauda Service Mesh v2and click to select it. -
Click the All Instances tab.
-
From the Filter by instance type dropdown, select
Istio. -
Click the name of the Istio installation, for example
default. -
Click the YAML tab.
-
Update the
Istiocustom resource (CR) so it resembles the following example:spec.values.pilot.autoscaleEnabledset tofalseturns off autoscaling so the replica count stays fixed at the value you define.spec.values.pilot.replicaCountsets the fixed number of Istio control plane replicas. To meet HA requirements, this value must be at least2.
Configuring via the CLI
Procedure
-
Retrieve the name of the
Istioresource:Example output
The
Istioresource is nameddefault. -
Patch the
Istiocustom resource (CR) to disable autoscaling and set a fixed replica count:For field explanations of these settings, see Configuring via the web console.
Verification
Check the status of the Istio control plane pods:
Example output
Two istiod pods are running, which is the minimum required for an HA Istio control plane and indicates that a basic HA setup is in place.