Kublr Demo/Installer Release 1.14.0 (2019-11-01)

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.14.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 your clusters and benefit from all features, create a full-featured, permanent Kublr Platform in any cloud or on-premise.

Overview

This major release brings support for multiple-instance groups. It gives you an option to create groups of nodes with different OS, VM sizes and labels. Now you can better plan your infrastructure (for instance create one group of VMs for front-end and another one for a backend or a database) and then implement the infrastructure in just a one click using Kublr UI. In addition, the feature gives you the ability to change\modify\delete\add\clone an instance group after a cluster creation procedure. So infrastructure can follow for your requirement and changes. We added support of Kubernetes 1.14.8, fixed many known issues, and made several improvements. One of the small, but very useful, improvement is the web console with embedded kubectl and Helm. In version 1.14 you no longer needed to download a Kubernetes config file. Just click on the “Open Web Console” link and you will have access to Kubernetes API via kubectl in your browser.

Changelog

1. Kubernetes 1.14.8
2. User interface:
   • New consistent design
   • Support of multiple instance groups - now you can granularly manage your infrastructure
   • Web console with kubectl and Helm are available on UI
   • Bug fixes and improvements
   • Multi-line support on the Events page
3. VMware vSphere
   • Full support of multiple instance groups (add, delete, modify, clone)
   • Support cloud-init
   • Bug fixes and improvements
4. VMware VCloud Director
   • Support installation with self-signed certificates on vCloud Director API
   • Full support multiple instance groups (add, delete, modify, clone)
5. OS support:
   • Added support for SUSE Linux Enterprise Server
6. OnPrem:
   • Full support of multiple instance groups (add, delete, modify, clone)
   • Allow to specify IP/Port for external Ingress LB
   • Improved installation troubleshooting
   • Allow to create cluster/platform with only Master nodes
   • Allow to setup master nodes without “NoSchedule” taint
7. Centralized monitoring:
   • Rule that checks entire alerting pipeline is functional
8. Centralized logging:
   • Automated a creation of a default index pattern for Kibana
   • Multi tenant ELK with Kublr RBAC integration
9. Ingress controller
   • Updated to the latest version
   • Added support for Cert manager
10. GCP:
    • Added support for Google Cloud JSON Service Account File
    • Full support of multiple instance groups (add, delete, modify, clone)
11. Azure:
    • Full support of multiple instance groups (add, delete, modify, clone)
    • Allow to increase/decrease the number of nodes
12. AWS:
    • Full support of multiple instance groups (add, delete, modify, clone)

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

Kublr Control Plane

Kublr Platform Features