Kublr Release 1.19.2 (2020-10-08)

This release has a known critical issue, use Kublr 1.21.2 or later instead

Due to docker image gcr.io/kubernetes-helm/tiller:v2.14.3 discontinued in the Google Image repository in August 2021, ( related issue: “Make Tiller Image Available on Docker Hub” ), Kublr may fail to complete cluster create and update.

The cluster hangs in “Creating” or “Updating” state indefinitely or for a very long time, or goes to “Error” state, in all cases with Tiller pod unhealthy due to Tiller image not available.

All versions of Kublr before 1.21.2 (including this one), and Kublr Agent versions earlier than the ones included in Kublr 1.21.2 are affected.

The issue and available solutions are described in the troubleshooting guide on Kublr support portal.

Migration to the latest Kublr Agents and Kublr Control Plane versions or at least Kublr 1.21.2 is recommended.

Kublr Quick Start

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

Overview

This update contains critical bug fix in cluster autoscaler components and GPU support fix in Kuberntes v1.18.9

Important Changes

  • Cluster Autoscaler upgraded to last version
  • Fixed DevicePlugins for GPU instances support

AirGap Artifacts list

Refer to AirGap deployment instructions for details on Kublr installation.

KCP image and binary archive load scripts:

KCP image and binary archives:

Supported Kubernetes versions

v1.18

v1.17

v1.16 (Deprecated in 1.20.0)

v1.15 (End of support in 1.20.0)

Components versions

Kubernetes

ComponentVersionKublr AgentNote
Kubernetes1.181.18.9-11default v1.18.9
1.171.17.12-12
1.161.16.13-6Deprecated in 1.20.0
1.15.(11, 12)1.15.12-8End of support in 1.20.0

Kublr Control Plane

ComponentVersion
Kublr Control Plane1.19.2-2
Kublr Operator1.19.2-3

Kublr Platform Features

ComponentVersion
Kublr System1.19.2-3
LocalPath Provisioner (helm chart version)0.0.12-6
Ingress1.19.2-3
nginx ingress controller (helm chart version)1.36.2
cert-manager0.14.2
Centralized Logging1.19.2-3
ElasticSearch6.8.4
Kibana6.8.4
SearchGuard plugin25.5.0
SearchGuard Kibana plugin25.5.0
SearchGuard Admin6.8.4-25.5.0
RabbitMQ3.8.3
Curator5.8.1
Logstash6.8.4
Fluentd2.7.1
Centralized Monitoring1.19.2-3
Prometheus2.13.0
Kube State Metrics2.4.1
AlertManager0.19.0
Grafana6.5.1
Kublr KubeDB1.19.2-3
kubedb (helm chart version)v0.14.0-alpha.2

Known issues and limitations

  1. Managed cluster migration from previos major Kublr version (<1.18.0) have limitations related to updgrading Kublr components to Kublr 1.18. Please refer to Kublr 1.18 migration document for more detail.

  2. In some cases, cluster upgrade process crashes on Azure due to underlying VM issues. The issue usually resolves after re-running the update procedure in ~30 minutes.

  3. (Critical) Due to docker image gcr.io/kubernetes-helm/tiller:v2.14.3 discontinued in the Google Image repository in August 2021, ( related issue: “Make Tiller Image Available on Docker Hub” ), Kublr may fail to complete cluster create and update.

    The cluster hangs in “Creating” or “Updating” state indefinitely or for a very long time, or goes to “Error” state, in all cases with Tiller pod unhealthy due to Tiller image not available.

    All versions of Kublr before 1.21.2 (including this one), and Kublr Agent versions earlier than the ones included in Kublr 1.21.2 are affected.

    The issue and available solutions are described in the troubleshooting guide on Kublr support portal.

    Migration to the latest Kublr Agents and Kublr Control Plane versions or at least Kublr 1.21.2 is recommended.