Kublr Demo/Installer Release 1.9.6 (2018-07-05)

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.

Overview

This update brings Kubernetes 1.9.9 and ehances the performance of GlusterFS installation

Changelog

1. Upgrade Kubernetes to 1.9.9
2. Do not use removed repo for GlusterFS

Known Issues

Performance enehancements for knwon issues will be included in next major release of Kublr

1. During cluster update adding new features works only in non-Persistence mode for AWS. (Fixed in Kublr 1.10)

2. Cluster is not updated in Draft state if AWS region was changed in cluster specification. (Fixed in Kublr 1.10)

3. In some cases user may experience errors when deleting nodes from on-premises cluster in Control Plane.

4. Restore: Links of features are not present on the cluster’s Overview page after restoration

5. Restore: overallClusterStatus not initialized for the restored cluster

6. (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.

Components versions

Kubernetes

Kublr Control Plane

Kublr Platform Features