Glasskube — Next-Generation Package Manager for Kubernetes

Introduction

Glasskube reimagines how teams install and manage Kubernetes infrastructure packages. Instead of wrestling with Helm values, kustomize overlays, and version compatibility, Glasskube provides a curated package repository with dependency resolution, automatic updates, and a web-based dashboard — bringing the developer experience of apt or brew to Kubernetes.

What Glasskube Does

• Installs Kubernetes packages (cert-manager, ingress-nginx, Prometheus, etc.) with a single command
• Resolves package dependencies automatically, installing prerequisites in correct order
• Provides a web UI for browsing, installing, configuring, and updating packages visually
• Supports GitOps workflows by generating declarative package manifests for Flux or Argo CD
• Delivers automatic update notifications and one-click upgrades for installed packages

Architecture Overview

Glasskube runs as a Kubernetes operator that watches PackageInfo and Package custom resources. The CLI and web UI communicate with the operator via the Kubernetes API. A central public package repository hosts package manifests defining Helm charts, dependencies, and configuration schemas. The operator reconciles desired state, handling installs, upgrades, and dependency resolution.

Self-Hosting & Configuration

• Bootstrap with glasskube bootstrap which installs the operator and CRDs into your cluster
• Access the web UI via glasskube serve which proxies through the Kubernetes API
• Configure packages through the UI or by editing Package custom resources directly
• Create private package repositories for internal packages using the repository specification
• Integrate with GitOps by exporting package manifests and committing them to your repo

Key Features

• Dependency resolution prevents broken installations from missing prerequisites
• Web UI provides a visual catalog with configuration forms generated from package schemas
• Package repository model enables versioned, tested combinations of infrastructure tools
• GitOps-native design produces declarative CRDs compatible with Flux and Argo CD
• Automatic update detection with controlled rollout policies per package

Comparison with Similar Tools

• Helm — powerful but requires manual dependency management and values authoring; Glasskube automates this
• Kustomize — overlay-based customization; no dependency resolution or update management
• Operator Lifecycle Manager (OLM) — operator-focused with complex APIs; Glasskube covers all package types simply
• Artifact Hub — discovery portal only; Glasskube is a full package manager with install and lifecycle
• Carvel (kapp-controller) — flexible but low-level; Glasskube offers higher-level UX with a GUI

FAQ

Q: Does Glasskube replace Helm? A: Not entirely. Glasskube uses Helm under the hood for some packages but adds dependency management, a UI, and automatic updates on top.

Q: Can I create custom packages? A: Yes. Define a PackageManifest with your Helm chart reference, dependencies, and configuration schema, then host it in a private repository.

Q: Is the web UI required? A: No. The CLI provides full functionality. The web UI is optional for teams preferring visual management.

Q: How does GitOps integration work? A: Glasskube generates Package CRDs that you commit to Git. Flux or Argo CD syncs them, and the Glasskube operator reconciles the actual state.

Sources

• https://github.com/glasskube/glasskube
• https://glasskube.dev