Kublr Release 1.18.1 (2020-07-07)

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

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 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 update contains iterative patch and minor improvements, RHEL8 support (technical preview), and Kublr cluster BackUps for AWS (technical preview). We also added Kubernetes 1.16.10 and 1.17.7 with CVE fixes.

Changelog

Kubernetes 1.17.7, 1.16.10 support.

Improvements and stability

• Cluster pre-flight checks, validation, and recommendations added
• Default master disk size increased to 25Gb for vSphere installation
• Agent versions parameter validation improved in the settings screen

Bug fixes

• Error reporting is improved in Kublr API; proxied kubectl requests error reporting fixed
• cni-calico network provider pod readiness check
• User must be logged in to Kublr when using kubectl as simple user
• UI: Impossible to increase boot Disk size for Master node in vSphere
• Backup controller fixed for work on AWS
• Kubeconfig file missing while cluster ins in the updating state
• AWS Spotist elastigroups userData is generated incorrectly

Technical preview

RHEL/CentOS 8 supported only in agent versions: 1.17.3, 1.17.4, 1.17.7

• for the baremetal installation, make sure that Selinux is disabled on the nodes:

  sudo setenforce permissive
  

• on cloud installations, disabling Selinux is not necessary
• CentOS/RHeL 8.0 is not supported, 8.1 or newer is required (https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/4/html-single/installation_guide/index#operating-system-requirements-for-red-hat-ceph-storage-install)
• don’t use components (both pods and node processes) that use iptables in legacy mode. This will disrupt Kubernetes auto-detection and might render the cluster inoperable (https://github.com/projectcalico/calico/issues/3709)
• Kublr by default installs two components that depend on iptables-legacy: NodeLocalDns and CNI provider Flannel (as part of cni-canal). For CentOS/RHeL 8 support these components must be disabled or not used.
• Therefore, only calico and weave CNI providers are supported (On Azure only weave is supported)
• To disable NodeLocalDns and select CNI provider, add the following lines to the custom cluster specification:

  spec:
  ...
    network:
      ...
      provider: cni-calico
      enableLocalDns: false
  

Kublr BackUp controller

• Disabled by default from UI, you can enable this feature on settings page
• Backup/Restore available only for AWS

AirGap Artifacts list

Additionally, you need to download the BASH scripts from https://repo.kublr.com

• https://repo.kublr.com/repository/arc/controlplane/1.18.1/kublr-load-helm-1.18.1.sh
• https://repo.kublr.com/repository/arc/controlplane/1.18.1/kublr-controlplane-load-images-1.18.1.sh

You also need to download Helm package archives and Docker images:

• https://dl.kublr.com/controlplane/1.18.1/kublr-helm-1.18.1.tar.gz
• https://dl.kublr.com/controlplane/1.18.1/kublr-controlplane-images-1.18.1.tar.gz

Supported Kubernetes versions

v1.17.7

• https://repo.kublr.com/repository/arc/agent/1.17.7/kublr-agent-load-gobins-1.17.7-4.sh

• https://dl.kublr.com/agent/1.17.7/kublr-agent-1.17.7-4.tar.gz

• https://repo.kublr.com/repository/arc/agent/1.17.7/kublr-agent-load-images-1.17.7-4.sh

  (optional if the control plane 1.18.1 images are imported already)

• https://dl.kublr.com/agent/1.17.7/kublr-agent-images-1.17.7-4.tar.gz

  (optional if the control plane 1.18.1 images are imported already)

v1.16 (Deprecated in 1.20.0)

• https://repo.kublr.com/repository/arc/agent/1.16.13/kublr-agent-load-gobins-1.16.10-2.sh
• https://dl.kublr.com/agent/1.16.10/kublr-agent-1.16.10-2.tar.gz
• https://repo.kublr.com/repository/arc/agent/1.16.10/kublr-agent-load-images-1.16.10-2.sh
• https://dl.kublr.com/agent/1.16.10/kublr-agent-images-1.16.10-2.tar.gz

v1.15 (Deprecated in 1.19.0)

• https://repo.kublr.com/repository/arc/agent/1.15.11/kublr-agent-load-gobins-1.15.11-3.sh
• https://dl.kublr.com/agent/1.15.11/kublr-agent-1.15.11-3.tar.gz
• https://repo.kublr.com/repository/arc/agent/1.15.11/kublr-agent-load-images-1.15.11-3.sh
• https://dl.kublr.com/agent/1.15.11/kublr-agent-images-1.15.11-3.tar.gz

Components versions

Kubernetes

Kublr Control Plane

Kublr Platform Features

Known issues and limitations

1. If you upgrade the platform from version 1.18.0 to 1.18.1, only agent version 1.18.1 will be available after the upgrade. If managed clusters are using agents of previous versions, these agent versions will need to be added manually in the settings page.

2. For migration to 1.18 review Kublr 1.18 migration document.

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.