When ArgoCD is enabled the hostname override doesn't seem to trickle to the ArgoCD add on as expected

Jan 18th - 29th was the 1st run through of the Big Bang Onboarding Residency using the new Big Bang Umbrella Helm chart implementation.
Part of the lab guides involve using mkcert to provision a self signed arbitrary HTTPS cert. *.yourname.bigbang.lab and configuring ingress for it

Setup:
I'm using BigBang Umbrella Helm Chart v1.0.1.
/mycloneofcustomertemplaterepo/dev/configmap.yaml

hostname: chrism.bigbang.lab
...
addons:
  argocd:
    enabled: true

kubectl get virtualservices -A

NAMESPACE      NAME                                      GATEWAYS                                HOSTS                               AGE
argocd         argocd-argocd-server                      [main.istio-system.svc.cluster.local]   [argocd.bigbang.dev]                18m
istio-system   jaeger                                    [main.istio-system.svc.cluster.local]   [jaeger.chrism.bigbang.lab]         4d
istio-system   kiali                                     [main.istio-system.svc.cluster.local]   [kiali.chrism.bigbang.lab]          4d
logging        kibana                                    [main.istio-system.svc.cluster.local]   [kibana.chrism.bigbang.lab]         4d
monitoring     monitoring-monitoring-kube-alertmanager   [main.istio-system.svc.cluster.local]   [alertmanager.chrism.bigbang.lab]   4d
monitoring     monitoring-monitoring-kube-grafana        [main.istio-system.svc.cluster.local]   [grafana.chrism.bigbang.lab]        4d
monitoring     monitoring-monitoring-kube-prometheus     [main.istio-system.svc.cluster.local]   [prometheus.chrism.bigbang.lab]     4d
twistlock      console                                   [main.istio-system.svc.cluster.local]   [twistlock.chrism.bigbang.lab]      4d

^-- Notice ArgoCD shows up as bigbang.dev, instead of respecting the hostname override