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.
sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 kublr/kublr:1.17.1
The Kublr Demo/Installer is a lightweight, dockerized, limited-functionality Kublr Platform which can be used to:
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.
This update contains Kubernetes 1.17.4 and bug fixes. We also added Kubernetes 1.15.11. The version 1.15.11 can be useful for testing migration applications from 1.15.x to a newer version.
| Component | Version |
|---|---|
| Kubernetes | 1.17.4 |
| 1.17.3 | |
| 1.16.8 | |
| 1.16.7 | |
| 1.16.6 | |
| 1.16.4 | |
| 1.15.11 | |
| etcd | 3.3.15 |
| Kubernetes Dashboard | 2.0.0-rc5 |
| Component | Version |
|---|---|
| Kublr Control Plane | 1.17.1 |
| Component | Version |
|---|---|
| Ingress | 1.17.1 |
| nginx ingress controller (helm chart version) | 1.24.5 |
| cert-manager | 0.11 |
| Centralized Logging | 1.17.0 |
| ElasticSearch | 6.8.4 |
| Kibana | 6.8.4 |
| SearchGuard plugin | 25.5.0 |
| SearchGuard Kibana plugin | 25.5.0 |
| SearchGuard Admin | 6.8.4-25.5.0 |
| RabbitMQ | 3.7.3 |
| Curator | 5.5.1 |
| Logstash | 6.8.4 |
| Fluentd | 2.7.1 |
| Centralized Monitoring | 1.17.1 |
| Prometheus | 2.13.0 |
| Kube State Metrics | 1.8.0 |
| AlertManager | 0.16.2 |
| Grafana | 6.5.1 |
| System | 1.17.1 |
| сoredns | 1.6.2 |
(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.