Expand Istio property replica counts to avoid problems when draining Istio nodes

You are currently viewing version 1.7 of the Apigee hybrid documentation. This version is end of life. You should upgrade to a newer version. For more information, see Supported versions.

Version 1.7 (unsupported)

   Supported versions:

• v1.13 (latest)                        
• v1.12                         
• v1.11                         
• List of supported versions

   Unsupported versions:

• v1.10                                      
• v1.9                                         
• v1.8                                         
• v1.7                                         
• v1.6                                         
• v1.5                                         
• v1.4                                         
• v1.3                                         
• v1.2                                         
• v1.1                                         

When draining Istio pods some nodes may not drain because they have a replica count of 1, while 3 or more replicas are required. In order to avoid this, you should set the minimum replica count for each property to at least 3.

When backing up and draining Istio nodes you may see errors like:

kubectl drain` failed to evict and reschedule pods to another node due to PodDisruptionBudget definitions:
===
NAMESPACE NAME MIN AVAILABLE MAX UNAVAILABLE ALLOWED DISRUPTIONS AGE
istio-system istio-ingressgateway 1 N/A 2 5d11h
istio-system istio-pilot 1 N/A 2 5d11h
===

For istio-ingressgateway and istio-pilot you can set the istio.ingressgateway.replicaCountMin and istio.pilot.replicaCountMin properties to 3 or higher. See the Configuration properties reference, istio.

For other istio components (that don't have a replicaCountMin property), see Manually upgrading a cluster or node pool in the GKE documentation or IstioOperator Options in the Istio documentation.