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.28.0
The Kublr Demo/Installer docker container can be run on ARM-based machines, such as MacBook M1.
Follow the full instructions in Quick start for Kublr Demo/Installer.
The Kublr 1.28.0 release introduces several new features and improvements, including:
All Kublr components are checked for vulnerabilities using Aquasecurity trivy scaner. In addition to these major features, the release also includes various other improvements and fixes.
Version | Kublr Agent | Notes |
---|---|---|
1.28 | 1.28.8-1 | Default version: v1.28.8 |
1.27 | 1.27.12-1 | |
1.26 | 1.26.15-1 | |
1.25 | 1.25.16-1 | Deprecated in 1.29.0 |
1.24 | 1.24.13-6 | End of support in 1.29.0 |
New versions of Kubernetes:
Kubernetes v1.28 (v1.28.8 by default) support
Kublr 1.28 CNCF Kubernetes conformance
Before upgrading your managed cluster, make sure to upgrade all Kublr components to v1.28.0 or above. Note that if you use Pod Security Policies (PSP) in your application deployments, be aware of the PSP end of support in Kubernetes v1.25.0.
Deprecations:
Kublr now supports cluster specification templating. You can utilize Go template functionality in the cluster specification.
The Kublr Helm Manager enables helm package installation on the infrastructure layer before Kubernetes nodes reach the Ready state. The Manager utilizes Kubernetes secrets as CR definitions and operates as a Kubernetes operator, functioning similarly to the native Kubernetes Addon Manager.
Kublr Operator contains values.yaml templating logic in the helm packages. You can specify templates/kublr/values-template.yaml file in the helm chart for values.yaml calculating before install/upgrade begins
The Kublr Operator incorporates values.yaml templating logic in the helm packages. You can specify the templates/kublr/values-template.yaml file in the helm chart to calculate values.yaml before the install/upgrade process begins.
Kublr Helm packages now utilize the Kublr Common package. Helm development standards have been implemented.
The Cluster Controller has undergone a complete refactor of its node update/reconcile logic. As a result, you now have access to comprehensive node status information on the UI.
A Velero-based BackUp controller has been implemented for AWS (technical preview). Please refer to our support portal for usage examples.
Kublr Agents:
Kublr Control Plane:
Azure:
AWS:
vSphere:
Centralized Log Collection:
Centralized Monitoring:
Kublr NGINX Ingress:
Stability, Reliability, and Security:
Component | Version |
---|---|
Kublr Operator | 1.28.0 |
Kublr Control Plane | 1.28.0 |
Component | Version |
---|---|
Kubernetes | |
Dashboard | v2.7.0 |
Kublr System | 1.28.0 |
LocalPath Provisioner (helm chart version) | 0.0.24 |
Ingress | 1.28.0 |
nginx ingress controller (helm chart version) | 4.8.0 |
cert-manager (helm chart version) | 1.13.2 |
Centralized Logging | 1.28.0 |
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.13.3 |
OpenSearch Dashboards | (helm chart version) |
RabbitMQ | 3.9.5 |
Curator | 5.8.1 |
Logstash | 7.10.2 |
Fluentd | 1.16.3 |
Fluentbit | 2.1.8 |
Centralized Monitoring | 1.28.0 |
Prometheus | 2.45.0 LTS |
Kube State Metrics (helm chart version) | 5.16.4 |
AlertManager | 0.27.0 |
Grafana (helm chart version) | 7.3.5 |
Victoria Metrics | |
Cluster | 0.11.13 |
Agent | 0.10.3 |
Alert | 0.9.3 |
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 archive and Docker images lists: