Exposing NATS monitoring outside of a kubernetes cluster

[Mike]

I'm experimenting with NATS on Kubernetes - so far I can run it in a pod and my services can connect. I'd like to make monitoring accessible outside of the cluster but I can;'t seem to get it right. I've been using this command to install via a Helm chart:

helm install stable/nats --namespace=myns --name=system-broker --set auth.enabled=true,auth.user=username,auth.password=password

I've tried using some of these additional values (among others) on the command line, but I can't seem to make monitoring accessible:

ingress.enabled=true
monitoring.service.nodePort=8222
networkPolicy.allowExternal=true
ingress.enabled=true

Is it possible to make monitoring accessible outside of the cluster using values, and if so, which ones need to be set?

I know that NATS prints the following when it is installed via Helm:

To access the Monitoring svc from outside the cluster, follow the steps below:

I followed those instructions but it doesn't work.

Thanks
Mike

[Mike]

This is the only progress I've made:

Name:             system-broker-nats-monitoring
Namespace:        mike
Address:          172.31.90.3
Default backend:  default-http-backend:80 (<none>)
Rules:
  Host                            Path  Backends
  ----                            ----  --------
  nats-monitoring.nats.local  
                                  /nats-monitor   system-broker-nats-monitoring:monitoring (<none>)
Annotations:
Events:  <none>

If I point my browser at: 172.31.90.3/nats-monitor, I get a 404 error.

Mike