[Stats Question] Possible to configure as backend instead of frontend? about kubernetes-ingress HOT 5 OPEN

@Mo3m3n additionally would it be possible to disable the default frontend stats? Then I could just use my own backend as normal (via an Ingress).

from kubernetes-ingress.

Hi @mecampbellsoup , the stats frontend can't be disabled. If you want to create your backend, you can. By default our script creates a service pointing to the controller. Your ingress only has to refer to it.

from kubernetes-ingress.

Hi @mecampbellsoup , the stats frontend can't be disabled. If you want to create your backend, you can. By default our script creates a service pointing to the controller. Your ingress only has to refer to it.

Yea, I ended up making an ingress that points to the metric service since, when enablePorts.stats = false, that port 1024 seems to be exposed by the metrics/Prometheus service.

In a perfect world, this particular ingress would NOT have a public IP, but since our IC is public generally I'm not sure how to accomplish that. Any ideas?

from kubernetes-ingress.

You have several options. Among them, you can secure the ingress with authentication or with allow and deny lists of IPs or CIDRs.

from kubernetes-ingress.

You have several options. Among them, you can secure the ingress with authentication or with allow and deny lists of IPs or CIDRs.

Cool, haven't used allow/deny lists yet! Thanks for the tip.

Is it possible to generate those dynamically to express something like "only people (IPs) with access to our private internal network can access the stats backend"?

from kubernetes-ingress.