To quickly start using Kublr, run the following command:
sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 kublr/kublr:1.24.2
Note that the Kublr Demo/Installer docker container can be run on ARM-based PCs, such as the MacBook M1. For full instructions on getting started with Kublr, please refer to our Quick start guide at /quickstart/.
The Kublr Demo/Installer is a lightweight, dockerized, limited-functionality platform that comes with a base trial license for Kublr. It can be used to:
Please note that 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.
The Kublr 1.24.2 patch release includes critical bug fixes for AWS volume resizer for version 1.24.1 and contains vSphere improvements for Distributed Switch support.
If you run Kublr clusters on AWS, we recommend migrating to v1.24.2 as soon as possible.
All Kublr components have been scanned for vulnerabilities using the Aquasecurity Trivy scanner. This release also includes various other improvements and fixes in addition to these key features.
AWS CSI Volume resizer has the wrong image. Please migrate to the latest agent version.
vSphere Distributed Switch is now supported on the UI and in the cluster specification.
The VMware vSphere has changed its behavior for custom root folders path customization. Please refer to our solution portal for use cases at https://support.kublr.com/support/solutions/articles/33000278409-vsphere-use-custom-root-folder-and-root-datastorage-dir
To use Kublr in an airgap environment, you will need to download the following BASH scripts from the repository at https://repo.kublr.com:
In addition to the BASH scripts, you will also need to download the following Helm package archives and Docker images:
Component | Version | Kublr Agent | Notes |
---|---|---|---|
Kubernetes | 1.24 | 1.24.8-7 | default v1.24.8 |
1.23 | 1.23.14-7 | ||
1.22 | 1.22.16-7 | ||
1.21 | 1.21.14-13 | Deprecated in 1.25.0 | |
1.20 | 1.20.14-17 | End of support in 1.25.0 |
Component | Version |
---|---|
Kublr Operator | 1.24.2 |
Kublr Control Plane | 1.24.2 |
Component | Version |
---|---|
Kubernetes | |
Dashboard | v2.4.0 |
Kublr System | 1.24.1 |
LocalPath Provisioner (helm chart version) | 0.0.23-12 |
Ingress | 1.24.1 |
nginx ingress controller (helm chart version) | 4.2.3 |
cert-manager (helm chart version) | 1.5.3 |
Centralized Logging | 1.24.1 |
ElasticSearch | 7.10.2 |
Kibana | 7.10.2 |
SearchGuard | 53.6.0 |
SearchGuard Kibana plugin | 53.0.0 |
SearchGuard Admin | 7.10.2-53.6.0 |
RabbitMQ | 3.9.5 |
Curator | 5.8.1 |
Logstash | 7.10.2 |
Fluentd | 3.3.0 |
Fluentbit | 1.8.10 |
Centralized Monitoring | 1.23.0 |
Prometheus | 2.37.1 LTS |
Kube State Metrics (helm chart version) | 4.20.2 |
AlertManager | 0.22.0 |
Grafana | 8.5.13 |
Victoria Metrics | |
Cluster | 0.9.32 |
Agent | 0.8.12 |
Alert | 0.4.35 |
When deploying Kublr Kubernetes clusters on vSphere with Kublr v1.23.2 or earlier, you must manually unmount CD/DVD drive 1 from each virtual machine using the vCenter console.
Deleting vSphere clusters is not automatic and requires manual removal of the VMs and unregistration of the cluster.
The Kublr Control Plane can only be updated from version 1.21.0 or higher.