Skip to content

Commit 78da768

Browse files
author
Michael Burke
committed
Fix build error
1 parent d893320 commit 78da768

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,4 +60,9 @@ Before installing this version of the Custom Metrics Autoscaler Operator, remove
6060
[id="nodes-pods-autoscaling-custom-rn-2141-TBD-bugs_{context}"]
6161
=== Bug fixes
6262

63-
* Previously, if you wanted the Custom Metrics Autoscaler Operator to scrape metrics, alerts, and so forth from the `openshift-keda` namespace, you needed to select the `Enable Operator recommended cluster monitoring on this Namespace` option upon installation or xref:../../../observability/monitoring/enabling-monitoring-for-user-defined-projects.adoc#enabling-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[manually enable monitoring] for the `opensift-keda` project after installation. This option is now enabled by default upon installation of the Operator. You can xref:../../../observability/monitoring/enabling-monitoring-for-user-defined-projects.adoc#disabling-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[manually disable monitoring] for the `opensift-keda` project, as needed. (link:https://issues.redhat.com/browse/PODAUTO-242[*PODAUTO-2428*])
63+
ifndef::openshift-rosa,openshift-dedicated[]
64+
* Previously, if you wanted the Custom Metrics Autoscaler Operator to scrape metrics, alerts, and so forth from the `openshift-keda` namespace, you had to select the `Enable Operator recommended cluster monitoring on this Namespace` option upon installation or xref:../../../observability/monitoring/enabling-monitoring-for-user-defined-projects.adoc#enabling-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[manually enable monitoring] for the `opensift-keda` project after installation. This option is now enabled by default upon installation of the Operator. You can xref:../../../observability/monitoring/enabling-monitoring-for-user-defined-projects.adoc#disabling-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[manually disable monitoring] for the `opensift-keda` project, as needed. (link:https://issues.redhat.com/browse/PODAUTO-242[*PODAUTO-2428*])
65+
endif::openshift-rosa,openshift-dedicated[]
66+
ifdef::openshift-rosa,openshift-dedicated[]
67+
* Previously, if you wanted the Custom Metrics Autoscaler Operator to scrape metrics, alerts, and so forth from the `openshift-keda` namespace, you had to select the `Enable Operator recommended cluster monitoring on this Namespace` option upon installation. This option is now enabled by default upon installation of the Operator. You can xref:../../../observability/monitoring/sd-disabling-monitoring-for-user-defined-projects.html#sd-disabling-monitoring-for-user-defined-projects_sd-disabling-monitoring-for-user-defined-projects[manually disable monitoring] for the `opensift-keda` project, as needed. (link:https://issues.redhat.com/browse/PODAUTO-242[*PODAUTO-2428*])
68+
endif::openshift-rosa,openshift-dedicated[]

0 commit comments

Comments
 (0)