Deployed 901b102 to 0.10 with MkDocs 1.5.3 and mike 2.0.0

0.10/faq.html

@@ -1429,6 +1429,15 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#q-why-are-there-mto-showback-pods-failing-in-my-cluster" class="md-nav__link">
+    <span class="md-ellipsis">
+      Q. Why are there mto-showback-* pods failing in my cluster?
+    </span>
+  </a>
+
 </li>
 
     </ul>
@@ -1598,6 +1607,15 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#q-why-are-there-mto-showback-pods-failing-in-my-cluster" class="md-nav__link">
+    <span class="md-ellipsis">
+      Q. Why are there mto-showback-* pods failing in my cluster?
+    </span>
+  </a>
+
 </li>
 
     </ul>
@@ -1642,6 +1660,8 @@ <h3 id="q-how-do-i-deploy-cluster-scoped-resource-via-the-argocd-integration">Q.
 <p><strong>Answer.</strong> Multi-Tenant Operator's ArgoCD Integration allows configuration of which cluster-scoped resources can be deployed, both globally and on a per-tenant basis. For a global allow-list that applies to all tenants, you can add both resource <code>group</code> and  <code>kind</code> to the <a href="how-to-guides/integration-config.html#argocd">IntegrationConfig's</a> <code>spec.argocd.clusterResourceWhitelist</code> field. Alternatively, you can set this up on a tenant level by configuring the same details within a <a href="how-to-guides/tenant.html">Tenant's</a> <code>spec.argocd.appProject.clusterResourceWhitelist</code> field. For more details, check out the <a href="tutorials/argocd/enabling-multi-tenancy-argocd.html#allow-argocd-to-sync-certain-cluster-wide-resources">ArgoCD integration use cases</a></p>
 <h2 id="q-invalidspecerror-application-repo-repo-is-not-permitted-in-project-project">Q. InvalidSpecError: application repo \&lt;repo&gt; is not permitted in project \&lt;project&gt;</h2>
 <p><strong>Answer.</strong> 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 <code>spec.argocd.sourceRepos</code> array.</p>
+<h2 id="q-why-are-there-mto-showback-pods-failing-in-my-cluster">Q. Why are there <code>mto-showback-*</code> pods failing in my cluster?</h2>
+<p><strong>Answer.</strong> The <code>mto-showback-*</code> 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 minutes. 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 <code>Operators</code> -&gt; <code>Installed Operators</code> in the OpenShift console and check if the MTO-OpenCost and MTO-Prometheus operators are installed. If they are in a pending state, you can manually approve them to install them in the cluster.</p>
 
 
 

0.10/features.html

@@ -1521,6 +1521,24 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#custom-metrics-support" class="md-nav__link">
+    <span class="md-ellipsis">
+      Custom Metrics Support
+    </span>
+  </a>
+
+</li>
+
+        <li class="md-nav__item">
+  <a href="#graph-visualization-for-tenants" class="md-nav__link">
+    <span class="md-ellipsis">
+      Graph Visualization for Tenants
+    </span>
+  </a>
+
 </li>
 
     </ul>
@@ -1589,6 +1607,14 @@ <h2 id="preventing-clusters-sprawl">Preventing Clusters Sprawl</h2>
 <p>With Multi Tenant Operator teams can share a single cluster with multiple teams, groups of users, or departments by saving operational and management efforts. This prevents you from Kubernetes cluster sprawl.</p>
 <h2 id="native-experience">Native Experience</h2>
 <p>Multi Tenant Operator provides multi-tenancy with a native Kubernetes experience without introducing additional management layers, plugins, or customized binaries.</p>
+<h2 id="custom-metrics-support">Custom Metrics Support</h2>
+<p>Multi Tenant Operator now supports custom metrics for templates, template instances and template group instances.</p>
+<p>Exposed metrics contain, number of resources deployed, number of resources failed, total number of resources deployed for template instances and template group instances. These metrics can be used to monitor the usage of templates and template instances in the cluster.</p>
+<p>Additionally, this allows us to expose other performance metrics listed <a href="https://book.kubebuilder.io/reference/metrics-reference.html">here</a>.</p>
+<p>More details on <a href="reference-guides/custom-metrics.html">Enabling Custom Metrics</a></p>
+<h2 id="graph-visualization-for-tenants">Graph Visualization for Tenants</h2>
+<p>Multi Tenant Operator now supports graph visualization for tenants on the MTO Console. Effortlessly associate tenants with their respective resources using the enhanced graph feature on the MTO Console. This dynamic graph illustrates the relationships between tenants and the resources they create, encompassing both MTO's proprietary resources and native Kubernetes/OpenShift elements.</p>
+<p>More details on <a href="reference-guides/graph-visualization.html">Graph Visualization</a></p>