Ingress Examples
Last updated
Last updated
Enabling external access to the Kubecost product requires exposing access to port 9090 on the kubecost-cost-analyzer
pod. Exposing this endpoint will handle routing to Grafana as well. There are multiple ways to do this, including Ingress or Service definitions.
Please exercise caution when exposing Kubecost via an Ingress controller especially if there is no authentication in use. Consult your organization's internal recommendations.
Common samples below and others can be found on our .
The following example definitions use the NGINX .
Once an AWS Load Balancer (ALB) Controller is installed, you can use the following Ingress resource manifest pointed at the Kubecost cost-analyzer service:
Here is a that uses a Kubernetes Secret.
When deploying Grafana on a non-root URL, you also need to update your grafana.ini to reflect this. More info can be found in .