Addons

Addons are cluster extensions — cert-manager, ingress-nginx, Karpenter, OpenCost, Kyverno, Grafana, and anything else you’d normally install by hand — that Skyhook installs, configures, and keeps in sync via GitOps. Instead of running helm install per cluster and tracking values files in Git by yourself, you pick addons from a catalog, edit shared base values (with per-cluster overrides), and Skyhook generates a PR against your GitOps repository. ArgoCD then rolls the change out to every selected cluster.

​

Prerequisites

• GitOps configured — Skyhook needs to know where to write addon manifests. See GitOps overview.
• At least one connected cluster — addons are per-cluster, so you need somewhere to install them. See Connecting Clusters.
• ArgoCD running on each target cluster — ArgoCD is what actually applies the manifests after Skyhook writes them.

​

The Addons page

Addons in the sidebar opens the main catalog view. It has three sections stacked from top to bottom.

​

Fleet Status

A clusters × addons matrix above everything else. Each cell shows the sync and health status of that addon on that cluster, with a tooltip for any errors and a clickable link into the addon or cluster.

• Green check — installed and in sync
• Amber warning — installed but drifted or out of sync
• Red error — installed but unhealthy (see tooltip for the ArgoCD error)
• Empty cell — addon not installed on that cluster

A summary above the matrix shows the total count of addons and clusters, plus how many are currently out of sync. Each cluster row has a three-dot menu with an Import addons entry point — useful when a new cluster needs to match the configuration of another.

​

Installed

“Addons managed by Skyhook through GitOps.” Each card shows:

• Addon logo + name and current chart version
• One-line description
• Cluster pills for the first few installed-on clusters and a +N more badge
• Custom Helm charts (installed via the search box below) appear here too, with a generic package icon if no logo is available

Clicking a card opens the addon’s Configure page.

​

Install any Helm chart + Suggested addons

A search box wired to ArtifactHub lets you install any public Helm chart — not just curated ones. Below the search, the Suggested addons catalog lists 34+ popular tools organized by category:

• Security — Kyverno, Falco, Polaris, HashiCorp Vault, Trivy Operator
• Observability — Grafana, Tempo, Loki, Prometheus Stack, Jaeger, OpenTelemetry Collector, Alloy
• Networking — Istio, Cilium, Traefik, Envoy Gateway, External DNS
• Autoscaling & Infra — Karpenter, KEDA, VPA, Metrics Server, Descheduler, Argo Rollouts / Workflows / Events
• Services — CloudNativePG, MariaDB Operator, MinIO Operator, Strimzi Kafka, RabbitMQ Operator, Redis Operator, Harbor

​

Addon detail page

Clicking any addon (installed or catalog) opens the detail page. The top shows the logo, version dropdown, description, and an Uninstall button. Below that, a flat tab row contains:

• Status — per-cluster installation status table
• One tab per component — e.g. cert-manager (Helm), cert-manager-crds (Kustomize), letsencrypt-issuer (Kustomize) — each addon declares what pieces it needs. Multi-component addons like cert-manager or OpenCost install several things at once.
• Secrets — manage Kubernetes secrets consumed by this addon

​

Status tab

The status tab lists every cluster in your organization and whether the addon is configured on each one. Not-installed clusters show an Add button. Click Edit configuration at the top of the table to jump to the component editor.

​

Configuring an addon

Each component tab opens an editor with three stacked sections:

​

Base Settings (curated fields)

The top panel exposes commonly-edited values as native form controls — sliders, toggles, text inputs — rather than raw YAML. Edits here are applied to all clusters unless overridden. Supported addons include cert-manager, KEDA, and others; curated fields are additive — anything not exposed is still editable in the YAML panel below. Curated-field edits preserve comments and formatting in the underlying YAML.

​

Clusters sidebar

A unified list of every cluster in your org. Configured clusters appear first with their values, an enable/disable toggle, and a remove button. Clusters not yet configured appear below with a + button to add them. Adding a cluster enables it automatically. The counter (e.g. 3 / 3 enabled) shows how many of the configured clusters are currently enabled.

​

YAML editor

The right pane is a YAML editor showing either:

• base/values.yaml — the shared base applied to all clusters, or
• <cluster>-values.yaml — the per-cluster override when a specific cluster is selected in the sidebar

Three toggle buttons sit above the editor:

• Diff — shows what’s changed since the version you started editing
• Preview — renders the Helm chart with your current values and shows the resulting Kubernetes manifests, so you can catch template errors before creating the pull request
• vs Base — when viewing a per-cluster file, shows the effective merged values (base + overrides) for that specific cluster

A Docs tab at the top renders the Helm chart’s README alongside the editor, useful when you need to look up what a value does without leaving the page.

​

Saving changes

Click Create PR at the bottom to write your changes as a pull request against the GitOps repository. The button label reminds you: Changes are applied to your cluster after the PR is merged. Once the PR merges, ArgoCD syncs the new values to the target clusters.

​

Importing addons from existing clusters

If you already have addons running on a cluster — either in GitOps or installed by hand — you can import them into Skyhook instead of re-configuring from scratch.

​

From GitOps Clusters

Multi-step wizard (Addons > Import > From GitOps Clusters) for when you have a working reference cluster already in GitOps:

​

From Any Cluster (Helm snapshot)

For clusters not yet in GitOps — a brownfield cluster with existing helm install releases — Skyhook provides a terminal command that captures a snapshot of the current Helm releases and uploads it. The snapshot is then used as the import source for the same wizard flow. This is useful for onboarding an existing environment without manually reverse-engineering every values file.

​

Secrets tab

The Secrets tab on an addon detail page manages Kubernetes secrets the addon depends on, per cluster.

• Namespace is auto-detected from the addon’s target namespace (editable if you need to override).
• Each secret has a name, namespace, and a list of key/value pairs.
• Saves go through the same Create PR flow as config changes — Skyhook batches secret updates alongside values edits.

​

Missing secret detection

As you edit a component, Skyhook scans the rendered manifests in the background for Kubernetes secret references. Any secret the chart expects but isn’t configured yet shows up as a warning on the Secrets tab with a Create button that pre-fills the name and keys for you. If the background scan temporarily fails, the previously-detected results are kept so transient errors don’t wipe out your list.

​

ArgoCD sync status

Sync and health status come from ArgoCD itself and are surfaced in multiple places:

• Fleet Status matrix on the main addons page — at-a-glance cluster × addon coverage
• Installed cards — sync status badge
• Cluster detail page — a Cluster Addons Health card shows installed addons with sync status, chart version, and namespace, plus a quick link to Copy Addons from another cluster
• Addon Configuration tab sidebar — per-cluster err badges with expandable error strips for clusters whose background preview failed

Clicking any status cell jumps straight to the relevant addon or cluster page.

​

Troubleshooting