OSDOCS CMA 2.17.2-2 Release Notes

[mburke5678]

https://issues.redhat.com/browse/OSDOCS-16900

Link to docs preview:
CMA RN -> Supported versions -- Updated version table.
CMA RN -> Custom Metrics Autoscaler Operator 2.17.2-2 release notes -- New module, text based on the text in the errata.
CMA Past Releases -> Custom Metrics Autoscaler Operator 2.17.2 release notes -- Moved from release notes to a new module in the past release notes assembly. Updated heading levels. NO CHANGES TO THE TEXT. No need to review.
CMA Past Releases -> Custom Metrics Autoscaler Operator 2.15.1-4 release notes -- Updated the mod-docs-content-type. No real preview.

[ocpdocs-previewbot]

🤖 Wed Oct 29 19:26:04 - Prow CI generated the docs preview:

https://101309--ocpdocs-pr.netlify.app/openshift-dedicated/latest/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.html
https://101309--ocpdocs-pr.netlify.app/openshift-dedicated/latest/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn-past.html
https://101309--ocpdocs-pr.netlify.app/openshift-enterprise/latest/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.html
https://101309--ocpdocs-pr.netlify.app/openshift-enterprise/latest/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn-past.html
https://101309--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.html
https://101309--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn-past.html
https://101309--ocpdocs-pr.netlify.app/openshift-rosa/latest/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.html
https://101309--ocpdocs-pr.netlify.app/openshift-rosa/latest/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn-past.html

[mburke5678]

PEER REVIEW: No change to text. Copied from the release note assembly to a new module and bumped up the heading levels. No change to the text.

[jeana-redhat]

One thing I wasn't sure whether it was a typo or not, LGTM

/remove-label merge-review-in-progress
/remove-label merge-review-needed

[jeana-redhat]

typo, or are there two Operators with similar names?

Suggested change

	This release of the Custom Metrics Autoscaler Operator 2.17.2-2 is a rebuild of the 2.17.2 version of the Custom Metrics Autoscaler Operator using a newer base image and Go compiler. There are no code changes to the Custom Metrics Operator. The following advisory is available for the Custom Metrics Autoscaler Operator:
	This release of the Custom Metrics Autoscaler Operator 2.17.2-2 is a rebuild of the 2.17.2 version of the Custom Metrics Autoscaler Operator using a newer base image and Go compiler. There are no code changes to the Custom Metrics Autoscaler Operator. The following advisory is available for the Custom Metrics Autoscaler Operator:

[jeana-redhat]

We stopped adding bold to the bug links in the core RNs (because of docs.redhat.com styling), idk if you want to do the same here or not

[openshift-ci]

@mburke5678: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[mburke5678]

/cherrypick enterprise-4.12

[mburke5678]

/cherrypick enterprise-4.13

[mburke5678]

/cherrypick enterprise-4.14

[mburke5678]

/cherrypick enterprise-4.15

[mburke5678]

/cherrypick enterprise-4.16

[mburke5678]

/cherrypick enterprise-4.17

[mburke5678]

/cherrypick enterprise-4.18

[mburke5678]

/cherrypick enterprise-4.19

[mburke5678]

/cherrypick enterprise-4.20

[mburke5678]

/cherrypick enterprise-4.21

[openshift-cherrypick-robot]

@mburke5678: #101309 failed to apply on top of branch "enterprise-4.12":

