[OSDOCS-20226]: Adding info about approving CSRs - #117169
Conversation
openshift-ci
Bot
added
the
size/S
|
🤖 Mon Aug 03 15:25:16 - Prow CI generated the docs preview: |
9bb2e17 to
7ba4fda
Compare
|
@lahinson: all tests passed! 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. |
| . If a CSR is not approved after the restart, you can investigate possible issues by checking the logs: | ||
| + | ||
| .. Check the Machine Approver logs by entering the following command: | ||
| + | ||
| [source,terminal] | ||
| ---- | ||
| $ oc logs -n openshift-cluster-machine-approver -l app=machine-approver | ||
| ---- | ||
| + | ||
| .. Check the Kube Controller Manager logs by entering the following command: | ||
| + | ||
| [source,terminal] | ||
| ---- | ||
| $ oc logs -n openshift-kube-controller-manager -l app=kube-controller-manager | ||
| ---- |
There was a problem hiding this comment.
It might make sense for us to be a bit more explicit as to the scenarios in which one might want to check which components logs.
Based on the README of https://github.com/openshift/cluster-machine-approver , it looks like machine-approver would be more for the scenario where CSRs for new worker nodes attempting to join the cluster have not been approved.
It looks like kube-controller-manager seems like it would be generally useful to look at logs for in CSR error scenarios as it looks like it is largely responsible for most of the CSR operations.
3 participants
Version(s): 4.21+
Issue: https://redhat.atlassian.net/browse/OSDOCS-20226
Link to docs preview: https://117169--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/graceful-cluster-restart.html#graceful-restart_graceful-restart-cluster
QE review:
Additional information: