Kublr Release 1.21.1 (2021-06-25)

Kublr Quick Start

sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 kublr/kublr:1.21.1

Follow the full instructions in Quick start for Kublr Demo/Installer.

The Kublr Demo/Installer is a lightweight, dockerized, limited-functionality Kublr Platform which can be used to:

  • Test setup and management of a standalone Kubernetes cluster
  • Setup a full-featured Kublr Platform

The Kublr Demo/Installer stores all of the data about the created clusters inside the Docker container. If you delete the Docker container you will lose all data about the created clusters and the Kublr platforms. However, you will not lose the clusters and the platforms themselves.

We recommend using the Kublr Demo/Installer to verify if a Kubernetes cluster can be created in your environment and to experiment with it. To manage a real cluster and experience all features, you can create a full-featured Kublr Platform in a cloud or on-premise.


The Kublr 1.21.1 patch release contains a critical Azure bug fix with deployment update logic. If you using Kublr in the Azure cloud, we recommend using Kublr 1.21.1 or later.

Important Fixes

  • Azure deployments update fixes
    • Improve resource managent
    • Cluster controller tries to remove LB created by Kubernets cloud controller
  • Kublr operator crashes if Tiller is missing or manually upgraded in a managed cluster
  • Minor UI improvements

AirGap Artifacts list

Additionally, you need to download the BASH scripts from https://repo.kublr.com

You also need to download Helm package archives and Docker images:

Supported Kubernetes versions

v1.21 (technical preview)



v1.18 (Deprecated in 1.22.0)

v1.17 (Deprecated in 1.21.0, End of support in 1.22.0)

Components versions


ComponentVersionKublr AgentNotes
Kubernetes1.201.20.7-13default v1.20.7 in 1.22.0 of support in 1.22.0 preview

Kublr Control Plane

Kublr Control Plane1.21.1-31
Kublr Operator1.21.1-19

Kublr Platform Features

Kublr System1.21.1-17
LocalPath Provisioner (helm chart version)0.0.12-6
nginx ingress controller (helm chart version)1.36.2
Centralized Logging1.21.1-23
SearchGuard Kibana plugin49.0.0
SearchGuard Admin7.10.2-49.0.0
Centralized Monitoring1.21.1-18
Kube State Metrics2.4.1
Victoria Metrics
Kublr KubeDB1.21.1-18
kubedb (helm chart version)v0.14.0-alpha.2

Known issues and limitations

  1. Canal CNI (default) does not work on AWS images with nm-cloud-config. At the moment it only affects RHEL 8 image.

    As a workaround, remove or disable nm-cloud-config or use a different CNI plugin (e.g. CNI Calico).

  2. SELinux is not supported for ContainerD CRI

  3. Containerd CRI is only supported for Kublr Agents 1.19, 1.20, and 1.21

  4. vCloud Director implementation does not support named disks for persistent volumes by default. vCloud Director CSI driver needs to be installed in the cluster.

  5. Beginning November 2, 2020, progressive enforcement of rate limits for anonymous and authenticated Docker Hub usage came into effect. Learn more about the change from the article Understanding Docker Hub Rate Limiting. Kublr clusters use some images hosted on Docker Hub / docker.io (e.g. kubernetesui/dashboard:v2.0.4). As a result some cluster operations may fail due to Docker Hub rate limiting. You can avoid possible issues using one of the following solutions:

    1. If you have a paid Docker Hub account, create a docker.io secret in Kublr Control Plane and add this docker registry to the cluster specification using advanced section in Kublr cluster creation UI.
    2. Override docker.io registry with cr.kublr.com, all imagess needed for cluster installation are mirrored in this repo. Learn more about docker registry override in the Kublr documentation cluster specification reference.