6.4. Troubleshooting GitOps
If you have problems with your GitOps controller, you can use the OpenShift CLI (oc) tool.
6.4.1. Debugging GitOps with oc adm inspect リンクのコピーリンクがクリップボードにコピーされました!
リンクのコピーリンクがクリップボードにコピーされました!
You can debug GitOps by using the OpenShift CLI (oc).
Prerequisites
-
The
occommand-line tool is installed.
Procedure
Run the
oc adm inspectcommand when in the GitOps namespace:$ oc adm inspect ns/openshift-gitopsExample output
Gathering data for ns/openshift-gitops... W0501 20:34:35.978508 57625 util.go:118] the server doesn't have a resource type egressfirewalls, skipping the inspection W0501 20:34:35.980881 57625 util.go:118] the server doesn't have a resource type egressqoses, skipping the inspection W0501 20:34:36.040664 57625 util.go:118] the server doesn't have a resource type servicemonitors, skipping the inspection Wrote inspect data to inspect.local.2673575938140296280.
Next steps
-
If
oc adm inspectdid not provide the information you need, you can run an sos report.