1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00

TELCODOCS-2005: Add topics to Telco Day 2 Troubleshooting and Maintenance

This commit is contained in:
Alexandra Molnar
2024-12-09 13:10:23 +00:00
committed by openshift-cherrypick-robot
parent 47f9282a62
commit 1b1f51c014
20 changed files with 483 additions and 8 deletions

View File

@@ -0,0 +1,29 @@
:_mod-docs-content-type: ASSEMBLY
[id="telco-troubleshooting-bmn-maintenance"]
= Bare-metal node maintenance
include::_attributes/common-attributes.adoc[]
:context: telco-troubleshooting-bmn-maintenance
toc::[]
You can connect to a node for general troubleshooting.
However, in some cases, you need to perform troubleshooting or maintenance tasks on certain hardware components.
This section discusses topics that you need to perform that hardware maintenance.
include::modules/telco-troubleshooting-bmn-connect-to-node.adoc[leveloffset=+1]
include::modules/telco-troubleshooting-bmn-move-apps-to-pods.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* xref:../../../nodes/nodes/nodes-nodes-working.adoc#nodes-nodes-working_nodes-nodes-working[Working with nodes]
include::modules/telco-troubleshooting-bmn-replace-dimm.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* xref:../../../storage/index.adoc#storage-overview_storage-overview[{product-title} storage overview]
include::modules/telco-troubleshooting-bmn-replace-disk.adoc[leveloffset=+1]
include::modules/telco-troubleshooting-bmn-replace-nw-card.adoc[leveloffset=+1]

View File

@@ -0,0 +1,66 @@
:_mod-docs-content-type: ASSEMBLY
[id="telco-troubleshooting-cert-maintenance"]
= Certificate maintenance
include::_attributes/common-attributes.adoc[]
:context: telco-troubleshooting-cert-maintenance
toc::[]
Certificate maintenance is required for continuous cluster authentication.
As a cluster administrator, you must manually renew certain certificates, while others are automatically renewed by the cluster.
Learn about certificates in {product-title} and how to maintain them by using the following resources:
* link:https://access.redhat.com/solutions/5018231[Which OpenShift certificates do rotate automatically and which do not in Openshift 4.x?]
* link:https://access.redhat.com/solutions/7000968[Checking etcd certificate expiry in OpenShift 4]
include::modules/telco-troubleshooting-certs-manual.adoc[leveloffset=+1]
include::modules/telco-troubleshooting-certs-manual-proxy.adoc[leveloffset=+2]
[role="_additional-resources"]
.Additional resources
* xref:../../../security/certificate_types_descriptions/proxy-certificates.adoc#cert-types-proxy-certificates[Proxy certificates]
include::modules/telco-troubleshooting-certs-manual-user-provisioned.adoc[leveloffset=+2]
[role="_additional-resources"]
.Additional resources
* xref:../../../security/certificate_types_descriptions/user-provided-certificates-for-api-server.adoc#cert-types-user-provided-certificates-for-the-api-server[User-provisioned certificates for the API server]
include::modules/telco-troubleshooting-certs-auto.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* xref:../../../security/certificate_types_descriptions/service-ca-certificates.adoc#cert-types-service-ca-certificates_cert-types-service-ca-certificates[Service CA certificates]
* xref:../../../security/certificate_types_descriptions/node-certificates.adoc#cert-types-node-certificates_cert-types-node-certificates[Node certificates]
* xref:../../../security/certificate_types_descriptions/bootstrap-certificates.adoc#cert-types-bootstrap-certificates_cert-types-bootstrap-certificates[Bootstrap certificates]
* xref:../../../security/certificate_types_descriptions/etcd-certificates.adoc#cert-types-etcd-certificates-cert-types-etcd-certificates[etcd certificates]
* xref:../../../security/certificate_types_descriptions/olm-certificates.adoc#cert-types-olm-certificates_cert-types-olm-certificates[OLM certificates]
* xref:../../../security/certificate_types_descriptions/machine-config-operator-certificates.adoc#cert-types-machine-config-operator-certificates_cert-types-machine-config-operator-certificates[Machine Config Operator certificates]
* xref:../../../security/certificate_types_descriptions/monitoring-and-cluster-logging-operator-component-certificates.adoc#cert-types-monitoring-and-cluster-logging-operator-component-certificates_cert-types-monitoring-and-cluster-logging-operator-component-certificates[Monitoring and cluster logging Operator component certificates]
* xref:../../../security/certificate_types_descriptions/control-plane-certificates.adoc#cert-types-control-plane-certificates_cert-types-control-plane-certificates[Control plane certificates]
* xref:../../../security/certificate_types_descriptions/ingress-certificates.adoc#cert-types-ingress-certificates_cert-types-ingress-certificates[Ingress certificates]
include::modules/telco-troubleshooting-certs-auto-etcd.adoc[leveloffset=+2]
[role="_additional-resources"]
.Additional resources
* xref:../../../security/certificate_types_descriptions/etcd-certificates.adoc#cert-types-etcd-certificates_cert-types-etcd-certificates[etcd certificates]
include::modules/telco-troubleshooting-certs-auto-node.adoc[leveloffset=+2]
[role="_additional-resources"]
.Additional resources
* xref:../../../security/certificate_types_descriptions/node-certificates.adoc#cert-types-node-certificates_cert-types-node-certificates[Node certificates]
include::modules/telco-troubleshooting-certs-auto-service-ca.adoc[leveloffset=+2]
[role="_additional-resources"]
.Additional resources
* xref:../../../security/certificate_types_descriptions/service-ca-certificates.adoc#cert-types-service-ca-certificates_cert-types-service-ca-certificates[Service CA certificates]

View File

@@ -0,0 +1,20 @@
:_mod-docs-content-type: ASSEMBLY
[id="telco-troubleshooting-mco"]
= Machine Config Operator
include::_attributes/common-attributes.adoc[]
:context: telco-troubleshooting-mco
toc::[]
The Machine Config Operator provides useful information to cluster administrators and controls what is running directly on the bare-metal host.
The Machine Config Operator differentiates between different groups of nodes in the cluster, allowing control plane nodes and worker nodes to run with different configurations.
These groups of nodes run worker or application pods, which are called `MachineConfigPool` (`mcp`) groups.
The same machine config is applied on all nodes or only on one MCP in the cluster.
For more information about how and why to apply MCPs in a telco core cluster, see xref:../../../edge_computing/day_2_core_cnf_clusters/updating/telco-update-ocp-update-prep.adoc#telco-update-applying-mcp-labels-to-nodes-before-the-update_ocp-update-prep[Applying MachineConfigPool labels to nodes before the update].
For more information about the Machine Config Operator, see xref:../../../operators/operator-reference.adoc#machine-config-operator_cluster-operators-ref[Machine Config Operator].
include::modules/telco-troubleshooting-mco-purpose.adoc[leveloffset=+1]
include::modules/telco-troubleshooting-mco-apply-several-mcs.adoc[leveloffset=+1]

View File

@@ -0,0 +1,16 @@
:_mod-docs-content-type: ASSEMBLY
[id="telco-troubleshooting-security"]
= Security
include::_attributes/common-attributes.adoc[]
:context: telco-troubleshooting-security
toc::[]
Implementing a robust cluster security profile is important for building resilient telco networks.
include::modules/telco-troubleshooting-security-authentication.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* xref:../../../authentication/understanding-identity-provider.adoc#supported-identity-providers[Supported identity providers]