Test virtualservices

README.md

@@ -2,6 +2,15 @@
 
 Work in progress umbrella package
 
+## Iron Bank Images
+
+Per the Charter, all Big Bang packages will leverage container images from [IronBank](https://ironbank.dsop.io/).  In order to pull these images, ImagePullSecrets must be provided to BigBang.  For developers to obtain access 
+to the images, follow the guides below.  These steps should NOT be used for production since the API keys for a user are only valid when the user is logged into [Registry1](https://registry1.dsop.io)
+
+1) Register for a free Ironbank account [Here](????)
+2) Log into the [Iron Bank Registry](https://registry1.dsop.io) and follow the directions [Here]() for obtaining your API keys.
+3) When installing BigBang, set the Helm Values `registryCredentials.username` and `registryCredentials.password` to match your Registry1 username and API token
+
 ## Usage
 
 The following examples expect a cluster with fluxv2 preinstalled.  This can be done by [installing the flux cli](https://toolkit.fluxcd.io/get-started/#install-the-flux-cli) and running `flux install`.  (TODO: Convert to IB images).

chart/templates/istio/istio-controlplane-helmrelease.yaml

@@ -36,7 +36,6 @@ spec:
     - name: values
       kind: Secret
       valuesKey: "istio.yaml"
-
   values:
     hostname: {{ .Values.hostname }}
 

chart/templates/monitoring/monitoring.yaml → chart/templates/monitoring/monitoring-helmrelease.yaml

@@ -14,7 +14,6 @@ spec:
         kind: GitRepository
         name: monitoring
         namespace: {{ .Release.Namespace }}
-
   {{- with .Values.flux }}
   interval: {{ .interval }}
   test:
@@ -43,6 +42,14 @@ spec:
     global:
       imagePullSecrets:
         - name: private-registry
+    hostname: {{ .Values.hostname }}
+    kubePrometheusStack:
+      alertmanager:
+        alertmanagerSpec:
+          image:
+            repository: registry1.dsop.io/ironbank/opensource/prometheus/alertmanager
+            tag: v0.21.0
+        enabled: true
 
     kubePrometheusStack:
       grafana: