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.
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.0
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:
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.
This major release brings role-based access control (RBAC). System administrators will now be able dynamically create security policies which can be used to restrict/grant access to certain users or groups of users. For example, a system administrator will be able to create a policy to grant or restrict access for creating, updating, deleting, or even viewing clusters. Furthermore, it is possible to restrict access from viewing cluster resources, such as events, metrics, endpoints, and applications. We also have included useful improvements and known issue fixes.
Ingress Service not initialized when Kublr cluster created with existing VPC
(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.
Component | Version |
---|---|
Kubernetes | 1.11.5 |
etcd | 3.2.18 |
Kubernetes Dashboard | 1.8.3 |
Component | Version |
---|---|
Kublr Control Plane | 1.11.0 |
Component | Version |
---|---|
Ingress | 0.3.5 |
nginx ingress controller (helm chart version) | 0.20.3 |
kube-lego (helm chart version) | 0.4.2 |
Centralized Logging | 1.11.0 |
ElasticSearch | 6.4.0 |
Kibana | 6.4.0 |
ElasticSearch Exporter | 1.0.1 |
Rabbitmq | 3.7.3 |
Curator | 5.5.1 |
Logstash | 6.4.0 |
Fluentd | 2.3.1 |
Centralized Monitoring | 1.11.0 |
Prometheus | 2.3.2 |
Kube State Metrics | 1.3.1 |
AlertManager | 0.15.2 |
Grafana | 5.2.2 |
System | 0.3.4 |