Ingress for Monitoring services

Description

Sets up Ingress for Grove monitoring services.

Supporting information

• https://tasks.opencraft.com/browse/SE-5470

Testing instructions

• Retrieve your cluster's external ip with ./kubectl get services -nkube-system ingress-nginx-controller

• Create an A Record that points *.your-domain to that IP.

  • If on local you can just add lines in your hosts file.

• Add the variables to the CI or cluster.yml:

  • TF_VAR_domain_monitoring to the base domain.
  • TF_VAR_lets_encrypt_notification_inbox: to a valid email.
  • TF_VAR_enable_monitoring_ingress: true

• ./tf plan && ./tf apply

• You will be able to visit the ingress domains now.

  • prometheus.: https://prometheus.keith-ingress.dev.opencraft.hosting
  • grafana.: https://grafana.keith-ingress.dev.opencraft.hosting
  • alert-manager.: https://alert-manager.keith-ingress.dev.opencraft.hosting
  • opensearch-dashboard.: https://opensearch-dashboard.keith-ingress.dev.opencraft.hosting

• By default the routes are protected with HTTP Basic Auth. The username is admin and the password can be obtained with ./tf output -raw monitoring_ingress_password [for the above the password is: sxey6EUqS2cVx0vViwHHIUurevDvlSLV

• SSL certificates should be provisioned using LetsEncrypt if possible. Otherwise a self-signed certificate will be used.

Checklist

If any of the items below is not applicable, do not remove them, but put a check in it.

• All providers include the new feature/change
• All affected providers can provision new clusters
• Unit tests are added/updated
• Documentation is added/updated
• The TOOLS_CONTAINER_IMAGE_VERSION in ci_vars.yml is updated
• The grove-template repository is updated