>1 replicas and PDB required

[lissff]

Right now the default replica for agic pod is 1, and no pod disruption defined; Better if we could config replicas using configmap, or it could scale up with number of numbers like coreDNS does.

[dhananjaya94]

In running in production PDB is required.

[akshaysngupta]

This will require leader election support on AGIC as multiple AGIC pod will cause multiple updates on AppGW.

Appendix: K8s docs Example PR

[atkhalsa]

When is this feature expected to be released?

[okautz]

@akshaysngupta We are also very interested in leader election support, is there any ETA on this?

We are planning on using the AGIC and AppGW in a Istio Multicluster Service Mesh in the future and want to deploy the AGIC in every cluster of the mesh to improve resilience in case of cluster breakdown or redeployment. Would it also be possible for the leader election have some sort of istio mode in which the leader is chosen from all AGIC Pods of the whole multicluster service mesh?

[MrEcco]

The community is still waiting for this essential reliability feature. Is there a chance to schedule the implementation for the near future?

It seems like the solution might be not so complex. It is possible to check service labels/annotations and do things or nothing by this flag value. Election can be run by API-requirest with object name+namespace+uid+resourceVersion (if resourceVersion in request and state are different then API always responds error). And pods can check each other or even a health state from KAPI. That is how HashiCorp helm charts and Nginx Ingress Controller do it.

[HammerNL89]

Any update on supporting this feature?