Applying: CMA 2.17.2-2 Release Notes
.git/rebase-apply/patch:74: trailing whitespace.
The KEDA controller is now automatically created when you install the Custom Metrics Autoscaler Operator. Previously, you needed to manually create the KEDA controller. You can edit the automatically-created KEDA controller, as needed. 
.git/rebase-apply/patch:166: trailing whitespace.
* Previously, the `custom-metrics-autoscaler` and `custom-metrics-autoscaler-adapter` images were missing time zone information. As a consequence, scaled objects with `cron` triggers failed to work because the controllers were unable to find time zone information. With this fix, the image builds are updated to include time zone information. As a result, scaled objects containing `cron` triggers now function properly. (link:https://issues.redhat.com/browse/OCPBUGS-32395[OCPBUGS-32395]) 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
Falling back to patching base and 3-way merge...
Auto-merging nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
CONFLICT (content): Merge conflict in nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 CMA 2.17.2-2 Release Notes

In response to this:

/cherrypick enterprise-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@mburke5678: #101309 failed to apply on top of branch "enterprise-4.13":

Applying: CMA 2.17.2-2 Release Notes
.git/rebase-apply/patch:74: trailing whitespace.
The KEDA controller is now automatically created when you install the Custom Metrics Autoscaler Operator. Previously, you needed to manually create the KEDA controller. You can edit the automatically-created KEDA controller, as needed. 
.git/rebase-apply/patch:166: trailing whitespace.
* Previously, the `custom-metrics-autoscaler` and `custom-metrics-autoscaler-adapter` images were missing time zone information. As a consequence, scaled objects with `cron` triggers failed to work because the controllers were unable to find time zone information. With this fix, the image builds are updated to include time zone information. As a result, scaled objects containing `cron` triggers now function properly. (link:https://issues.redhat.com/browse/OCPBUGS-32395[OCPBUGS-32395]) 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
Falling back to patching base and 3-way merge...
Auto-merging nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
CONFLICT (content): Merge conflict in nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 CMA 2.17.2-2 Release Notes

In response to this:

/cherrypick enterprise-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@mburke5678: #101309 failed to apply on top of branch "enterprise-4.14":

Applying: CMA 2.17.2-2 Release Notes
.git/rebase-apply/patch:74: trailing whitespace.
The KEDA controller is now automatically created when you install the Custom Metrics Autoscaler Operator. Previously, you needed to manually create the KEDA controller. You can edit the automatically-created KEDA controller, as needed. 
.git/rebase-apply/patch:166: trailing whitespace.
* Previously, the `custom-metrics-autoscaler` and `custom-metrics-autoscaler-adapter` images were missing time zone information. As a consequence, scaled objects with `cron` triggers failed to work because the controllers were unable to find time zone information. With this fix, the image builds are updated to include time zone information. As a result, scaled objects containing `cron` triggers now function properly. (link:https://issues.redhat.com/browse/OCPBUGS-32395[OCPBUGS-32395]) 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
Falling back to patching base and 3-way merge...
Auto-merging nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
CONFLICT (content): Merge conflict in nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 CMA 2.17.2-2 Release Notes

In response to this:

/cherrypick enterprise-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@mburke5678: #101309 failed to apply on top of branch "enterprise-4.15":

Applying: CMA 2.17.2-2 Release Notes
.git/rebase-apply/patch:74: trailing whitespace.
The KEDA controller is now automatically created when you install the Custom Metrics Autoscaler Operator. Previously, you needed to manually create the KEDA controller. You can edit the automatically-created KEDA controller, as needed. 
.git/rebase-apply/patch:166: trailing whitespace.
* Previously, the `custom-metrics-autoscaler` and `custom-metrics-autoscaler-adapter` images were missing time zone information. As a consequence, scaled objects with `cron` triggers failed to work because the controllers were unable to find time zone information. With this fix, the image builds are updated to include time zone information. As a result, scaled objects containing `cron` triggers now function properly. (link:https://issues.redhat.com/browse/OCPBUGS-32395[OCPBUGS-32395]) 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
Falling back to patching base and 3-way merge...
Auto-merging nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
CONFLICT (content): Merge conflict in nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 CMA 2.17.2-2 Release Notes

In response to this:

/cherrypick enterprise-4.15

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@mburke5678: #101309 failed to apply on top of branch "enterprise-4.16":

Applying: CMA 2.17.2-2 Release Notes
.git/rebase-apply/patch:74: trailing whitespace.
The KEDA controller is now automatically created when you install the Custom Metrics Autoscaler Operator. Previously, you needed to manually create the KEDA controller. You can edit the automatically-created KEDA controller, as needed. 
.git/rebase-apply/patch:166: trailing whitespace.
* Previously, the `custom-metrics-autoscaler` and `custom-metrics-autoscaler-adapter` images were missing time zone information. As a consequence, scaled objects with `cron` triggers failed to work because the controllers were unable to find time zone information. With this fix, the image builds are updated to include time zone information. As a result, scaled objects containing `cron` triggers now function properly. (link:https://issues.redhat.com/browse/OCPBUGS-32395[OCPBUGS-32395]) 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
Falling back to patching base and 3-way merge...
Auto-merging nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
CONFLICT (content): Merge conflict in nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 CMA 2.17.2-2 Release Notes

In response to this:

/cherrypick enterprise-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@mburke5678: #101309 failed to apply on top of branch "enterprise-4.17":

Applying: CMA 2.17.2-2 Release Notes
.git/rebase-apply/patch:74: trailing whitespace.
The KEDA controller is now automatically created when you install the Custom Metrics Autoscaler Operator. Previously, you needed to manually create the KEDA controller. You can edit the automatically-created KEDA controller, as needed. 
.git/rebase-apply/patch:166: trailing whitespace.
* Previously, the `custom-metrics-autoscaler` and `custom-metrics-autoscaler-adapter` images were missing time zone information. As a consequence, scaled objects with `cron` triggers failed to work because the controllers were unable to find time zone information. With this fix, the image builds are updated to include time zone information. As a result, scaled objects containing `cron` triggers now function properly. (link:https://issues.redhat.com/browse/OCPBUGS-32395[OCPBUGS-32395]) 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
Falling back to patching base and 3-way merge...
Auto-merging nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
CONFLICT (content): Merge conflict in nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 CMA 2.17.2-2 Release Notes

In response to this:

/cherrypick enterprise-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@mburke5678: #101309 failed to apply on top of branch "enterprise-4.18":

Applying: CMA 2.17.2-2 Release Notes
.git/rebase-apply/patch:74: trailing whitespace.
The KEDA controller is now automatically created when you install the Custom Metrics Autoscaler Operator. Previously, you needed to manually create the KEDA controller. You can edit the automatically-created KEDA controller, as needed. 
.git/rebase-apply/patch:166: trailing whitespace.
* Previously, the `custom-metrics-autoscaler` and `custom-metrics-autoscaler-adapter` images were missing time zone information. As a consequence, scaled objects with `cron` triggers failed to work because the controllers were unable to find time zone information. With this fix, the image builds are updated to include time zone information. As a result, scaled objects containing `cron` triggers now function properly. (link:https://issues.redhat.com/browse/OCPBUGS-32395[OCPBUGS-32395]) 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
Falling back to patching base and 3-way merge...
Auto-merging nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
CONFLICT (content): Merge conflict in nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 CMA 2.17.2-2 Release Notes

In response to this:

/cherrypick enterprise-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@mburke5678: #101309 failed to apply on top of branch "enterprise-4.19":

Applying: CMA 2.17.2-2 Release Notes
.git/rebase-apply/patch:74: trailing whitespace.
The KEDA controller is now automatically created when you install the Custom Metrics Autoscaler Operator. Previously, you needed to manually create the KEDA controller. You can edit the automatically-created KEDA controller, as needed. 
.git/rebase-apply/patch:166: trailing whitespace.
* Previously, the `custom-metrics-autoscaler` and `custom-metrics-autoscaler-adapter` images were missing time zone information. As a consequence, scaled objects with `cron` triggers failed to work because the controllers were unable to find time zone information. With this fix, the image builds are updated to include time zone information. As a result, scaled objects containing `cron` triggers now function properly. (link:https://issues.redhat.com/browse/OCPBUGS-32395[OCPBUGS-32395]) 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
Falling back to patching base and 3-way merge...
Auto-merging nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
CONFLICT (content): Merge conflict in nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 CMA 2.17.2-2 Release Notes

In response to this:

/cherrypick enterprise-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@mburke5678: new pull request created: #101370

In response to this:

/cherrypick enterprise-4.20

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@mburke5678: new pull request created: #101371

In response to this:

/cherrypick enterprise-4.21

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.