Mike Bell

https://github.com/prometheus-community/helm-charts/tree/main/charts/prometheus-operator-crds This will also remove some custom code from the monitoring modules

Proposed solution using the helm chart linked above: 1. Create a new terraform module with above helm chart 2. Implement in core but don't apply 3. Create a new release...

Branch for removing prometheus crds from cloud-platform-terraform-monitoring - https://github.com/ministryofjustice/cloud-platform-terraform-monitoring/tree/remove-prom-crds Branch for migrating prometheus crds in cloud-platform-infrastructure - https://github.com/ministryofjustice/cloud-platform-infrastructure/tree/migrate-prom-crds

I've had to remove the `module.monitoring` dependency from `cluster_autoscaler` because it was showing changes when removing the crds from `components`. Needs further investigation into whether this is safe. 10 resources...

There's a new option on the`migrate-resource` called `--remove-module` this will remove the `module` key from the state on migration. I've tested this out on a test cluster and seems to...

Fly command to update the pipeline: `fly -t moj-cp set-pipeline --pipeline migrate-module --config migrate-module.yaml -v cluster_name=cp-1206-0659 -v resources_flagged=kubectl_manifest.prometheus_operator_crds -v module=null -v resources=null` * `cluster_name` - name of the cluster *...

Clean build using `custom-cluster` and passing tests on the `migrate-prom-crds` branch - https://concourse.cloud-platform.service.justice.gov.uk/teams/main/pipelines/custom-cluster/jobs/custom-integration-tests/builds/12

[tfmgirate](https://github.com/minamijoyo/tfmigrate) - doesn't appear to do what it's supposed to so discounting for now: When migrating an example resource the outputs were wildly different to what I was expecting. [terravalet](https://github.com/pix4D/terravalet)...

The pipeline is in concourse now. Gatekeeper will be moved Monday 22nd April

Completed this morning