sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 kublr/kublr:1.23.0
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 with base trial license 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.
The Kublr 1.23.0 release brings Kubernetes 1.23 and 1.24, proxy servers supports, upgraded NGINX controler and terraform controller versions.
All Kublr components are checked for vulnerabilities with Aquasecurity trivy scaner.
It also includes new Kublr license management UI, and provides a number of other improvements and fixes.
New versions of Kubernetes
Kubernetes v1.23 (v1.23.10 by default), v1.24 (v1.24.6 by default) support
SELinux policy upgrade
Proxy servers configuration supports
Kublr license management
Kuberntes Pod Security Policy feature is deprecated and will be removed from Kubernetes v1.25
baseline PodSecurityConfiguration:apiVersion: pod-security.admission.config.k8s.io/v1beta1
kind: PodSecurityConfiguration
defaults:
enforce: "baseline"
enforce-version: "latest"
audit: "baseline"
audit-version: "latest"
warn: "baseline"
warn-version: "latest"
exemptions:
usernames: []
runtimeClasses: []
namespaces: [kube-system,kublr]
Kublr Demo/Installer image is now a docker multiarch AMD64/ARM64 image
Kublr cert-updater is deprecated in Kublr v1.23 and is removed from Kublr agent starting with v1.22 and above
Kublr backup controller is deprecated in Kublr v1.23 and will be removed from Kublr 1.24.0
Kubernetes v1.19 support in Kublr v1.23 is deprecated and will be removed in Kublr v1.24.0
Upgrade patch versions of supported Kubernetes versions
Keycloak v15.1.1 used
Kublr Operator:
Kublr Terraform controller
terraform migrated to v1.1.7
Currently supported versions: 0.12.30, 0.13.6, 0.14.11, 1.1.7
Please read an important note above for vSphere based clusters upgrade procedure!
Kublr Monitoring:
Kublr Logging:
RabbitMQ v9.5.3
Fluentbit enabled by default (instead of Fluentd)
RabbitMQ space limit autofix
The following settings are removed from the default template:
"auto_expand_replicas": "0-1",
"codec": "best_compression"
Kublr feature ingress
Kubernetes NGINX controller automaticaly migrates to v1.3.0 (helm chart v4.2.3)
This may affect the applications deployed to the managed clusters; please refer to NGINX Ingress Controller documentation to prepare for the upgrade.
Kublr Agent
vSphere:
AWS:
Azure:
Stability, Reliability and security
Various UI Improvements
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.24.6/kublr-agent-load-gobins-1.24.6-7.sh
https://dl.kublr.com/agent/1.24.6/kublr-agent-1.24.6-7.tar.gz
https://repo.kublr.com/repository/arc/agent/1.24.6/kublr-agent-load-images-1.24.6-7.sh
(optional if the control plane 1.23.0 images are imported already)
https://dl.kublr.com/agent/1.24.6/kublr-agent-images-1.24.6-7.tar.gz
(optional if the control plane 1.23.0 images are imported already)
| Component | Version | Kublr Agent | Notes |
|---|---|---|---|
| Kubernetes | 1.24 | 1.24.6-7 | default v1.24.6 |
| 1.23 | 1.23.10-7 | ||
| 1.22 | 1.22.13-7 | ||
| 1.21 | 1.21.14-7 | ||
| 1.20 | 1.20.14-7 | Deprecated in 1.24.0 | |
| 1.19 | 1.19.16-7 | End of support in 1.24.0 |
| Component | Version |
|---|---|
| Kublr Operator | 1.23.0 |
| Kublr Control Plane | 1.23.0 |
| Component | Version |
|---|---|
| Kubernetes | |
| Dashboard | v2.4.0 |
| Kublr System | 1.23.0 |
| LocalPath Provisioner (helm chart version) | 0.0.22-11 |
| Ingress | 1.23.0 |
| nginx ingress controller (helm chart version) | 4.2.3 |
| cert-manager (helm chart version) | 1.5.3 |
| Centralized Logging | **1.23.0 * |
| ElasticSearch | 7.10.2 |
| Kibana | 7.10.2 |
| SearchGuard | 52.3.0 |
| SearchGuard Kibana plugin | 51.0.0 |
| SearchGuard Admin | 7.10.2-52.3.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 |
| Kube State Metrics (helm chart version) | 3.4.2 |
| AlertManager | 0.22.0 |
| Grafana | 7.5.10 |
| Victoria Metrics | |
| Cluster | 0.9.13 |
| Agent | 0.7.35 |
| Alert | 0.4.15 |
ContainerD CRI does not support private registry authentication; use the following cluster spec configuration override as a workaround if needed:
kublrAgentConfig:
kublr:
containerd:
config:
plugins:
"io.containerd.grpc.v1.cri":
registry:
configs:
"{{ DOCKER_REPO_URL }}":
auth:
username: {{ REPO_USER }}
password: {{ REPO_PASSWORD }}
tls:
insecure_skip_verify: true
After adding a new managed cluster with centralized logging enabled, a default index pattern is not created automaticaly in Kibana. You will need to add the index pattern manually via Kibana cluster settings.
For Kublr kubernetes clusters deployed on vSphere it is necessary to unmount CD/DVD drive 1 from each virtual machines manually via vCenter console.
vSphere clusters cannot be deleted automaticaly, it is necessary to remove VMs manually and unregister the cluster after that.