Skip to content

OSDOCS -16577 [ROSA] Vale Errors: Cluster Admin#108402

Closed
jc-berger wants to merge 2 commits intoopenshift:mainfrom
jc-berger:jcberger-16577-vale-cluster-admin
Closed

OSDOCS -16577 [ROSA] Vale Errors: Cluster Admin#108402
jc-berger wants to merge 2 commits intoopenshift:mainfrom
jc-berger:jcberger-16577-vale-cluster-admin

Conversation

@jc-berger
Copy link
Copy Markdown
Contributor

@jc-berger jc-berger commented Mar 16, 2026

Version(s):
4.20+

Issue:
https://redhat.atlassian.net/browse/OSDOCS-16577

Link to docs preview:
https://108402--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/rosa_cluster_admin/rosa-cluster-notifications.html

QE review:

  • QE has approved this change.

Additional information:

@openshift-ci openshift-ci Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 16, 2026
Comment thread rosa_cluster_admin/rosa-cluster-notifications.adoc
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 16, 2026
@jc-berger jc-berger force-pushed the jcberger-16577-vale-cluster-admin branch from 6b46f2f to 2def691 Compare March 17, 2026 15:22
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 17, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Mar 17, 2026

New changes are detected. LGTM label has been removed.

@openshift-ci openshift-ci Bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Mar 17, 2026

//ROSA HCP procedure
ifdef::openshift-rosa-hcp[]
.Procedure
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewers:

Vale flagged .Procedure as a DITA violation for "block titles"

However, I see a lot of our modules do have the .Procedure title, so perhaps it's only a DITA violation when it's in an assembly?

Let me know if you want it removed or kept, thanks!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, keep the .Procedure since that's required for :_mod-docs-content-type: PROCEDURE. I would move the .procedure to line 12, then conditionalize the differences


If your cluster does not receive notifications:
[role="_additional-resources"]
.Additional resources
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewers:

I see we're allowed to have "Additional resources" for assemblies. I I documented it as .Additional resources instead of ==Additional resources because that's consistent with other files in the rosa_cluster_admin book.

For the wider ROSA docs, I see we have it documented both ways, so let me know your preference, thanks!

.Additional resources

* Ensure that your cluster can access resources at `api.openshift.com`. No newline at end of file
* link:https://docs.openshift.com/rosa/rosa_architecture/rosa_policy_service_definition/rosa-policy-responsibility-matrix.adoc#notifications_rosa-policy-responsibility-matrix[Customer responsibilities: Review and action cluster notifications] No newline at end of file
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewers:

Vale wanted me to remove xrefs, and since some of those xrefs are now include statements, I thought it's an appropriate change.

Let me know if you think the "Additional resources" here is flushed out enough though to still help users, thanks!

@jc-berger jc-berger force-pushed the jcberger-16577-vale-cluster-admin branch from 9be2df1 to cdda581 Compare March 17, 2026 17:05
@jc-berger jc-berger force-pushed the jcberger-16577-vale-cluster-admin branch from cdda581 to 40c62de Compare March 17, 2026 17:12
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Mar 17, 2026

@jc-berger: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/validate-portal 40c62de link true /test validate-portal
ci/prow/validate-asciidoc 40c62de link true /test validate-asciidoc

Full PR test history. Your PR dashboard.

Details

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.

Copy link
Copy Markdown
Contributor

@EricPonvelle EricPonvelle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small nitpicks


//ROSA HCP procedure
ifdef::openshift-rosa-hcp[]
.Procedure
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, keep the .Procedure since that's required for :_mod-docs-content-type: PROCEDURE. I would move the .procedure to line 12, then conditionalize the differences


Pods with priority lower than the cutoff value do not cause the cluster to scale up or prevent the cluster from scaling down. No new nodes are added to run the pods, and nodes running these pods might be deleted to free resources.

include::modules/rosa-cluster-autoscaler-cli-interactive-during.adoc[leveloffset=+1]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We cannot have includes within a module.

[role="_abstract"]
By default, when a cluster notification is sent to the cluster, it is also sent as an email to the cluster owner. You can configure additional recipients for notification emails to ensure that all appropriate users remain informed about the state of the cluster.

include::modules/managed-cluster-add-notification-contacts.adoc[leveloffset=+2]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as previous comment: we cannot have includes within a module.

$ rosa edit autoscaler --cluster=<mycluster>
----
+
** To edit a specific parameter, run the following command:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is just a single * because it's either editing the cluster wide autoscaler or a parameter.

[role="_abstract"]
As a cluster administrator, you need to be aware of when and why cluster notifications are sent, as well as their types and severity levels, in order to effectively understand the health and administration needs of your cluster.

include::modules/managed-cluster-notification-policy.adoc[leveloffset=+2]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as previous; cannot have includes within a module.

//
// * rosa_cluster_admin/rosa-cluster-notifications.adoc

:_mod-docs-content-type: PROCEDURE
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be a CONCEPT type.

@jc-berger
Copy link
Copy Markdown
Contributor Author

Please see this PR instead for the Vale changes: https://github.com/openshift/openshift-docs/pull/108636/changes

@jc-berger jc-berger closed this Mar 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants