Kublr Release 1.22.2 (2022-03-15)

Kublr Quick Start

sudo docker run --name kublr -d --restart=unless-stopped -p 9080:9080 kublr/kublr:1.22.2

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:

  • Test setup and management of a standalone Kubernetes cluster
  • Setup a full-featured Kublr Platform

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.

Overview

The Kublr 1.22.2 patch release includes bug fixes in Kublr feature Ingress with pod termination on each update request; Kibana pod terminated on Kublr feature Logging update; CloudWatch issue on Kuberntes 1.22 and Alertmanager configurability improvements with extraVar/extraEnv in helm chart.

Important Fixes and Improvements

  • MongoDB exporter in AirGap env override issue
  • Ingress Controller terminates all running pod on each cluster upgrade request
  • Centralized Log collection:
    • Init Elasticsearch SearchGuard job finished with non 0 exit code
    • Index naming improvement for DataStream migration
    • fluentbit log exporter encreased max_buff_size
    • Licensed SearchGuard support
    • Kibana pods restarted on logging update
    • Kibana user don’t have permission on async search
    • AWS CloudWatch not working in v1.22 k8s
    • Infinite ELK job creation in cluster without centralized logging
  • Centralized monitoring:
    • Alermanager extraVar/extraEnv supports in helm chart
    • minor alert rules improvements

CNCF Kubernetes Conformance tests:

AirGap Artifacts list

Additionally, you need to download the BASH scripts from https://repo.kublr.com

You also need to download Helm package archives and Docker images:

Supported Kubernetes versions

v1.22

v1.21

v1.20

v1.19 (Deprecated in 1.23.0, End of support in 1.24.0)

Components versions

Kubernetes

ComponentVersionKublr AgentNotes
Kubernetes1.221.22.5-10default v1.22.5
1.211.21.8-25
1.201.20.14-31
1.191.19.16-58Deprecated in 1.23.0

Kublr Control Plane

ComponentVersion
Kublr Operator1.22.2-11
Kublr Control Plane1.22.2-58

Kublr Platform Features

ComponentVersion
Kubernetes
Dashboardv2.2.0
Cluster autoscaller1.8.4
Kublr System1.22.2-6
LocalPath Provisioner (helm chart version)0.0.12-8
Ingress1.22.2-9
nginx ingress controller (helm chart version)4.0.10
cert-manager (helm chart version)1.5.3
Centralized Logging1.22.2-33
ElasticSearch7.10.2
Kibana7.10.2
SearchGuard52.7.0
SearchGuard Kibana plugin51.0.0
SearchGuard Admin7.10.2-52.7.0
RabbitMQ3.9.5
Curator5.8.1
Logstash7.10.2
Fluentd3.3.0
Fluentbit1.8.10
Centralized Monitoring1.22.2-14
Prometheus2.28.1
Kube State Metrics (helm chart version)3.4.2
AlertManager0.22.0
Grafana7.5.10
Victoria Metrics
Cluster0.8.2
Agent0.6.5
Alert0.3.5
Kublr KubeDB (Deprecated in 1.22.0, End of support in 1.23.0)1.22.2-5
kubedb (helm chart version)v0.14.0-alpha.2

Known issues and limitations

  1. Kublr feature Ingress 1.22.2-9 included in Kublr 1.22 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).

  2. 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
    
  3. When upgrading a Kubernetes v1.22, Kublr feature Ingress must first be upgraded to v1.22.1-7. 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.

  4. Upgrading to the new Kublr Logging version will override kublr predefined SearchGuard roles (kublr:*, sg_kublr_kibana_user, sg_curator, sg_hooks, sg_kublr_logstash, sg_monitor) and role mappings (kublr:*, sg_kublr_logstash, sg_kublr_kibana_user, sg_curator, sg_hooks, sg_monitor, SGS_KIBANA_SERVER, SGS_LOGSTASH, SGS_ALL_ACCESS, SGS_KIBANA_USER).

    Please refer to support portlal howto backups existing customization before upgrading.

  5. Kublr feature logging with fluentbit log collector uses new Elasticsearch index template named kublr-logs instead of the legacy kublr-index-template. By default ES index templates are updated by Kublr once every 24 hours, so when plannig to switch from fluentd to fluentbit, it is recommended to first upgrade the control plane, and perform the switch 24 hours later.