Kublr Release 1.20.2 (2021-03-25)

Kublr Quick Start

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

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.


This update contains critical bug fixes, Azure autoscaling support, Kubernetes v1.20.4 and VictoriaMetrics technical preview.

Important Changes and fixes

  • Hot/Warm/Cold nodes support in Elasticsearch 7.10.2
  • Azure cluster autoscaling support
  • UI multilanguage support
  • Terraform controller upgraded to v0.14.4
  • Monitoring components upgraded to the latest version
  • Azure NTP time synchronization issue resolved

Improvements and stability fixes

  • Allow to configure number of replicas in elasticsearch template
  • Override docker repositories in the cluster specification
  • Ability to parse json in docker logs and use structured logs in Elasticsearch and Kibana
  • Default index-pattern for self-hosted logging
  • vCloud API 32.0 support
  • Logs collection from /var/log/kublr/cache-info.log
  • UI: Azure: Allow user to select Availability Set or Scale Set
  • UI fixes and improvements

Technical preview

Kuberntes v1.20.4


Kuberntes 1.20.4 can be used for Kublr cluster installation. Add kublr agent 1.20.4-1 into agent list on setting page.

Important notice: This is a technical preview not recommended for use in production environments

VictoriaMetrics v1.49


VictoriaMetrics can be enabled in Kublr feature Monitoring for collecting metrics along with Prometheus.

Important notice: This is a technical preview not recommended for use in production environments

To enable this feature, modify spec.features.monitoring section in the cluster specification:

          enabled: true

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.17 (Deprecated in 1.21.0)

v1.16 (End of support in 1.21.0)

Components versions


ComponentVersionKublr AgentNote
Kubernetes1.191.19.7-29default v1.19.7 in 1.21.0 of support in 1.21.0 preview

Kublr Control Plane

Kublr Control Plane1.20.2-95
Kublr Operator1.20.2-40

Kublr Platform Features

Kublr System1.20.2-37
LocalPath Provisioner (helm chart version)0.0.12-6
nginx ingress controller (helm chart version)1.36.2
Centralized Logging1.20.2-58
Centralized Monitoring1.20.2-42
Kube State Metrics2.4.1
Kublr KubeDB1.20.2-36
kubedb (helm chart version)v0.14.0-alpha.2

Known issues and limitations

  1. Azure cluster autoscaling is only supported with Kublr agents 1.18.15-7 or 1.19.7-29 and above.

  2. For migration from Kubernetes versions below 1.19:

    kubectl delete cm -n kube-system coredns
  3. If customized values are used for the centralized logging package, please refer to Logging upgrade notice for custom defined values.

  4. Managed cluster migration from previous major Kublr version (<1.18.0) have limitations related to updgrading Kublr components to Kublr 1.20. Please refer to Kublr 1.18 migration document for more details.

  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.