Glasskube — Next-Generation Package Manager for Kubernetes

What it is

Glasskube is a modern Kubernetes package manager that simplifies installing and managing cluster add-ons. Unlike Helm, which requires manually tracking chart versions and dependencies, Glasskube packages are dependency-aware, GitOps-ready, and receive automatic updates. It includes both a CLI and a web-based GUI for package management.

Glasskube is for Kubernetes operators and platform engineers who want a simpler way to manage cluster add-ons like cert-manager, ingress-nginx, and monitoring stacks.

The project is actively maintained with regular releases and a growing user community. Documentation covers common use cases, and the open-source nature means you can inspect the source code, contribute fixes, and adapt the tool to your specific requirements.

How it saves time or tokens

Helm charts require version pinning, values file management, and manual upgrade tracking. When one chart depends on another, you manage the dependency graph yourself. Glasskube handles all of this: dependencies resolve automatically, updates are applied safely, and the GUI provides a visual overview of installed packages and their status.

How to use

1. Install the Glasskube CLI.
2. Bootstrap Glasskube in your Kubernetes cluster.
3. Install packages via CLI or the built-in GUI.

Example

# Install Glasskube CLI
brew install glasskube/tap/glasskube

# Bootstrap in your cluster
glasskube bootstrap

# Install a package
glasskube install cert-manager

# Open the GUI
glasskube serve
# Open http://localhost:8580

# List installed packages
glasskube list

# Update all packages
glasskube update --all

Related on TokRepo

• AI Tools for DevOps -- Kubernetes management and deployment tools
• AI Tools for Self-Hosted -- Self-hosted infrastructure tooling

Common pitfalls

• Glasskube runs a controller in your cluster. The bootstrap step installs CRDs and a package operator. Ensure you have cluster-admin permissions before running bootstrap.
• Not all Helm charts are available as Glasskube packages. The package catalog is growing but smaller than the Helm ecosystem. Check the catalog before committing to Glasskube for a specific add-on.
• Automatic updates can be disruptive for production clusters. Configure update policies to require manual approval for major version bumps.

Before adopting this tool, evaluate whether it fits your team's existing workflow. Read the official documentation thoroughly, and start with a small proof-of-concept rather than a full migration. Community forums, GitHub issues, and Stack Overflow are valuable resources when you encounter edge cases not covered in the documentation.