OSDOCS -16577 [ROSA] Vale Errors: Cluster Admin#108402
OSDOCS -16577 [ROSA] Vale Errors: Cluster Admin#108402jc-berger wants to merge 2 commits intoopenshift:mainfrom
Conversation
6b46f2f to
2def691
Compare
|
New changes are detected. LGTM label has been removed. |
|
|
||
| //ROSA HCP procedure | ||
| ifdef::openshift-rosa-hcp[] | ||
| .Procedure |
There was a problem hiding this comment.
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!
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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!
9be2df1 to
cdda581
Compare
cdda581 to
40c62de
Compare
|
@jc-berger: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
|
||
| //ROSA HCP procedure | ||
| ifdef::openshift-rosa-hcp[] | ||
| .Procedure |
There was a problem hiding this comment.
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] |
There was a problem hiding this comment.
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] |
There was a problem hiding this comment.
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: |
There was a problem hiding this comment.
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] |
There was a problem hiding this comment.
Same as previous; cannot have includes within a module.
| // | ||
| // * rosa_cluster_admin/rosa-cluster-notifications.adoc | ||
|
|
||
| :_mod-docs-content-type: PROCEDURE |
There was a problem hiding this comment.
This should be a CONCEPT type.
|
Please see this PR instead for the Vale changes: https://github.com/openshift/openshift-docs/pull/108636/changes |
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:
Additional information: