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.
Additionally, Kublr release 1.21.0 contains a known issue with Azure resources update and removal.
sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 kublr/kublr:1.21.0
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.
The Kublr 1.21.0 release brings Kuberntes 1.20, multiple container runtimes, and major vCloud Director redesign and improvements including migration to the recent versions of vCloud Director API and SDK, org and app networks of differnet types, edge gateways, NAT and firewall configuration. It also adds support for environments that only have access to public internet via proxy server, and provides a number of other improvements and fixes.
kublrAgentConfig.kublr.version.k8s
Additionally, you need to download the BASH scripts from https://repo.kublr.com
You also need to download Helm package archives and Docker images:
https://repo.kublr.com/repository/arc/agent/1.20.7/kublr-agent-load-gobins-1.20.7-13.sh
https://dl.kublr.com/agent/1.20.7/kublr-agent-1.20.7-13.tar.gz
https://repo.kublr.com/repository/arc/agent/1.20.7/kublr-agent-load-images-1.20.7-13.sh
(optional if the control plane 1.21.0 images are imported already)
https://dl.kublr.com/agent/1.20.7/kublr-agent-images-1.20.7-13.tar.gz
(optional if the control plane 1.21.0 images are imported already)
Component | Version | Kublr Agent | Notes |
---|---|---|---|
Kubernetes | 1.20 | 1.20.7-13 | default v1.20.7 |
1.19 | 1.19.11-43 | ||
1.18 | 1.18.19-22 | Deprecated in 1.22.0 | |
1.17 | 1.17.17-21 | End of support in 1.22.0 | |
1.21 | 1.21.1-5 | technical preview |
Component | Version |
---|---|
Kublr Control Plane | 1.21.0-27 |
Kublr Operator | 1.21.0-11 |
Component | Version |
---|---|
Kuberntes | |
Dashboard | v2.0.4 |
Kublr System | 1.21.0-9 |
LocalPath Provisioner (helm chart version) | 0.0.12-6 |
Ingress | 1.21.0-9 |
nginx ingress controller (helm chart version) | 1.36.2 |
cert-manager | 0.14.2 |
Centralized Logging | 1.21.0-15 |
ElasticSearch | 7.10.2 |
Kibana | 7.10.2 |
SearchGuard | 49.0.0 |
SearchGuard Kibana plugin | 49.0.0 |
SearchGuard Admin | 7.10.2-49.0.0 |
RabbitMQ | 3.8.11 |
Curator | 5.8.1 |
Logstash | 7.10.2 |
Fluentd | 2.7.1 |
Centralized Monitoring | 1.21.0-10 |
Prometheus | 2.24.1 |
Kube State Metrics | 2.4.1 |
AlertManager | 0.21.0 |
Grafana | 7.4.1 |
Victoria Metrics | |
Cluster | 0.8.2 |
Agent | 0.6.5 |
Alert | 0.3.5 |
Kublr KubeDB | 1.21.0-10 |
kubedb (helm chart version) | v0.14.0-alpha.2 |
(Critical) During Azure cluster update, Kublr Cluster Controller tries to remove LoadBalancers created by Kubernets cloud controller.
Please use Kublr 1.21.1 to avoid Azure cluster downtime.
Kublr operator crashes if Tiller is missing or upgraded in a managed cluster
Canal CNI (default) does not work on AWS images with nm-cloud-config
. At the moment it only affects RHEL 8
image.
As a workaround, remove or disable nm-cloud-config
or use a different CNI plugin (e.g. CNI Calico).
SELinux is not supported for ContainerD CRI
Containerd CRI is only supported for Kublr Agents 1.19, 1.20, and 1.21
vCloud Director implementation does not support named disks for persistent volumes by default. vCloud Director CSI driver needs to be installed in the cluster.
Beginning November 2, 2020, progressive enforcement of rate limits for anonymous and authenticated Docker Hub usage came into effect. Learn more about the change from the article Understanding Docker Hub Rate Limiting. Kublr clusters use some images hosted on Docker Hub / 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 issues using one of the following solutions:
(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.