Kublr Demo/Installer Release 1.11.1 (2019-01-23)

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.

Quick Start

Please use your KUBLR_LICENSE key and run this command. If you have already registered on kublr.com you will find KUBLR_LICENSE in your email. Just substitute your key for the KublrLicense. You can also register again on kublr.com and receive a new Kublr license by email. For additional instructions, click here Quick start for Kublr Demo/Installer

sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 -e KUBLR_LICENSE=<KublrLicense> kublr/kublr:1.11.1

Kublr Demo/Installer is a lightweight tool for running a limited-functionality Kublr Platform inside Docker container and installing full Kublr Control Plane. It can be used to:

  • Test setup and management of a standalone Kubernetes cluster;
  • Setup a fully featured Kublr Platform.

Kublr Demo/Installer stores all 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 Kublr platforms. You will not lose the cluster and platform itself. The Kublr team recommends to using Kublr Demo/Installer to check that a Kubernetes cluster can be created in your environment and to experiment. Then we recommend creating a fully featured and durable Kublr Platform, in any cloud or on-premise, with the full power Kublr platform to manage your Kubernetes clusters.

Overview

This update covers Kubernetes 1.11.7 and other enhancements.

Changelog

  1. Kubernetes 1.11.7.
  2. Bug fixes and improvements

Known issues and limitations

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

ComponentVersion
Kubernetes1.11.7
etcd3.2.18
Kubernetes Dashboard1.8.3

Kublr Control Plane

ComponentVersion
Kublr Control Plane1.11.1

Kublr Platform Features

ComponentVersion
Ingress0.3.5
nginx ingress controller (helm chart version)0.20.3
kube-lego (helm chart version)0.4.2
Centralized Logging1.11.1
ElasticSearch6.4.0
Kibana6.4.0
ElasticSearch Exporter1.0.1
Rabbitmq3.7.3
Curator5.5.1
Logstash6.4.0
Fluentd2.3.1
Centralized Monitoring1.11.1
Prometheus2.3.2
Kube State Metrics1.3.1
AlertManager0.15.2
Grafana5.2.2
System0.3.4