-
Notifications
You must be signed in to change notification settings - Fork 1.8k
TELCODOCS-2171#Generalize Day2Ops Troubleshooting #96100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
TELCODOCS-2171#Generalize Day2Ops Troubleshooting #96100
Conversation
a9ac20b
to
40511ec
Compare
40511ec
to
88c2eaf
Compare
|
||
toc::[] | ||
|
||
When using bare-metal deployments on {product-title}, you must pay more attention to certain configurations which can have a significant impact on cluster stability. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 [error] RedHat.TermsErrors: Use 'bare metal' rather than 'bare-metal'. For more information, see RedHat.TermsErrors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using hyphen here because it's an adjective
88c2eaf
to
3101442
Compare
:_mod-docs-content-type: ASSEMBLY | ||
[id="telco-troubleshooting-cluster-maintenance"] | ||
= Cluster maintenance | ||
include::_attributes/common-attributes.adoc[] | ||
:context: telco-troubleshooting-cluster-maintenance | ||
|
||
toc::[] | ||
|
||
In telco networks, you must pay more attention to certain configurations due the nature of bare-metal deployments. | ||
You can troubleshoot more effectively by completing these tasks: | ||
|
||
* Monitor for failed or failing hardware components | ||
* Periodically check the status of the cluster Operators | ||
[NOTE] | ||
==== | ||
For hardware monitoring, contact your hardware vendor to find the appropriate logging tool for your specific hardware. | ||
==== | ||
|
||
include::modules/telco-troubleshooting-clusters-check-cluster-operators.adoc[leveloffset=+1] | ||
include::modules/telco-troubleshooting-clusters-check-for-failed-pods.adoc[leveloffset=+1] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not deleted, just renamed: https://github.com/openshift/openshift-docs/pull/96100/files#diff-e0eb58922acf734883a6bb436240f5c31704ce2a02c0b1543652f8508e441cf8
There are also some changes to generalize the topic and remove any reference to telco
@amolnar-rh: The following test failed, say
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. |
Comment to peer reviewer: Other than |
LGTM |
Version(s):
Issue: https://issues.redhat.com/browse/TELCODOCS-2171
Link to docs preview: https://96100--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-intro
QE review:
Additional information: