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.19.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:
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.
This update contains critical patches and improvements, fixes in BareMetal upgrade procedure, and support for scaling up master group in GCP clusters. Default versions of Kubernetes 1.17 and 1.18 are upgraded to v1.17.12 and v1.18.9 correspondingly.
Refer to AirGap deployment instructions for details on Kublr installation.
KCP image and binary archive load scripts:
KCP image and binary archives:
https://repo.kublr.com/repository/arc/agent/1.18.9/kublr-agent-load-gobins-1.18.9-8.sh
https://dl.kublr.com/agent/1.18.9/kublr-agent-1.18.9-8.tar.gz
https://repo.kublr.com/repository/arc/agent/1.18.9/kublr-agent-load-images-1.18.9-8.sh
(optional if the control plane 1.19.1 images are imported already)
https://dl.kublr.com/agent/1.18.9/kublr-agent-images-1.18.9-8.tar.gz
(optional if the control plane 1.19.1 images are imported already)
| Component | Version | Kublr Agent | Note |
|---|---|---|---|
| Kubernetes | 1.18 | 1.18.9-8 | default v1.18.9 |
| 1.17 | 1.17.12-11 | ||
| 1.16 | 1.16.13-5 | Deprecated in 1.20.0 | |
| 1.15.(11, 12) | 1.15.12-7 | End of support in 1.20.0 |
| Component | Version |
|---|---|
| Kublr Control Plane | 1.19.1-93 |
| Kublr Operator | 1.19.1-37 |
| Component | Version |
|---|---|
| Kublr System | 1.19.1-32 |
| LocalPath Provisioner (helm chart version) | 0.0.12-6 |
| Ingress | 1.19.1-34 |
| nginx ingress controller (helm chart version) | 1.36.2 |
| cert-manager | 0.14.2 |
| Centralized Logging | 1.19.1-39 |
| ElasticSearch | 6.8.4 |
| Kibana | 6.8.4 |
| SearchGuard | 25.5.0 |
| SearchGuard Kibana plugin | 25.5.0 |
| SearchGuard Admin | 6.8.4-25.5.0 |
| RabbitMQ | 3.8.3 |
| Curator | 5.8.1 |
| Logstash | 6.8.4 |
| Fluentd | 2.7.1 |
| Centralized Monitoring | 1.19.1-35 |
| Prometheus | 2.13.0 |
| Kube State Metrics | 2.4.1 |
| AlertManager | 0.19.0 |
| Grafana | 6.5.1 |
| Kublr KubeDB | 1.19.1-32 |
| kubedb (helm chart version) | v0.14.0-alpha.2 |
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.
In some cases, cluster upgrade process crashes on Azure due to underlying VM issues. The issue usually resolves after re-running the update procedure in ~30 minutes.
Kubernetes cluster auto-scaler may fail to scale AWS Kubernetes cluster if scheduled on a worker node rather than on a master node. As a workaround, node affinity rule may be applied to schedule the cluster autoscaler to the masters; the fix is scheduled for Kublr 1.19.2 release (see Release Notes 1.19.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.