Upgrading

CLI

To upgrade the Glasskube CLI, simply install the latest version via your preferred package manager.

macOS

To upgrade Glasskube on macOS, use the following command:

brew upgrade glasskube

Linux

You can upgrade Glasskube by reinstalling the latest package using one of the package managers below.

RPM-based installation (RedHat/CentOS/Fedora)

dnf install https://releases.dl.glasskube.dev/glasskube_v0.10.1_amd64.rpm

DEB-based installation (Ubuntu/Debian)

curl -LO https://releases.dl.glasskube.dev/glasskube_v0.10.1_amd64.deb
sudo dpkg -i glasskube_v0.10.1_amd64.deb

APK-based installation (Alpine)

curl -LO https://releases.dl.glasskube.dev/glasskube_v0.10.1_amd64.apk
apk add glasskube.apk

If you are using a distribution that does not use one of the package managers above, or require a 32-bit binary, check out additional download options attached to our latest release.

Windows

Download the windows archive from our latest Release and unpack it using Windows Explorer and replace the existing executable with the new one.

NixOS/Nixpkgs

You can either use the package temporarily in a nix-shell:

nix-shell -p glasskube

Or install it globally by adding pkgs.glasskube to your environment.systemPackages.

After upgrading Glasskube on your local machine, make sure to install the necessary components in your Kubernetes cluster by running glasskube bootstrap. For more information, check out our bootstrap guide.

Cluster Components

To upgrade the Glasskube cluster components, run glasskube boostrap using the same configuration that was used for the initial installation.

Breaking Changes

Upgrading to v0.10.0

While our goal is to prevent breaking changes if possible, this release includes several major changes in the Glasskube system:

1. The scope of the Package CRD has been changed from Cluster to Namespaced.
2. Flux components have been updated to the latest API version.
3. The naming strategy for PackageInfos and HelmReleases was changed.
4. The ownership model was overhauled in order to not rely on native OwnerReferences, since they have become limiting to our usecase.

Unfortunately, this means that a migration from prior releases is not supported. Please remove Glasskube from your cluster using glasskube purge, then install the new version.

warning

This will remove all installed packages.

If you have any questions or concerns, please reach out. We are happy to assist.