feat(docs): add Catalog playbook

charts/greenhouse/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 name: greenhouse
 description: A Helm chart for deploying greenhouse
 type: application
-version: 0.20.2
+version: 0.20.3‚
 appVersion: "v0.14.0"
 
 dependencies:
@@ -18,7 +18,7 @@ dependencies:
     repository: "file://../cors-proxy"
     version: 0.10.0
   - name: manager
-    version: 0.13.1
+    version: 0.13.2
     repository: "file://../manager"
   - condition: dashboard.enabled
     name: dashboard

charts/manager/Chart.yaml

@@ -16,7 +16,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.13.1
+version: 0.13.2
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

charts/manager/alerts/catalog.alerts

@@ -9,6 +9,7 @@ groups:
       service: '{{ $labels.catalog }}'
       organization: '{{ $labels.organization }}'
       support_group: '{{ $labels.owned_by }}'
+      playbook: https://cloudoperators.github.io/greenhouse/docs/operations/playbooks/catalog/catalog-not-ready/
     annotations:
       summary: "Catalog not ready for over 15 minutes"
       description: "The catalog {{ $labels.catalog }} in organization {{ $labels.organization }} has not been ready for more than 15 minutes. Reason: {{ $labels.reason }}."

docs/operations/playbooks/catalog/catalog-not-ready.md

@@ -0,0 +1,69 @@
+---
+title: "CatalogNotReady"
+linkTitle: "CatalogNotReady"
+landingSectionIndex: false
+weight: 1
+description: >
+  Playbook for the GreenhouseCatalogNotReady Alert
+---
+
+## Alert Description
+
+This alert fires when a Greenhouse catalog has not been ready for more than 15 minutes.
+
+## What does this alert mean?
+
+A Catalog in Greenhouse holds the available PluginDefinitions and acts as the source of truth for which plugins can be deployed within an organization. When a catalog is not ready, it indicates that the catalog source cannot be synchronized or that the catalog controller is unable to process it correctly.
+
+This could be due to:
+
+- The catalog source (e.g. Helm repository, OCI registry) being unavailable or unreachable
+- Invalid or expired credentials for accessing the catalog source
+- A misconfigured catalog resource (e.g. wrong URL, invalid reference)
+- The catalog controller encountering errors during reconciliation
+- Network connectivity issues between the Greenhouse operator and the catalog source
+
+## Diagnosis
+
+### Get the Catalog Resource
+
+Retrieve the catalog resource to view its current status:
+
+```bash
+kubectl get catalog <catalog-name> -n <namespace> -o yaml
+```
+
+Or use kubectl describe for a more readable output:
+
+```bash
+kubectl describe catalog <catalog-name> -n <namespace>
+```
+
+### Check the Status Conditions
+
+Look at the `status.statusConditions` section in the catalog resource. Pay special attention to:
+
+- **Ready**: The main indicator of catalog health
+- **SourceSynced**: Indicates whether the catalog source was successfully synchronized
+
+### Check Controller Logs
+
+Review the Greenhouse controller logs for more detailed error messages:
+
+```bash
+kubectl logs -n greenhouse -l app=greenhouse --tail=100 | grep -i catalog # requires permissions on the greenhouse namespace
+```
+
+Or access your logs sink for Greenhouse logs.
+
+### List All Catalogs
+
+Check if multiple catalogs are affected:
+
+```bash
+kubectl get catalog -A
+```
+
+## Additional Resources
+
+- [Greenhouse Catalog Documentation](../../../../reference/components/catalog)