This release contains a critical fix in the cluster controller for AWS clusters. In cases where there is an incorrect CloudFormation Extra resources definition for AWS, the Kublr cluster controller locks the database and prevents new cluster operations from being created.
The Kublr team strongly recommends that customers migrate to v1.25.3.
To quickly get started with Kublr, run the following command in your terminal:
sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 kublr/kublr:1.25.1
The Kublr Demo/Installer docker container can be run on ARM-based PC, such as MacBook M1.
Follow the full instructions in Quick start for Kublr Demo/Installer.
The Kublr Demo/Installer is a lightweight, dockerized, limited-functionality Kublr Platform with a base trial license. It can be used for the following purposes:
The Kublr Demo/Installer stores all data about created clusters inside the Docker container. If you delete the container, you will lose all data about the created clusters and the Kublr platforms. However, you will not lose the clusters and platforms themselves.
To use Kublr in an airgap environment, you will need to download the following BASH scripts from the repository at https://repo.kublr.com:
You will also need to download the following Helm package archives and Docker images list:
| Component | Version | Kublr Agent | Notes |
|---|---|---|---|
| Kubernetes | 1.25 | 1.25.6-4 (important to use 1.25.6-6) | default v1.25.6 |
| 1.24 | 1.24.9-4 (important to use 1.24.9-6) | ||
| 1.23 | 1.23.15-4 (important to use 1.23.15-6) | ||
| 1.22 | 1.22.17-4 (important to use 1.22.17-8) | Deprecated in 1.26.0 | |
| 1.21 | 1.21.14-22 (important to use 1.21.14-24) | End of support in 1.26.0 |
| Component | Version |
|---|---|
| Kublr Operator | 1.25.1 |
| Kublr Control Plane | 1.25.1 |
| Component | Version |
|---|---|
| Kubernetes | |
| Dashboard | v2.7.0 |
| Kublr System | 1.25.1 |
| LocalPath Provisioner (helm chart version) | 0.0.23-12 |
| Ingress | 1.25.1 |
| nginx ingress controller (helm chart version) | 4.2.3 |
| cert-manager (helm chart version) | 1.10.0 |
| Centralized Logging | 1.25.1 |
| ElasticSearch | 7.10.2 |
| SearchGuard | 53.6.0 |
| Kibana | 7.10.2 |
| SearchGuard Kibana plugin | 53.0.0 |
| SearchGuard Admin | 7.10.2-53.6.0 |
| OpenSearch (helm chart version) | 2.6.2 |
| OpenSearch Dashboards | (helm chart version) |
| RabbitMQ | 3.9.5 |
| Curator | 5.8.1 |
| Logstash | 7.10.2 |
| Fluentd | 4.3.3 |
| Fluentbit | 1.8.12 |
| Centralized Monitoring | 1.25.1 |
| Prometheus | 2.37.1 LTS |
| Kube State Metrics (helm chart version) | 4.24.0 |
| AlertManager | 0.22.0 |
| Grafana | 8.5.13 |
| Victoria Metrics | |
| Cluster | 0.9.59 |
| Agent | 0.8.35 |
| Alert | 0.5.21 |
For Kublr Kubernetes clusters deployed on vSphere, perhaps you will need unmount CD/DVD drive 1 from each virtual machine manually using the vCenter console on update error.
Elasticsearch supports only in AMD64 architecture, you can use tag 7.17.9 for ARM64 cluster nodes.
vSphere CSI limitation Please refer to VMWare documentation for vSphere Functionality Supported by vSphere Container Storage Plug-in