Kublr Release 1.23.1 (2022-11-10)

Kublr Quick Start

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

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:

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

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.

Overview

The Kublr 1.23.1 patch release includes bug fixes in Kublr Logging feature where RabbitMQ was OOM killed in RHEL9, UI, minor Kublr agent Kubernetes versions updates and CNI providers upgrades.

All Kublr components are checked for vulnerabilities with Aquasecurity trivy scaner.

Important Notes

  • Kuberntes Pod Security Policy feature is deprecated and will be removed from Kubernetes v1.25

    • (PSA) Enabled by default starting with Kublr agent v1.23
    • (PSP) Enabled in Kublr agent v1.23, deprecated and disabled in agent v1.24
  • 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

Important Fixes and Changes

  • Minor Kubernetes versions updated to v1.24.7, v1.23.13, v1.22.15

  • CNI providers updated in k8s v1.24, v1.23 and v1.22:

    • Canal: v3.24.1
    • Flannel: v0.15.1
  • Kublr logging feature fixes:

    • RabbitMQ OOM killed in RHEL9
    • Logging controller cannot create a default index pattern
  • Kublr license management

    • License management UI fixes
    • Fully functional 30 day trial license is included in the Kublr Demo/Installer
  • Kublr cert-updater component

    • Improved behavior for k8s v1.22 and above
    • Deprecated in Kublr v1.24 and will be removed from Kublr 1.25.0

Fixes

  • Alertmanager rules bug fixes
  • Kublr operator freezes on checksum mismatch
  • Kublr agent sets an incorrect node state condition if the node has pod swithout controller in comleted state
  • Keycloak NPM lib updated

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.24

v1.23

v1.22

v1.21

v1.20 (Deprecated in 1.24.0, End of support in 1.25.0)

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

Components versions

Kubernetes

ComponentVersionKublr AgentNotes
Kubernetes1.241.24.7-1default v1.24.7
1.231.23.13-1
1.221.22.15-1
1.211.21.14-8
1.201.20.14-9Deprecated in 1.24.0
1.191.19.16-9End of support in 1.24.0

Kublr Control Plane

ComponentVersion
Kublr Operator1.23.1
Kublr Control Plane1.23.1

Kublr Platform Features

ComponentVersion
Kubernetes
Dashboardv2.4.0
Kublr System1.23.1
LocalPath Provisioner (helm chart version)0.0.22-11
Ingress1.23.1
nginx ingress controller (helm chart version)4.2.3
cert-manager (helm chart version)1.5.3
Centralized Logging**1.23.1 *
ElasticSearch7.10.2
Kibana7.10.2
SearchGuard52.3.0
SearchGuard Kibana plugin51.0.0
SearchGuard Admin7.10.2-52.3.0
RabbitMQ3.9.5
Curator5.8.1
Logstash7.10.2
Fluentd3.3.0
Fluentbit1.8.10
Centralized Monitoring1.23.1
Prometheus2.37.1
Kube State Metrics (helm chart version)3.4.2
AlertManager0.22.0
Grafana7.5.10
Victoria Metrics
Cluster0.9.13
Agent0.7.35
Alert0.4.15

Known issues and limitations

  1. 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
    
  2. For Kublr kubernetes clusters deployed on vSphere it is necessary to unmount CD/DVD drive 1 from each virtual machines manually via vCenter console.

  3. vSphere clusters cannot be deleted automaticaly, it is necessary to remove VMs manually and unregister the cluster after that.