From olm
Lists installed operators in an OpenShift cluster, showing status, version, namespace, channel, and source in a formatted table.
How this command is triggered — by the user, by Claude, or both
Slash command
/olm:list [namespace] [--all-namespaces]The summary Claude sees in its command listing — used to decide when to auto-load this command
## Name olm:list ## Synopsis ## Description The `olm:list` command lists all installed operators in an OpenShift cluster, showing their status, version, and namespace. This command provides a quick overview of the operator landscape in your cluster. This command helps you: - Discover what operators are currently installed - Check operator versions and status at a glance - Identify operators that may need attention (failed, upgrading, etc.) - Get a comprehensive view across namespaces The command presents information in an easy-to-read table format with key details about each operator's...
olm:list
/olm:list [namespace] [--all-namespaces]
The olm:list command lists all installed operators in an OpenShift cluster, showing their status, version, and namespace. This command provides a quick overview of the operator landscape in your cluster.
This command helps you:
The command presents information in an easy-to-read table format with key details about each operator's ClusterServiceVersion (CSV) and Subscription.
The command performs the following steps:
Parse Arguments:
$1: Namespace (optional) - Target namespace to list operators from$2: Flag (optional):
--all-namespaces or -A: List operators across all namespaces (default behavior if no namespace specified)Prerequisites Check:
oc CLI is installed: which ococ whoamiDetermine Scope:
--all-namespaces flag or no arguments: List operators cluster-wideFetch Operator Data:
# For specific namespace
oc get csv -n {namespace} -o json
# For all namespaces
oc get csv --all-namespaces -o json
# For specific namespace
oc get subscription -n {namespace} -o json
# For all namespaces
oc get subscription --all-namespaces -o json
Parse and Correlate Data:
.metadata.name.metadata.namespace.spec.displayName.spec.version.status.phase (e.g., "Succeeded", "Installing", "Failed").metadata.creationTimestamp.spec.name.spec.channel.spec.source.status.installedCSV.status.currentCSVFormat Output as Table: Create a formatted table with columns:
NAMESPACE OPERATOR NAME VERSION STATUS CHANNEL SOURCE
cert-manager-operator cert-manager-operator v1.13.1 Succeeded stable-v1 redhat-operators
external-secrets-operator external-secrets-operator v0.10.5 Succeeded stable-v0.10 redhat-operators
openshift-pipelines openshift-pipelines-operator-rh v1.14.4 Succeeded latest redhat-operators
Add Summary Statistics:
Highlight Issues (if any):
⚠️ Operators requiring attention:
- namespace/operator-name: Failed (reason: ...)
- namespace/operator-name: Installing (waiting for...)
Provide Actionable Suggestions:
/olm:status {operator-name} {namespace} for details/olm:search {operator-name} to find available operators/olm:status {operator-name} to check upgrade optionsList all operators cluster-wide:
/olm:list
List operators in a specific namespace:
/olm:list cert-manager-operator
``
--all-namespaces or -A: Explicitly list all operators cluster-wideSucceeded: Operator is healthy and runningInstalling: Operator is being installedUpgrading: Operator is being upgradedFailed: Operator installation or operation failedReplacing: Old version being replacedDeleting: Operator is being removedoc auth can-i list csv --all-namespaces
oc auth can-i list subscription --all-namespaces
installedCSV differs from currentCSV, an upgrade may be in progress/olm:status <operator-name> [namespace] - Get detailed status of a specific operator/olm:install <operator-name> - Install a new operator/olm:search <query> - Search for available operators in catalogsnpx claudepluginhub bradmwilliams/ai-helpers --plugin olm/openshiftDiagnoses and resolves OpenShift cluster issues across SCC, Routes, GitOps, and upgrades. Also supports a debug mode for general troubleshooting.
/statusChecks Omni-managed Talos cluster phase and health, Kubernetes nodes, ArgoCD applications, External Secrets, and Longhorn storage, producing a formatted status report with issues.
/k8s-healthRuns comprehensive Kubernetes cluster health diagnostics with dynamic operator discovery, producing scored reports in summary, detailed, or JSON format.
/prereqsChecks current OS and installs missing prerequisites for Kubernetes operator development: kind, kubectl, kustomize, tilt, go, kubebuilder.
/listLists all installed and generated CLI-Anything tools with version, status, and path. Supports custom scan directories and JSON output.
/listLists all configured hookify rules in the project by scanning .claude/hookify.*.local.md files and displaying their frontmatter, status, and message previews in a table.