Kublr Release 1.19.3 (2020-11-03)

Kublr Quick Start

sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 kublr/kublr:1.19.3

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 clusters and the platforms themselves.

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 can create a full-featured Kublr Platform in a cloud or on-premise.

Overview

The Kublr 1.19.3 release includes AWS partitions support in UI (AWS standard cloud, AWS Gov cloud, and AWS China etc), full support for encryption on AWS cloud, v27 API for VMWare vCloud Director, updates for default alert rules in the centralized monitroing, and stability updates for the centralized logging.

Important Changes

  • AWS partitions) support. Kublr supports AWS standard cloud (aws), AWS Gov cloud (aws-us-gov), AWS China (aws-cn), aws-iso, and aws-iso-b (top secret) partitions.
  • VMWare vCloud Director v27 API support
  • S3 encryption support in AWS cluster
  • Control plane configuration page refactored (refer to upgrade notes for details)

Improvements and stability

  • Kublr Audit service improvements
  • Cluster update/creation flow improvments
  • Centralized logging fixes to improve stability, ELK chart synced with the upstream
  • Centralized monitoring default alert rules fixes
  • Fixed issue with cluster nodes not displayed in Kublr UI when metrics server is not installed in the cluster
  • UI/UX fixes

AirGap Artifacts list

Refer to AirGap deployment instructions for details on Kublr installation.

KCP image and binary archive load scripts:

KCP image and binary archives:

Supported Kubernetes versions

v1.18

v1.17

v1.16 (Deprecated in 1.20.0)

v1.15 (End of support in 1.20.0)

Components versions

Kubernetes

ComponentVersionKublr AgentNote
Kubernetes1.181.18.9-14default v1.18.9
1.171.17.12-19
1.161.16.13-10Deprecated in 1.20.0
1.15.(11, 12)1.15.12-13End of support in 1.20.0

Kublr Control Plane

ComponentVersion
Kublr Control Plane1.19.3-146
Kublr Operator1.19.3-59

Kublr Platform Features

ComponentVersion
Kublr System1.19.3-49
LocalPath Provisioner (helm chart version)0.0.12-6
Ingress1.19.3-51
nginx ingress controller (helm chart version)1.36.2
cert-manager0.14.2
Centralized Logging1.19.3-60
ElasticSearch6.8.4
Kibana6.8.4
RabbitMQ3.8.3
Curator5.8.1
Logstash6.8.4
Fluentd2.7.1
Centralized Monitoring1.19.3-55
Prometheus2.13.0
Kube State Metrics2.4.1
AlertManager0.19.0
Grafana6.5.1
Kublr KubeDB1.19.3-49
kubedb (helm chart version)v0.14.0-alpha.2

Upgrade notes

  1. In 1.19.3 in settings, ‘/api’ path should be removed from in the Public API Endpoint. The address should look like “https://kublr-control-plane.example.com” (no path in the URL), while in 1.19.2 it looked like “https://kublr-control-plane.example.com/api". Go to Kublr Control Plane configuration page and modify Public API Endpoint.

Known issues and limitations

  1. Managed cluster migration from previos major Kublr version (<1.18.0) have limitations related to updgrading Kublr components to Kublr 1.18. Please refer to Kublr 1.18 migration document for more detail.

  2. Beginning November 2, 2020, progressive enforcement of rate limits for anonymous and authenticated Docker Hub usage goes into effect. Learn more on understanding Docker Hub Rate Limiting. Kublr clusters use some images hosted on docker.io (e.g. kubernetesui/dashboard:v2.0.4). As a result some cluster operations may fail due to Docker Hub rate limiting. You can avoid possible problems by one of the following solutions:

    1. If you own a paid Docker Hub account, create a docker.io secret in Kublr Control Plane and add this docker registry to the cluster specification using advanced section in Kublr cluster creation UI.
    2. Override docker.io registry with cr.kublr.com, all imagess needed for cluster installation are mirrored in this repo. Learn more about docker registry override in the Kublr documentation at cluster specification.