Steve Williams

Investigation completed. Steps carried out as follows: - Created test cluster with an additional module call to create a second default ingress-controller in `ingress-controllers` namespace with `controller-name = "default-2"` -...

`divergence-live-2` pipeline PR here for ref: https://github.com/ministryofjustice/cloud-platform-terraform-concourse/pull/155

Merged to main, set by bootstrap. eks, components and networking divergence tasks running green: https://concourse.cloud-platform.service.justice.gov.uk/teams/main/pipelines/divergence-live-2/jobs/divergence-eks-live-2/builds/1 https://concourse.cloud-platform.service.justice.gov.uk/teams/main/pipelines/divergence-live-2/jobs/divergence-eks-live-2-components/builds/1 https://concourse.cloud-platform.service.justice.gov.uk/teams/main/pipelines/divergence-live-2/jobs/divergence-networking-live-2/builds/1

relates to ministryofjustice/cloud-platform#4877

This is a work in progress. 80% ish there, a couple things left to do: - Run POC in dev environment with user - Consider additional authentication layer (API key...

Discussed request and implementation approach with user. Confirmed that they can proceed with enabling custom metrics for S3 and applying required terraform resources to enable s3 request based alerts.

Milestone and associated module update tickets created: https://github.com/ministryofjustice/cloud-platform/milestone/34

The no data issue we are experiencing is due to a change applied to the Prometheus Overview default dashboard config, which now includes a cluster label for the dashboard queries....

Overview dashboard now working https://grafana.live.cloud-platform.service.justice.gov.uk/d/BNLlmx9nk/prometheus-overview-working?orgId=1&refresh=60s

Stale ticket, prometheus architecture has changed substantially since this issue.