PluginNotReady

Playbook for the PluginNotReady Alert

Alert Description

This alert fires when a Plugin has not been ready for more than 15 minutes.

What does this alert mean?

A Plugin in Greenhouse represents an application or service deployed to a target cluster via Helm. When a Plugin is not ready, it indicates that the deployment or the workload resources are not functioning correctly.

This could be due to:

Helm chart deployment failures
Missing or invalid PluginDefinition
Cluster access issues
Invalid plugin option values
Workload resources not becoming ready (pods failing, etc.)
Dependencies not being met (via waitFor)

Diagnosis

Get the Plugin Resource

Retrieve the plugin resource to view its current status:

kubectl get plugin <plugin-name> -n <namespace> -o yaml

Or use kubectl describe for a more readable output:

kubectl describe plugin <plugin-name> -n <namespace>

Check the Status Conditions

Look at the status.statusConditions section in the plugin resource. Pay special attention to:

Ready: The main indicator of plugin health
ClusterAccessReady: Indicates if Greenhouse can access the target cluster. If false check target Cluster status.
HelmReconcileFailed: Shows if Helm reconciliation failed
HelmDriftDetected: Indicates drift between desired and actual state
HelmChartTestSucceeded: Shows if Helm chart tests passed
WaitingForDependencies: Indicates if waiting for other plugins
RetriesExhausted: Shows if all retry attempts have been exhausted

Check Underlying Flux Resources

Since Greenhouse uses Flux as the default deployment mechanism, you can inspect the Flux HelmRelease resource belonging to a Plugin:

# Get the HelmRelease in the organization namespace
kubectl get helmrelease <plugin-name> -n <namespace> -o yaml

# Describe the HelmRelease for detailed status
kubectl describe helmrelease <plugin-name> -n <namespace>