fix: pin istio versions

Unpinned versions caused version mismatch in deployed helm charts and
deployed container images.

Author: denniseffing

infrastructure/istio/helmfile.d/05-istio-base.yaml

@@ -10,3 +10,4 @@ releases:
   - name: istio-base
     namespace: istio-system
     chart: istio/base
+    version: 1.12.5

infrastructure/istio/helmfile.d/06-istio-cni.yaml

@@ -10,4 +10,5 @@ releases:
   - name: istio-cni
     namespace: kube-system
     chart: istio/cni
+    version: 1.12.5
     installed: {{ eq .Environment.Name "cni" | toYaml }}

infrastructure/istio/helmfile.d/10-istiod.yaml

@@ -10,6 +10,7 @@ releases:
   - name: istiod
     namespace: istio-system
     chart: istio/istiod
+    version: 1.12.5
     wait: true
     values:
       - ./values/istiod.values.yaml.gotmpl

infrastructure/istio/helmfile.d/11-istio-ingress.yaml

@@ -12,6 +12,7 @@ releases:
   - name: istio-ingressgateway
     namespace: istio-ingress
     chart: istio/gateway
+    version: 1.12.5
     # this fails the installation because helm waits for the loadbalancer to get an ip.
     # But the IP is not available until someone runs minikube tunnel
     #wait: true

infrastructure/istio/helmfile.d/values/istiod.values.yaml.gotmpl

@@ -1,5 +1,5 @@
 global:
-  tag: 1.12.2
+  tag: 1.12.5
   tracer:
     zipkin:
       address: jaeger-collector.istio-system.svc.cluster.local:9411