Kublr Release 1.15.0 (2019-12-04)

Kublr Quick Start

sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 kublr/kublr:1.15.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’ll have to create a full-featured Kublr Platform in a cloud or on-premise.

Overview

This major release provides a new user interface to manage RBAC in Kubernetes clusters and integrates Kublr and Kubernetes RBAC. Through the Kublr UI, administrators can now restrict access or provide limited access to certain Kubernetes namespaces.

A common use case is providing developers with read-only access to the production environment (referred to in Kubernetes as namespace). Please refer to the quick start for details.

We added the Kubernetes Dashboard v2.

Additionally, Kubernetes core components requests and limits were reviewed. New Kublr Kubernetes clusters require now fewer resources (memory and CPU).

And last but not least, we updated “Centralized Logging and Monitoring” with newer components and implemented a new architecture design to move logs between clusters.

Changelog

1. Kubernetes 1.15.7
2. Kublr and Kubernetes RBAC integration
3. Dashboard v2
4. User interface:
   • User interface for managing Kubernetes RBAC
5. Centralized monitoring:
   • Update to Prometheus 2.13 and Grafana 6.5
6. Centralized logging:
   • Architecture redesign
   • ELK 6.8.4
7. Ingress controller
   • Ingress controller 1.24.5
   • Remove kube-lego
8. Reviewed core Kubernetes requests and limits

Known Issues

1. In the case of using an AWS cloud without its own domain (the default AWS ELB domain used), you may have problems reaching Kibana in the Safari web browser. There’s workaround to be done here: resolve the domain name and use an IP address instead.

Components versions

Kubernetes

Kublr Control Plane

Kublr Platform Features