Kublr Release 1.16.0 (2020-01-28)

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

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 cluster and platform itself. 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 must create a full-featured Kublr Platform in a cloud or on-premise.

Overview

This major release brings one of the most valuable features for Enterprise Container Platform based on Kubernetes - in-place rolling upgrade of Kubernetes versions. It works in all supported clouds, on-premises and VMware environments. Upgrade of a cluster requires zero down time. It’s fully automatic, supports different strategies and includes a rollback option in case of a failure. Please refer to the guide for more details in-place rolling upgrade. Now the Kublr Platform supports multiple Kubernetes versions. Please read this important information before moving to 1.16 from previous Kubernetes versions Urgent Upgrade Notes. Please contact support-team@kublr.com for upgrade guide from version 1.15.x to 1.16.0.

Changelog

1. Kubernetes 1.16.4, 1.16.6
2. In place upgrade for Kubernetes and components for all supported types of infrastructure
3. User interface:
   • Kublr provides more telemetry information through the UI
4. VMware vSphere
   • It is possible to use static IP with cloud init
5. Centralized monitoring:
   • Alert manager 0.19
6. GCP:
   • Support for creating clusters in existing VPC
7. Core:
   • IPVS support for kube-proxy (technical preview)
   • Kublr agent extensions
   • Coredns 1.6.2

Known Issues

1. nginx-ingress’s Grafana dashboard does not show all statistics if host value not specified in ingress rule

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