v3.3.1

What's Changed

• Fix JAVA_OPTS to Allow Additional Customization by Appending Existing Options by @mukesh154 in #141
• Increase memory limits to 4Gi to match Java heap space configuration by @mukesh154 in #142

New Contributors

• @mukesh154 made their first contribution in #141

Full Changelog: v3.3.0...v3.3.1

bkvm-0.1.1

A Helm chart for running BKVM

v3.3.0

What's Changed

• deps: bump misc dependencies by @nicoloboschi in #139
• fix: deleted ledgers are not removed from the cache by @nicoloboschi in #137

Full Changelog: bkvm-0.1.0...v3.3.0

v3.2.0

What's Changed

• Initial support for a basic Helm Chart for k8s deployment by @eolivelli in #126
• update chart by @enzo-dechaene in #128
• Add liveness and readiness probe to the chart by @nicoloboschi in #129
• Add release process for the chart by @nicoloboschi in #130
• Improve docs for the chart by @nicoloboschi in #131
• Bookies topology (kubernetes) by @nicoloboschi in #133

New Contributors

• @enzo-dechaene made their first contribution in #128

Full Changelog: v3.1.1...v3.2.0

bkvm-0.1.0

A Helm chart for running BKVM

bkvm-0.0.1

A Helm chart for running BKVM

v3.1.1

What's Changed

• Deduplicate yarn dependencies by @aluccaroni in #124
• Disable spammy log by default by @aluccaroni in #125

Full Changelog: v3.1.0...v3.1.1

v3.1.0

Full Changelog: v3.0.0...v3.1.0

v.3.0.0

News and noteworthy:

• Revamped UI
• New Ledger Search page, with pagination
• Automatic refresh of metadata (configurable, disabled by default)
• Support for multiple BookKeeper Clusters
• Support for BookKeeper 4.12 BookieID
• Expose Bookie Endpoints (httpserver, bookie-rpc) and capabilities (BP-38)
• Upgrade HerdDB to 0.22.0

Compatibility:
The new multi cluster mode required a brand new database schema, if you already have a database you have to wipe it out.
This is not a big problem, because at every metadata refresh we are populating all of the tables with up-to-date contents

v.1.2.0

• Allow to deploy BKVM with a relative path (like deploying a /bkvm instead of /)
• Publish to Maven Central split artifacts (war-no-libs and classes) in order to ease the intragretion with StringBoot applications like Apache Pulsar Manager