Tips: Before Upgrade

Lenses Agent
Lenses HQ

Provisioning (v2) is mandatory

Main element managing all agents which are connecting to Kafka

It no longer uses the ingress controller

Supports only Postgres as a database

All security elements are moved from security.conf to Lenses HQ

Holder of license

Remained the same in terms of functionalities; authentication and authorization were moved to HQ, along with new features.

Single pane of glass for all engineers to check the whole Kafka ecosystem

No Wizard / UI for making connections between Agent and any component of Kafka ecosystem

Cannot work without HQ

PostgresDB is mandatory for Production systems (H2 embedded available as of v6.0.6 for non production deployments)

No longer holder of license

Read more how they work together in Overview

Pick a upgrade method

There are two upgrade methods and each has its ups and downs:

Decision Matrix

Choose Side by Side Migration When
Choose In-Place When

SLA requires < 5 minutes downtime or follows blue-green deployment patterns.

Downtime windows are acceptable.

Connections in Lenses ⅘ have been set by Wizard mode.

Configuration is simple (already use Provision v2).

Resources available for parallel infrastructure.

Quick upgrade is priority.

Wants to spend more time exploring IAMs and new potential permissions for certain AD Groups.

Enterprise deployment with SQL processors, complex data policies, and multi-tenant configurations.

Last updated

Was this helpful?