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.20.2
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 bug fixes, Azure autoscaling support, Kubernetes v1.20.4 and VictoriaMetrics technical preview.
https://github.com/kubernetes/kubernetes/releases/tag/v1.20.4
Kuberntes 1.20.4 can be used for Kublr cluster installation. Add kublr agent 1.20.4-1
into agent list on setting page.
Important notice: This is a technical preview not recommended for use in production environments
https://github.com/VictoriaMetrics/VictoriaMetrics
VictoriaMetrics can be enabled in Kublr feature Monitoring for collecting metrics along with Prometheus.
Important notice: This is a technical preview not recommended for use in production environments
To enable this feature, modify spec.features.monitoring
section in the cluster specification:
spec:
features:
monitoring:
values:
victoriametrics:
enabled: true
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.19.7/kublr-agent-load-gobins-1.19.7-29.sh
https://dl.kublr.com/agent/1.19.7/kublr-agent-1.19.7-29.tar.gz
https://repo.kublr.com/repository/arc/agent/1.19.7/kublr-agent-load-images-1.19.7-29.sh
(optional if the control plane 1.20.2 images are imported already)
https://dl.kublr.com/agent/1.19.7/kublr-agent-images-1.19.7-29.tar.gz
(optional if the control plane 1.20.2 images are imported already)
Component | Version | Kublr Agent | Note |
---|---|---|---|
Kubernetes | 1.19 | 1.19.7-29 | default v1.19.7 |
1.18 | 1.18.15-7 | ||
1.17 | 1.17.17-8 | Deprecated in 1.21.0 | |
1.16 | 1.16.15-7 | End of support in 1.21.0 | |
1.20 | 1.20.4-1 | Technical preview |
Component | Version |
---|---|
Kublr Control Plane | 1.20.2-95 |
Kublr Operator | 1.20.2-40 |
Component | Version |
---|---|
Kuberntes | |
Dashboard | v2.0.4 |
Tiller | |
Kublr System | 1.20.2-37 |
LocalPath Provisioner (helm chart version) | 0.0.12-6 |
Ingress | 1.20.2-35 |
nginx ingress controller (helm chart version) | 1.36.2 |
cert-manager | 0.14.2 |
Centralized Logging | 1.20.2-58 |
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.20.2-42 |
Prometheus | 2.24.1 |
Kube State Metrics | 2.4.1 |
AlertManager | 0.21.0 |
Grafana | 7.4.1 |
Kublr KubeDB | 1.20.2-36 |
kubedb (helm chart version) | v0.14.0-alpha.2 |
Azure cluster autoscaling is only supported with Kublr agents 1.18.15-7
or 1.19.7-29
and above.
For migration from Kubernetes versions below 1.19:
kubectl delete cm -n kube-system coredns
If customized values are used for the centralized logging package, please refer to Logging upgrade notice for custom defined values.
Managed cluster migration from previous major Kublr version (<1.18.0) have limitations related to updgrading Kublr components to Kublr 1.20. Please refer to Kublr 1.18 migration document for more details.
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:
If you have a paid Docker Hub account, create a docker.io secret in Kublr Control Plane and add this docker registry to the cluster specification using advanced section in Kublr cluster creation UI.
Override docker.io registry with cr.kublr.com, all imagess needed for cluster installation are mirrored in this repo. Learn more about docker registry override in the Kublr documentation cluster specification reference.
(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.