[Action] Make Grafana dashboards publicly accessible from cluster

[rossf7]

This issue is to make our Grafana dashboards public accessible from our Equinix cluster.

We already have the Kepler dashboard deployed by Flux #16

For #20 we want to be able to visualize the metrics we are interested in collecting.

Tasks

• Enable Grafana ingress via helm chart Exposing Grafana dashboards publicly accessible from cluster using ingress #42
• Add Equinix elastic IP to worker node running Grafana via tofu
• Create DNS entry tag-env-green-reviews.cncf.io that routes to elastic IP
• Install cert-manager and create cert for tag-env-green-reviews.cncf.io

Networking

• Currently the Equinix cluster managed by opentofu doesn't have a publicly accessible Ingress or Gateway API
• We can configure elastic IPs for our Equinix nodes via the TF provider https://deploy.equinix.com/developers/docs/metal/networking/elastic-ips/
• We have Traefik deployed as an ingress controller as part of K3s
• kube-prometheus-stack helm chart lets us deploy an ingress for Grafana
• We can deploy cert-manager with LetsEncrypt to have an SSL cert

Open Questions

• How do we get a publicly accessible DNS entry? e.g. tag-env-green-reviews.cncf.io

[dipankardas011]

I Can help with this issue

[rossf7]

@dipankardas011 thanks for taking #30

@greenscale-nandesh thanks for taking this one. As of #36 the K3s install of Traefik is now deployed to the cluster.

As a starting point it would be worth investigating if we can enable the Grafana ingress via the kube-prometheus-stack helm chart

https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack

We can then look into getting a DNS entry and cert. We should also investigate adding an elastic IP to the worker node.
https://deploy.equinix.com/developers/docs/metal/networking/elastic-ips/

Nandesh, let me know if anything is unclear or you want to sync on this.

[rossf7]

We would like to have a DNS record for the cluster so we can have public grafana dashboards.

e.g. tag-env-green-reviews.cncf.io

@leonardpahlke Could you help with this?

[leonardpahlke]

Yes. I can open a ticket once we have an elastic IP and a dashboard to display smth. I would ask for green-reviews.tag-env-sustainability.cncf.io

[rossf7]

@nikimanoledaki @leonardpahlke @AntonioDiTuri Grafana is now available via the elastic ip '147.75.40.83' should we go with green-reviews.tag-env-sustainability.cncf.io as the domain?

You can access it at http://147.75.40.83/

[dipankardas011]

Given: docs/home page tag-env-sustainability.cncf.io

we have this subdomain *.green-reviews.tag-env-sustainability.cncf.io

[dipankardas011]

for what all things we need to decide the domain for?

[leonardpahlke]

We can get the domain registered. If we plan to have other pages too we could also opt for dash-green-reviews.tag-env-sustainability.cncf.io or dash.green-reviews.tag-env-sustainability.cncf.io & later docs.greeen-reviews.tag-env-sustainability.cncf.io.

[AntonioDiTuri]

+1 For

• dash.green-reviews.tag-env-sustainability.cncf.io
• docs.greeen-reviews.tag-env-sustainability.cncf.io

[rossf7]

I think the dashboard is the primary site so what about using green-reviews.tag-env-sustainability.cncf.io for that?

+1 for docs.green-reviews.tag-env-sustainability.cncf.io

[dipankardas011]

I think the dashboard is the primary site so what about using green-reviews.tag-env-sustainability.cncf.io for that?

what about grafana.green-reviews.tag-env-sustainability.cncf.io for the dasbooard
😄

[dipankardas011]

for the docs it might be good if we keep it as the root of the subdomain and all other in the subdomain like *.green-reviews...

[rossf7]

@leonardpahlke like we agreed in WG meeting domain will be dash.green-reviews.tag-env-sustainability.cncf.io and the elastic IP is 147.75.40.83

[leonardpahlke]

👍 - 147.75.40.83 leads to a Grafana page where you need to provide credentials. Do we plan to make this page public?

[leonardpahlke]

will wait for #65 (comment) - so we register both CNAME’s at once

[dipankardas011]

had one question what are we going to use nginx lb or nginx gateway api?

[rossf7]

147.75.40.83 leads to a Grafana page where you need to provide credentials. Do we plan to make this page public?

@leonardpahlke We can share the SCI dashboard publicly but it will need code changes because we use template variables which is not supported grafana/grafana#67346 (comment)

had one question what are we going to use nginx lb or nginx gateway api?

@dipankardas011 Grafana already has an ingress managed via the helm chart. We use the traefik ingress controller that ships with k3s.

We will likely need to add cert-manager to the cluster managed by Flux and configure LetsEncrypt to issue a cert. Once the domain is set up we can add that.

[leonardpahlke]

@leonardpahlke like we agreed in WG meeting domain will be dash.green-reviews.tag-env-sustainability.cncf.io and the elastic IP is 147.75.40.83

opened a servicedesk ticket