sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 kublr/kublr:1.23.2
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.
Kublr 1.23.2 patch release includes vSphere deployment change with root folder support. With that it becomes possible to specify a folder in vCenter to be used as the root folder for a Kublr cluster deployment.
All Kublr components are checked for vulnerabilities with Aquasecurity trivy scaner.
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.7/kublr-agent-load-gobins-1.24.7-1.sh
https://dl.kublr.com/agent/1.24.7/kublr-agent-1.24.7-1.tar.gz
https://repo.kublr.com/repository/arc/agent/1.24.7/kublr-agent-load-images-1.24.7-1.sh
(optional if the control plane 1.23.2 images are imported already)
https://dl.kublr.com/agent/1.24.7/kublr-agent-images-1.24.7-1.tar.gz
(optional if the control plane 1.23.2 images are imported already)
| Component | Version | Kublr Agent | Notes |
|---|---|---|---|
| Kubernetes | 1.24 | 1.24.7-1 | default v1.24.7 |
| 1.23 | 1.23.13-1 | ||
| 1.22 | 1.22.15-1 | ||
| 1.21 | 1.21.14-8 | ||
| 1.20 | 1.20.14-9 | Deprecated in 1.24.0 | |
| 1.19 | 1.19.16-9 | End of support in 1.24.0 |
| Component | Version |
|---|---|
| Kublr Operator | 1.23.2 |
| Kublr Control Plane | 1.23.2 |
| Component | Version |
|---|---|
| Kubernetes | |
| Dashboard | v2.4.0 |
| Kublr System | 1.23.2 |
| LocalPath Provisioner (helm chart version) | 0.0.22-11 |
| Ingress | 1.23.2 |
| nginx ingress controller (helm chart version) | 4.2.3 |
| cert-manager (helm chart version) | 1.5.3 |
| Centralized Logging | **1.23.2 * |
| 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.2 |
| 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
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.