Fix link for DP-042

resources/prometheus/prometheus-rules.yaml

@@ -721,7 +721,7 @@ spec:
             summary: "Cluster Autoscaler has {{ $value }} unschedulable pods."
             description: "The cluster autoscaler is unable to scale up and is alerting that there are unschedulable pods because of this condition.
 This may be caused by the cluster autoscaler reaching its resources limits, or by Kubernetes waiting for new nodes to become ready."
-            sop_url: "https://gitlab.cee.redhat.com/stackrox/acs-cloud-service/runbooks/-/blob/master/sops/dp-041-modify-cluster-autoscaler.md"
+            sop_url: "https://gitlab.cee.redhat.com/stackrox/acs-cloud-service/runbooks/-/blob/master/sops/dp-042-modify-cluster-autoscaler.md"
         - alert: ClusterAutoscalerNotSafeToScale
           expr: cluster_autoscaler_cluster_safe_to_autoscale{service="cluster-autoscaler-default"} != 1
           for: 15m
@@ -733,7 +733,7 @@ This may be caused by the cluster autoscaler reaching its resources limits, or b
 and it is not safe to continute scaling operations. It makes this determination by checking that the number of ready nodes is greater than the minimum ready count
 (default of 3) and the ratio of unready to ready nodes is less than the maximum unready node percentage (default of 45%). If either of those conditions are not
 true then the cluster autoscaler will enter an unsafe to scale state until the conditions change."
-            sop_url: "https://gitlab.cee.redhat.com/stackrox/acs-cloud-service/runbooks/-/blob/master/sops/dp-041-modify-cluster-autoscaler.md"
+            sop_url: "https://gitlab.cee.redhat.com/stackrox/acs-cloud-service/runbooks/-/blob/master/sops/dp-042-modify-cluster-autoscaler.md"
         - alert: ClusterAutoscalerUnableToScaleCPULimitReached
           expr: increase(cluster_autoscaler_skipped_scale_events_count{service="cluster-autoscaler-default",direction="up",reason="CpuResourceLimit"}[15m]) > 0
           for: 15m
@@ -744,7 +744,7 @@ true then the cluster autoscaler will enter an unsafe to scale state until the c
             description: "The number of total cores in the cluster has exceeded the maximum number set on the
 cluster autoscaler. This is calculated by summing the cpu capacity for all nodes in the cluster and comparing that number against the maximum cores value set for the
 cluster autoscaler. Limits can be adjusted by modifying the cluster autoscaler configuration."
-            sop_url: "https://gitlab.cee.redhat.com/stackrox/acs-cloud-service/runbooks/-/blob/master/sops/dp-041-modify-cluster-autoscaler.md"
+            sop_url: "https://gitlab.cee.redhat.com/stackrox/acs-cloud-service/runbooks/-/blob/master/sops/dp-042-modify-cluster-autoscaler.md"
         - alert: ClusterAutoscalerUnableToScaleMemoryLimitReached
           expr: increase(cluster_autoscaler_skipped_scale_events_count{service="cluster-autoscaler-default",direction="up",reason="MemoryResourceLimit"}[15m]) > 0
           for: 15m
@@ -755,4 +755,4 @@ cluster autoscaler. Limits can be adjusted by modifying the cluster autoscaler c
             description: "The number of total bytes of RAM in the cluster has exceeded the maximum number set on
 the cluster autoscaler. This is calculated by summing the memory capacity for all nodes in the cluster and comparing that number against the maximum memory bytes value set
 for the cluster autoscaler. Limits can be adjusted by modifying the cluster autoscaler configuration."
-            sop_url: "https://gitlab.cee.redhat.com/stackrox/acs-cloud-service/runbooks/-/blob/master/sops/dp-041-modify-cluster-autoscaler.md"
+            sop_url: "https://gitlab.cee.redhat.com/stackrox/acs-cloud-service/runbooks/-/blob/master/sops/dp-042-modify-cluster-autoscaler.md"