Configure and validate that Gateway pulls images from registry1

Description

It was found that images for Istio Gateway are not pulling from registry1.

Expected Outcome

1. Set global values in the Istiod value.yaml for the Istio Gateway package.
2. Validate that images are pulled from https://registry1.dso.mil in a test deployment.

changed milestone to %2.33.0

added istio kindmaintenance priority6 statusdoing teamService Mesh labels

set weight to 1

assigned to @lgomez2

added to epic big-bang&352 (closed)

changed iteration to Big Bang Iterations Jul 23, 2024 - Aug 5, 2024

created branch 5-configure-and-validate-that-gateway-pulls-images-from-registry1 to address this issue

mentioned in merge request !6 (merged)

changed the description

created branch 5-configure-and-validate-that-gateway-pulls-images-from-registry1-2 to address this issue

mentioned in issue big-bang/bigbang#2214 (closed)

I added the imagePullSecret in the chart/values.yaml.

I also ran a test deployment in a k3d cluster and verified that the image for the gateway pod is getting pulled from registry1 and referencing the correct pull secret. The secret needs to exist in the namespace prior to running the helm deploy.

removed statusdoing label

added statusreview label

mentioned in merge request istiod!15

I opened a new Istiod MR #15 to rework how image pull values are handled for the Istiod and Gateway charts. There is now global set values in the Istiod package that gets consumed by both Istiod and Gatway deployments.

Global image pull values in the Istiod package have been tested and validated for both Istiod and Gateway deployments.

changed weight to 3 from 1

changed the description

mentioned in commit ce692153

closed with merge request !6 (merged)

added priority5 label and removed priority6 label