Istio Helm Chart Deployment Gaps Causing Cert Creation Failure in aks Cluster

Due to migration from agic gateway to istio gateway, there are a few gaps in the istio helm chart deployment that are causing Letsencrypt certificate creation failures in the aks cluster.

1. Certificate is not re-created in synch job when DNS Host/CN changes. Cert is only regenerated when it expires. This gap leads to mismatching SSL between what istio gateway expects and the cert in kv. Thus Bad Gateway error when request is send to the OSDU instance.
2. ingress-cert secret in istio-system namespace is conflicting with common-ingress cert in the osdu namespace causing cert creation challenging phase stuck and cert creation failure. Thus Bad Gateway error when request is send to the OSDU instance.