From a180a2e94c552ba8013ba3acc5f0d0351ffca73f Mon Sep 17 00:00:00 2001 From: SheryarButt Date: Wed, 6 Dec 2023 16:42:34 +0500 Subject: [PATCH] adds faq --- content/faq.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/faq.md b/content/faq.md index 0435e5e47..7266e8af6 100644 --- a/content/faq.md +++ b/content/faq.md @@ -11,3 +11,7 @@ ## Q. InvalidSpecError: application repo \ is not permitted in project \ **A.** The above error can occur if the ArgoCD Application is syncing from a source that is not allowed the referenced AppProject. To solve this, verify that you have referred to the correct project in the given ArgoCD Application, and that the repoURL used for the Application's source is valid. If the error still appears, you can add the URL to the relevant Tenant's `spec.argocd.sourceRepos` array. + +## Q. Why are there mto-showback-* pods failing in my cluster? + +**A.** The mto-showback-* pods are used to calculate the cost of the resources used by each tenant. These pods are created by the Multi-Tenant Operator and are scheduled to run every 10 mintutes. If the pods are failing, it is likely that the operator's necessary to calculate cost are not present in the cluster. To solve this, you can navigate to `Operators` -> `Installed Operators` in the OpenShift console and check if the MTO-OpenCost and MTO-Promehteus operators are installed. If they are in a pending state, you can manually approve them to install them in the cluster.