vizier-operator does not use global.proxy setting therefore cannot deploy without direct internet access

vizier-operator does not utilise global.proxy setting therefore cannot deploy without direct internet access

Steps to Reproduce

Steps:
Run the new relic pixie install using CLI or Helm 3 with the global.proxy pararmeter.
Check the vizier-operator pod logs and newrelic-bundle-newrelic-pixie logs

#Expected Result
Vizier container should have launched making a pl-cluster-secrets secret

Relevant Logs / Console output

Error from newrelic-bundle-newrelic-pixie:
CreateContainerConfigError (secret "pl-cluster-secrets" not found)

Error from Vizier pod:
time="2022-11-05T09:09:09Z" level=info msg="Reconciling Vizier..." req=newrelic/pixie
time="2022-11-05T09:09:09Z" level=info msg="Creating a new vizier instance"
time="2022-11-05T09:09:09Z" level=error msg="Failed to get latest Vizier version" error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 34.102.151.106:443: connect: connection refused""
time="2022-11-05T09:09:09Z" level=info msg="Failed to deploy new Vizier instance" error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 34.102.151.106:443: connect: connection refused""

Your Environment

On Premise Kubenetes cluster:
✔ Kernel version > 4.14.0
✔ Cluster type is supported
✔ K8s version > 1.16.0
✔ Kubectl > 1.10.0 is present

Additional context

NewRelic K8S integration connects fine, it is just pixie that seems to ignore the proxy parameter

Start by tracing the global.proxy value from the CLI or Helm 3 installation into the vizier-operator deployment path, then compare it with the working New Relic Kubernetes integration. Reproduce the offline installation and inspect the vizier-operator and newrelic-bundle-newrelic-pixie logs; done means the Vizier container launches and creates the pl-cluster-secrets secret without direct internet access.