Kublr Release 1.20.1 (2021-02-12)

Kublr Quick Start

sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 kublr/kublr:1.20.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.


Your upgrade to Kublr 1.20.1 must include the procedures described below.

Simultaneous Update of Kublr Control Plane

When upgrading a Kublr Control Plane, first upgrade the following fieature versions in the KCP cluster specification simulatzniously and wait for the KCP to update and recover:

  • kublrOperator: 1.20.1-1
  • ControlPlane: 1.20.1-1
  • System: 1.20.1-1
  • Ingress: 1.20.1-1
  • KubeDB: 1.20.1-1

After that you can update log collection and monitoring feature versions via UI.

Logging migration to ELK 7.10.2

  1. Before updating log collection feature, go to Kibana Management menu and delete kublr*, kublr_default* index patterns

  2. After the new cluster specification update is applied and the helm charts installed or upgraded, run the following command from the logging-controller pod:

    /sgadmin/tools/sgadmin.sh --delete-config-index -icl -nhnv \
        -cacert /sg-certificates/root-ca.pem \
        -cert /sg-certificates/sgadmin.pem \
        -key /sg-certificates/sgadmin.key \
  3. Trigger kublr-logging-sg-init CronJob in kubernetes dashboard or use the following commnand:

    kubectl create job kublr-logging-sg-init --from=cronjob/kublr-logging-sg-init -n kublr


This update contains critical bug fixes for the centralized logging and upgrades Elasticsearch to 7.10.2

Important Changes

  • Elasticsearch 7.10.2 with SearchGuard plugin
  • Non-OSS Elasticsearch version support issue fixed
  • RabbitMQ lost data after restarting fixed
  • Azure cluster monitoring “Failed to refresh the Token” error

Improvements and stability

  • Deprecated Letsncrypt API endpoints (v1) removed from UI
  • Azure: images may be specified by resourceId property
  • UI fixes and 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.17 (Deprecated in 1.21.0)

v1.16 (End of support in 1.21.0)

Components versions


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

Kublr Control Plane

Kublr Control Plane1.20.1-1
Kublr Operator1.20.1-1

Kublr Platform Features

Kublr System1.20.0-1
LocalPath Provisioner (helm chart version)0.0.12-6
nginx ingress controller (helm chart version)1.36.2
Centralized Logging1.20.0-1
SearchGuard Kibana plugin45.0.0
SearchGuard Admin7.9.0-45.0.0
Centralized Monitoring1.20.0-1
Kube State Metrics2.4.1
Kublr KubeDB1.20.0-1
kubedb (helm chart version)v0.14.0-alpha.2

Known issues and limitations

  1. For migration from Kubernetes versions below 1.19:

    kubectl delete cm -n kube-system coredns
  2. Index Pattern in self-hosted Kibana need to be created manually. Please refer to Kubana documentation for more information.

  3. 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 detail.

  4. 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.