sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 kublr/kublr:1.22.0
Follow the full instructions in Quick start for Kublr Demo/Installer.
The Kublr Demo/Installer is a lightweight, dockerized, limited-functionality 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.
We recommend using the Kublr Demo/Installer to verify if a Kubernetes cluster can be created in your environment and to experiment with it. To manage a real cluster and experience all features, you can create a full-featured Kublr Platform in a cloud or on-premise.
The Kublr 1.22.0 release brings Kubernetes 1.22, upgraded NGINX Ingress controller and CertManager, and latest CNI plugins versions. All java components are updated to resolve CVE-2021-44228 Log4J 0-day vulnerability. It also includes Kublr Operator with CRD v1, and provides a number of other improvements and fixes.
A new elasticsearch index template kublr_logs is created and used instead of kublr-index-template in Kublr v1.22.0.
New versions of Kubernetes
Kubernetes v1.22 support (v1.22.2 by default)
CNI plugins upgraded
CVE-2021-44228: Log4J 0-day Vulnerability fixed in all java components (CVE-2021-44228 Kublr Support article)
Kublr feature ingress is upgraded for Kubernetes v1.22 support
Kubernetes NGINX controller automaticaly migrates to v1.1.0 (helm chart v4.0.10)
This may affect the applications deployed to the managed clusters; please refer to NGINX Ingress Controller documentation to prepare for the upgrade.
Cert Manager automaticaly migrates to v1.5 (helm chart v1.5.3)
To keep compatibility with older Kubernetes versions, cert-manager 1.5 is now compatible with both Ingress v1 and v1beta1. Please refer to Cert Manager release notes for more information
Kublr feature KubeDB end of support (KubeDB is not supported in Kubernetes v1.22 and above)! Please plan the upgrade accordingly if Kublr KubeDB feature is used by the applications running in the cluster.
DNS based URLs for Kublr feature components (Grafana/Kibana/Prometheus/Alertmanager) are migrated to sub-path by default:
Kublr feature logging:
vCloud Director improvements
Upgrade patch versions of supported Kubernetes version
Use OIDC oauth2-proxy instead of keycloak-proxy for all Kublr components
Kublr Operator:
Kublr shell:
Kublr feature Monitoring:
Kublr feature Logging:
Kublr Agent
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.22.2/kublr-agent-load-gobins-1.22.2-7.sh
https://dl.kublr.com/agent/1.22.2/kublr-agent-1.22.2-7.tar.gz
https://repo.kublr.com/repository/arc/agent/1.22.2/kublr-agent-load-images-1.22.2-7.sh
(optional if the control plane 1.22.0 images are imported already)
https://dl.kublr.com/agent/1.22.2/kublr-agent-images-1.22.2-7.tar.gz
(optional if the control plane 1.22.0 images are imported already)
| Component | Version | Kublr Agent | Notes |
|---|---|---|---|
| Kubernetes | 1.22 | 1.22.2-7 | default v1.22.2 |
| 1.21 | 1.21.6-23 | ||
| 1.20 | 1.20.12-28 | ||
| 1.19 | 1.19.16-58 | Deprecated in 1.23.0 | |
| 1.18 | 1.18.20-34 | End of support in 1.22.1 |
| Component | Version |
|---|---|
| Kublr Operator | 1.22.0-6 |
| Kublr Control Plane | 1.22.0-24 |
| Component | Version |
|---|---|
| Kubernetes | |
| Dashboard | v2.2.0 |
| Kublr System | 1.22.0-4 |
| LocalPath Provisioner (helm chart version) | 0.0.12-8 |
| Ingress | 1.22.0-5 |
| nginx ingress controller (helm chart version) | 4.0.10 |
| cert-manager (helm chart version) | 1.5.3 |
| Centralized Logging | 1.22.0-13 |
| 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.22.0-7 |
| Prometheus | 2.28.1 |
| Kube State Metrics (helm chart version) | 3.4.2 |
| AlertManager | 0.22.0 |
| Grafana | 7.5.10 |
| Victoria Metrics | |
| Cluster | 0.8.2 |
| Agent | 0.6.5 |
| Alert | 0.3.5 |
| Kublr KubeDB (Deprecated in 1.22.0, End of support in 1.23.0) | 1.22.0-3 |
| kubedb (helm chart version) | v0.14.0-alpha.2 |
Kublr feature Ingress 1.22.0-5 included in Kublr 1.22.0 only supports Kubernetes v1.19 and above, so for Kubernetes v1.18 clusters please use Kublr feature Ingress 1.21.2-24 (the version can be overridded in the custom cluster spec).
Kublr feature KubeDB reaches end of support in Kublr v1.22.0 and is not supported on Kubernetes v1.22 and above. Please remove the feature from the cluster specification after Kublr Control Plane upgrade:
spec:
features:
kubedb:
enabled: false
When upgrading a Kubernetes v1.22, Kublr feature Ingress must first be upgraded to v1.22.0-5.
If applications deployed to the cluster are using Kublr-managed ingress controller, review their ingress rules
before upgrading and make sure that spec.ingressClassName proerty is set to nginx.
For Kublr Control Plane deployed on baremetal clusters it is recomended to skip Kublr 1.22.0 and migrate to Kublr v1.22.1 directly.
If for any reason it is necessary to use Kublr v1.22.0, it is recomended to modify the cluster specification for the controlplane feature as follows on update:
spec:
featrures:
controlplane:
values:
mongodb:
initContainers:
- name: kublr-migrate-move-data-kubdb-to-bitnami
image: 'docker.io/bitnami/bitnami-shell:10-debian-10-r197'
command:
- /bin/bash
- -c
- |
if [[ ! -d /bitnami/mongodb/data/db ]] ; then
mkdir -p /bitnami/mongodb/data/db
ls /bitnami/mongodb/ -I data | xargs -i mv /bitnami/mongodb/{} /bitnami/mongodb/data/db/
fi
volumeMounts:
- mountPath: /bitnami/mongodb
name: datadir
If fluentbit log collection is enabled, most audit records are rejected by elasticsearch and end up in the logstash dead letter queue.
Fluentbit was introduced in preview mode and is disabled by default.
If Elasticsearch datastreams are enabled, then SearchGuard security rules must be updated by running the kublr-logging-sg-init cron job manually.
The job will overwrite all custom SearchGuard configuration changes and customizations ( https://docs.kublr.com/logging/#roles-customization ).
Elasticsearch datastreams functionality is disabled by default.